From: Tom Lendacky <thomas.lendacky@amd.com>
To: Borislav Petkov <bp@alien8.de>
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, xen-devel@lists.xen.org,
linux-mm@kvack.org, iommu@lists.linux-foundation.org,
"Brijesh Singh" <brijesh.singh@amd.com>,
"Toshimitsu Kani" <toshi.kani@hpe.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Matt Fleming" <matt@codeblueprint.co.uk>,
"Alexander Potapenko" <glider@google.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Larry Woodman" <lwoodman@redhat.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Joerg Roedel" <joro@8bytes.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Ingo Molnar" <mingo@redhat.com>,
"Andrey Ryabinin" <aryabinin@virtuozzo.com>,
"Dave Young" <dyoung@redhat.com>,
"Rik van Riel" <riel@redhat.com>, "Arnd Bergmann" <arnd@arndb.de>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"Andy Lutomirski" <luto@kernel.org>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Dmitry Vyukov" <dvyukov@google.com>,
"Juergen Gross" <jgross@suse.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH v7 25/36] swiotlb: Add warnings for use of bounce buffers with SME
Date: Wed, 21 Jun 2017 10:37:41 -0500 [thread overview]
Message-ID: <7b9f8b6d-60f2-0a78-b582-0821401d17eb@amd.com> (raw)
In-Reply-To: <20170621105026.lcbtkklaenyi2wqe@pd.tnic>
On 6/21/2017 5:50 AM, Borislav Petkov wrote:
> On Fri, Jun 16, 2017 at 01:54:36PM -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. Actions can range from utilizing an
>> IOMMU, replacing the device with another device that can support 64-bit
>> DMA, ignoring the message if the device isn't used much, etc.
>>
>> Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
>> ---
>> include/linux/dma-mapping.h | 11 +++++++++++
>> include/linux/mem_encrypt.h | 8 ++++++++
>> lib/swiotlb.c | 3 +++
>> 3 files changed, 22 insertions(+)
>>
>> diff --git a/include/linux/dma-mapping.h b/include/linux/dma-mapping.h
>> index 4f3eece..ee2307e 100644
>> --- a/include/linux/dma-mapping.h
>> +++ b/include/linux/dma-mapping.h
>> @@ -10,6 +10,7 @@
>> #include <linux/scatterlist.h>
>> #include <linux/kmemcheck.h>
>> #include <linux/bug.h>
>> +#include <linux/mem_encrypt.h>
>>
>> /**
>> * List of possible attributes associated with a DMA mapping. The semantics
>> @@ -577,6 +578,11 @@ static inline int dma_set_mask(struct device *dev, u64 mask)
>>
>> if (!dev->dma_mask || !dma_supported(dev, mask))
>> return -EIO;
>> +
>> + /* Since mask is unsigned, this can only be true if SME is active */
>> + if (mask < sme_dma_mask())
>> + dev_warn(dev, "SME is active, device will require DMA bounce buffers\n");
>> +
>> *dev->dma_mask = mask;
>> return 0;
>> }
>> @@ -596,6 +602,11 @@ static inline int dma_set_coherent_mask(struct device *dev, u64 mask)
>> {
>> if (!dma_supported(dev, mask))
>> return -EIO;
>> +
>> + /* Since mask is unsigned, this can only be true if SME is active */
>> + if (mask < sme_dma_mask())
>> + dev_warn(dev, "SME is active, device will require DMA bounce buffers\n");
>
> Looks to me like those two checks above need to be a:
>
> void sme_check_mask(struct device *dev, u64 mask)
> {
> if (!sme_me_mask)
> return;
>
> /* Since mask is unsigned, this can only be true if SME is active */
> if (mask < (((u64)sme_me_mask << 1) - 1))
> dev_warn(dev, "SME is active, device will require DMA bounce buffers\n");
> }
>
> which gets called and sme_dma_mask() is not really needed.
Makes a lot of sense, I'll update the patch.
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-06-21 15:37 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 18:49 [PATCH v7 00/36] x86: Secure Memory Encryption (AMD) Tom Lendacky
2017-06-16 18:49 ` [PATCH v7 01/36] x86: Document AMD Secure Memory Encryption (SME) Tom Lendacky
2017-06-16 18:50 ` [PATCH v7 02/36] x86/mm/pat: Set write-protect cache mode for full PAT support Tom Lendacky
2017-06-16 18:50 ` [PATCH v7 03/36] x86, mpparse, x86/acpi, x86/PCI, x86/dmi, SFI: Use memremap for RAM mappings Tom Lendacky
2017-06-20 7:21 ` Borislav Petkov
2017-06-16 18:50 ` [PATCH v7 04/36] x86/CPU/AMD: Add the Secure Memory Encryption CPU feature Tom Lendacky
2017-06-16 18:50 ` [PATCH v7 05/36] x86/CPU/AMD: Handle SME reduction in physical address size Tom Lendacky
2017-06-16 18:50 ` [PATCH v7 06/36] x86/mm: Add Secure Memory Encryption (SME) support Tom Lendacky
2017-06-20 20:49 ` Thomas Gleixner
2017-06-21 13:26 ` Tom Lendacky
2017-06-16 18:51 ` [PATCH v7 07/36] x86/mm: Don't use phys_to_virt in ioremap() if SME is active Tom Lendacky
2017-06-20 20:55 ` Thomas Gleixner
2017-06-21 13:52 ` Tom Lendacky
2017-06-21 7:37 ` Thomas Gleixner
2017-06-21 13:54 ` Tom Lendacky
2017-06-16 18:51 ` [PATCH v7 08/36] x86/mm: Add support to enable SME in early boot processing Tom Lendacky
2017-06-20 7:38 ` Borislav Petkov
2017-06-20 15:52 ` Tom Lendacky
2017-06-21 7:16 ` Thomas Gleixner
2017-06-21 15:14 ` Tom Lendacky
2017-06-21 15:38 ` Thomas Gleixner
2017-06-21 18:30 ` Tom Lendacky
2017-06-21 18:52 ` Thomas Gleixner
2017-06-16 18:51 ` [PATCH v7 09/36] x86/mm: Simplify p[gum]d_page() macros Tom Lendacky
2017-06-16 18:51 ` [PATCH v7 10/36] x86/mm: Provide general kernel support for memory encryption Tom Lendacky
2017-06-21 7:18 ` Thomas Gleixner
2017-06-21 8:23 ` Borislav Petkov
2017-06-16 18:51 ` [PATCH v7 11/36] x86/mm: Add SME support for read_cr3_pa() Tom Lendacky
2017-06-20 8:25 ` Borislav Petkov
2017-06-20 16:17 ` Andy Lutomirski
2017-06-20 16:23 ` Tom Lendacky
2017-06-16 18:52 ` [PATCH v7 12/36] x86/mm: Extend early_memremap() support with additional attrs Tom Lendacky
2017-06-16 18:52 ` [PATCH v7 13/36] x86/mm: Add support for early encrypt/decrypt of memory Tom Lendacky
2017-06-16 18:52 ` [PATCH v7 14/36] x86/mm: Insure that boot memory areas are mapped properly Tom Lendacky
2017-06-20 15:30 ` Borislav Petkov
2017-06-16 18:52 ` [PATCH v7 15/36] x86/boot/e820: Add support to determine the E820 type of an address Tom Lendacky
2017-06-16 18:52 ` [PATCH v7 16/36] efi: Add an EFI table address match function Tom Lendacky
2017-06-22 10:57 ` Matt Fleming
2017-06-16 18:53 ` [PATCH v7 17/36] efi: Update efi_mem_type() to return an error rather than 0 Tom Lendacky
2017-06-22 10:03 ` Matt Fleming
2017-06-16 18:53 ` [PATCH v7 18/36] x86/efi: Update EFI pagetable creation to work with SME Tom Lendacky
2017-06-22 10:58 ` Matt Fleming
2017-06-16 18:53 ` [PATCH v7 19/36] x86/mm: Add support to access boot related data in the clear Tom Lendacky
2017-06-20 20:39 ` Borislav Petkov
2017-06-22 11:04 ` Matt Fleming
2017-06-16 18:53 ` [PATCH v7 20/36] x86, mpparse: Use memremap to map the mpf and mpc data Tom Lendacky
2017-06-21 8:39 ` Borislav Petkov
2017-06-16 18:53 ` [PATCH v7 21/36] x86/mm: Add support to access persistent memory in the clear Tom Lendacky
2017-06-16 18:54 ` [PATCH v7 22/36] x86/mm: Add support for changing the memory encryption attribute Tom Lendacky
2017-06-16 18:54 ` [PATCH v7 23/36] x86, realmode: Decrypt trampoline area if memory encryption is active Tom Lendacky
2017-06-21 9:43 ` Borislav Petkov
2017-06-16 18:54 ` [PATCH v7 24/36] x86, swiotlb: Add memory encryption support Tom Lendacky
2017-06-21 9:54 ` Borislav Petkov
2017-06-16 18:54 ` [PATCH v7 25/36] swiotlb: Add warnings for use of bounce buffers with SME Tom Lendacky
2017-06-21 10:50 ` Borislav Petkov
2017-06-21 15:37 ` Tom Lendacky [this message]
2017-06-16 18:54 ` [PATCH v7 26/36] x86/CPU/AMD: Make the microcode level available earlier in the boot Tom Lendacky
2017-06-22 9:40 ` Borislav Petkov
2017-06-16 18:54 ` [PATCH v7 27/36] iommu/amd: Allow the AMD IOMMU to work with memory encryption Tom Lendacky
2017-06-22 10:56 ` Borislav Petkov
2017-06-22 16:48 ` Tom Lendacky
2017-06-16 18:55 ` [PATCH v7 28/36] x86, realmode: Check for memory encryption on the APs Tom Lendacky
2017-06-16 18:55 ` [PATCH v7 29/36] x86, drm, fbdev: Do not specify encrypted memory for video mappings Tom Lendacky
2017-06-17 14:08 ` kbuild test robot
2017-06-16 18:55 ` [PATCH v7 30/36] kvm: x86: svm: Support Secure Memory Encryption within KVM Tom Lendacky
2017-06-16 18:55 ` [PATCH v7 31/36] x86/mm, kexec: Allow kexec to be used with SME Tom Lendacky
2017-06-23 8:56 ` Borislav Petkov
2017-06-16 18:55 ` [PATCH v7 32/36] xen/x86: Remove SME feature in PV guests Tom Lendacky
2017-06-17 10:40 ` Juergen Gross
2017-06-23 9:09 ` Borislav Petkov
2017-06-16 18:56 ` [PATCH v7 33/36] x86/mm: Use proper encryption attributes with /dev/mem Tom Lendacky
2017-06-23 9:32 ` Borislav Petkov
2017-06-16 18:56 ` [PATCH v7 34/36] x86/mm: Add support to encrypt the kernel in-place Tom Lendacky
2017-06-23 10:00 ` Borislav Petkov
2017-06-23 17:44 ` Tom Lendacky
2017-06-26 15:45 ` Borislav Petkov
2017-06-26 16:34 ` Tom Lendacky
2017-06-16 18:56 ` [PATCH v7 35/36] x86/boot: Add early cmdline parsing for options with arguments Tom Lendacky
2017-06-23 11:57 ` Borislav Petkov
2017-06-16 18:56 ` [PATCH v7 36/36] x86/mm: Add support to make use of Secure Memory Encryption Tom Lendacky
2017-06-23 17:39 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7b9f8b6d-60f2-0a78-b582-0821401d17eb@amd.com \
--to=thomas.lendacky@amd.com \
--cc=arnd@arndb.de \
--cc=aryabinin@virtuozzo.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=corbet@lwn.net \
--cc=dvyukov@google.com \
--cc=dyoung@redhat.com \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jgross@suse.com \
--cc=joro@8bytes.org \
--cc=kasan-dev@googlegroups.com \
--cc=kexec@lists.infradead.org \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=lwoodman@redhat.com \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=riel@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=toshi.kani@hpe.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox