From: "Lendacky, Thomas" <Thomas.Lendacky@amd.com>
To: Lucas Stach <l.stach@pengutronix.de>, Christoph Hellwig <hch@lst.de>
Cc: "iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thiago Jung Bauermann <bauerman@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>
Subject: Re: Regression due to d98849aff879 (dma-direct: handle DMA_ATTR_NO_KERNEL_MAPPING in common code)
Date: Tue, 6 Aug 2019 14:18:49 +0000 [thread overview]
Message-ID: <78833204-cd30-1a4b-54e3-1580018c6d57@amd.com> (raw)
In-Reply-To: <1565100418.2323.32.camel@pengutronix.de>
On 8/6/19 9:06 AM, Lucas Stach wrote:
> Am Dienstag, den 06.08.2019, 16:04 +0200 schrieb Christoph Hellwig:
>> Ok, does this work?
>>
>> --
>> From 34d35f335a98f515f2516b515051e12eae744c8d Mon Sep 17 00:00:00 2001
>>> From: Christoph Hellwig <hch@lst.de>
>> Date: Tue, 6 Aug 2019 14:33:23 +0300
>> Subject: dma-direct: fix DMA_ATTR_NO_KERNEL_MAPPING
>>
>> The new DMA_ATTR_NO_KERNEL_MAPPING needs to actually assign
>> a dma_addr to work. Also skip it if the architecture needs
>> forced decryption handling, as that needs a kernel virtual
>> address.
>>
>> Fixes: d98849aff879 (dma-direct: handle DMA_ATTR_NO_KERNEL_MAPPING in common code)
>>> Signed-off-by: Christoph Hellwig <hch@lst.de>
>> ---
>> kernel/dma/direct.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/kernel/dma/direct.c b/kernel/dma/direct.c
>> index 59bdceea3737..b01064d884f2 100644
>> --- a/kernel/dma/direct.c
>> +++ b/kernel/dma/direct.c
>> @@ -130,11 +130,13 @@ void *dma_direct_alloc_pages(struct device *dev, size_t size,
>>> if (!page)
>>> return NULL;
>>
>>> - if (attrs & DMA_ATTR_NO_KERNEL_MAPPING) {
>>> + if ((attrs & DMA_ATTR_NO_KERNEL_MAPPING) &&
>> + !force_dma_unencrypted(dev)) {
I think you need to keep everything inside the original if statement since
the caller is expecting a page pointer to be returned in this case and not
the page_address() which is returned when the DMA_ATTR_NO_KERNEL_MAPPING
is not present.
>
> dma_direct_free_pages() then needs the same check, as otherwise the cpu
Agreed. And the cpu_addr passed in here will be the page pointer, so
will need to keep everything inside the if check of the
DMA_ATTR_NO_KERNEL_MAPPING attr here as well.
Thanks,
Tom
> address is treated as a cookie instead of a real address and the
> encryption needs to be re-enabled.
>
> Regards,
> Lucas
>
>> /* remove any dirty cache lines on the kernel alias */
>>> if (!PageHighMem(page))
>>> arch_dma_prep_coherent(page, size);
>>> /* return the page pointer as the opaque cookie */
>>> + *dma_handle = phys_to_dma(dev, page_to_phys(page));
>>> return page;
>>> }
>>
next prev parent reply other threads:[~2019-08-06 14:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 9:13 Lucas Stach
2019-08-06 11:33 ` Christoph Hellwig
2019-08-06 12:20 ` Lucas Stach
2019-08-06 13:38 ` Lendacky, Thomas
2019-08-06 14:04 ` Christoph Hellwig
2019-08-06 14:06 ` Lucas Stach
2019-08-06 14:18 ` Lendacky, Thomas [this message]
2019-08-06 15:46 ` Christoph Hellwig
2019-08-06 15:59 ` Lendacky, Thomas
2019-08-06 16:07 ` Christoph Hellwig
2019-08-06 15:44 ` Christoph Hellwig
2019-08-07 15:24 ` Lucas Stach
2019-08-08 7:48 ` Christoph Hellwig
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=78833204-cd30-1a4b-54e3-1580018c6d57@amd.com \
--to=thomas.lendacky@amd.com \
--cc=bauerman@linux.ibm.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=l.stach@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pasic@linux.ibm.com \
/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
all inboxes | Powered by JetHome®