From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f199.google.com (mail-pf0-f199.google.com [209.85.192.199]) by kanga.kvack.org (Postfix) with ESMTP id A1BEC6B036A for ; Thu, 8 Jun 2017 19:04:14 -0400 (EDT) Received: by mail-pf0-f199.google.com with SMTP id h76so19173280pfh.15 for ; Thu, 08 Jun 2017 16:04:14 -0700 (PDT) Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0059.outbound.protection.outlook.com. [104.47.38.59]) by mx.google.com with ESMTPS id 91si5373830ply.252.2017.06.08.16.04.13 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 08 Jun 2017 16:04:13 -0700 (PDT) Subject: Re: [PATCH v6 25/34] swiotlb: Add warnings for use of bounce buffers with SME References: <20170607191309.28645.15241.stgit@tlendack-t1.amdoffice.net> <20170607191732.28645.42876.stgit@tlendack-t1.amdoffice.net> <20170608075829.GA2446@infradead.org> From: Tom Lendacky Message-ID: <8d78db0c-7c3e-9304-7d04-31095246ec83@amd.com> Date: Thu, 8 Jun 2017 18:04:03 -0500 MIME-Version: 1.0 In-Reply-To: <20170608075829.GA2446@infradead.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Christoph Hellwig Cc: linux-arch@vger.kernel.org, linux-efi@vger.kernel.org, kvm@vger.kernel.org, linux-doc@vger.kernel.org, x86@kernel.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com, linux-mm@kvack.org, iommu@lists.linux-foundation.org, Rik van Riel , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , Toshimitsu Kani , Arnd Bergmann , Jonathan Corbet , Matt Fleming , "Michael S. Tsirkin" , Joerg Roedel , Konrad Rzeszutek Wilk , Paolo Bonzini , Larry Woodman , Brijesh Singh , Ingo Molnar , Borislav Petkov , Andy Lutomirski , "H. Peter Anvin" , Andrey Ryabinin , Alexander Potapenko , Dave Young , Thomas Gleixner , Dmitry Vyukov On 6/8/2017 2:58 AM, Christoph Hellwig wrote: > On Wed, Jun 07, 2017 at 02:17:32PM -0500, Tom Lendacky wrote: >> Add warnings to let the user know when bounce buffers are being used for >> DMA when SME is active. Since the bounce buffers are not in encrypted >> memory, these notifications are to allow the user to determine some >> appropriate action - if necessary. > > And what would the action be? Do we need a boot or other option to > disallow this fallback for people who care deeply? The action could be to enable the IOMMU so that lower DMA addresses are used, or to replace the device with one that supports 64-bit DMA or, if the device is not used much, you could just ignore it. I'm not sure we need an option to disallow the fallback. Are you thinking along the lines of disabling the device? Thanks, Tom > -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org