From: Christoph Hellwig <hch@infradead.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Baoquan He <bhe@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org,
rientjes@google.com, rppt@linux.ibm.com, thomas.lendacky@amd.com,
brijesh.singh@amd.com, kexec@lists.infradead.org,
iommu@lists.linux-foundation.org, m.szyprowski@samsung.com
Subject: Re: [PATCH RFC 0/2] dma-pool: allow user to disable atomic pool
Date: Thu, 24 Jun 2021 13:10:51 +0100 [thread overview]
Message-ID: <YNR2S02hWS2hwNiz@infradead.org> (raw)
In-Reply-To: <8b3d4e02-6e94-ad59-a480-fed8e55c009a@arm.com>
On Thu, Jun 24, 2021 at 11:47:31AM +0100, Robin Murphy wrote:
> Hmm, I think the Kconfig reshuffle has actually left a slight wrinkle here.
> For DMA_DIRECT_REMAP=y we can assume an atomic pool is always needed, since
> that was the original behaviour anyway. However the implications of
> AMD_MEM_ENCRYPT=y are different - even if support is enabled, it still
> should only be relevant if mem_encrypt_active(), so it probably does make
> sense to have an additional runtime gate on that.
Yeah, a check for that would probably be useful.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: thomas.lendacky@amd.com, brijesh.singh@amd.com, x86@kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
rppt@linux.ibm.com, Christoph Hellwig <hch@infradead.org>,
linux-mm@kvack.org, iommu@lists.linux-foundation.org,
rientjes@google.com
Subject: Re: [PATCH RFC 0/2] dma-pool: allow user to disable atomic pool
Date: Thu, 24 Jun 2021 13:10:51 +0100 [thread overview]
Message-ID: <YNR2S02hWS2hwNiz@infradead.org> (raw)
In-Reply-To: <8b3d4e02-6e94-ad59-a480-fed8e55c009a@arm.com>
On Thu, Jun 24, 2021 at 11:47:31AM +0100, Robin Murphy wrote:
> Hmm, I think the Kconfig reshuffle has actually left a slight wrinkle here.
> For DMA_DIRECT_REMAP=y we can assume an atomic pool is always needed, since
> that was the original behaviour anyway. However the implications of
> AMD_MEM_ENCRYPT=y are different - even if support is enabled, it still
> should only be relevant if mem_encrypt_active(), so it probably does make
> sense to have an additional runtime gate on that.
Yeah, a check for that would probably be useful.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Baoquan He <bhe@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org,
rientjes@google.com, rppt@linux.ibm.com, thomas.lendacky@amd.com,
brijesh.singh@amd.com, kexec@lists.infradead.org,
iommu@lists.linux-foundation.org, m.szyprowski@samsung.com
Subject: Re: [PATCH RFC 0/2] dma-pool: allow user to disable atomic pool
Date: Thu, 24 Jun 2021 13:10:51 +0100 [thread overview]
Message-ID: <YNR2S02hWS2hwNiz@infradead.org> (raw)
In-Reply-To: <8b3d4e02-6e94-ad59-a480-fed8e55c009a@arm.com>
On Thu, Jun 24, 2021 at 11:47:31AM +0100, Robin Murphy wrote:
> Hmm, I think the Kconfig reshuffle has actually left a slight wrinkle here.
> For DMA_DIRECT_REMAP=y we can assume an atomic pool is always needed, since
> that was the original behaviour anyway. However the implications of
> AMD_MEM_ENCRYPT=y are different - even if support is enabled, it still
> should only be relevant if mem_encrypt_active(), so it probably does make
> sense to have an additional runtime gate on that.
Yeah, a check for that would probably be useful.
next prev parent reply other threads:[~2021-06-24 12:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 5:20 [PATCH RFC 0/2] dma-pool: allow user to disable atomic pool Baoquan He
2021-06-24 5:20 ` Baoquan He
2021-06-24 5:20 ` [PATCH 1/2] docs: kernel-parameters: Update to reflect the current default size of " Baoquan He
2021-06-24 5:20 ` Baoquan He
2021-06-24 5:20 ` [PATCH 2/2] dma-pool: allow user to disable " Baoquan He
2021-06-24 5:20 ` Baoquan He
2021-06-24 7:40 ` [PATCH RFC 0/2] " Christoph Hellwig
2021-06-24 7:40 ` Christoph Hellwig
2021-06-24 9:29 ` Baoquan He
2021-06-24 9:29 ` Baoquan He
2021-06-24 9:29 ` Baoquan He
2021-06-24 10:47 ` Robin Murphy
2021-06-24 10:47 ` Robin Murphy
2021-06-24 10:47 ` Robin Murphy
2021-06-24 12:10 ` Christoph Hellwig [this message]
2021-06-24 12:10 ` Christoph Hellwig
2021-06-24 12:10 ` Christoph Hellwig
2021-08-05 6:54 ` Baoquan He
2021-08-05 6:54 ` Baoquan He
2021-08-05 6:54 ` Baoquan He
2021-08-10 20:52 ` Tom Lendacky
2021-08-10 20:52 ` Tom Lendacky
2021-08-10 20:52 ` Tom Lendacky via iommu
2021-08-11 2:23 ` Baoquan He
2021-08-11 2:23 ` Baoquan He
2021-08-11 2:23 ` Baoquan He
2021-08-11 13:46 ` Tom Lendacky
2021-08-11 13:46 ` Tom Lendacky
2021-08-11 13:46 ` Tom Lendacky via iommu
2021-08-11 5:52 ` Christoph Hellwig
2021-08-11 5:52 ` Christoph Hellwig
2021-08-11 5:52 ` 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=YNR2S02hWS2hwNiz@infradead.org \
--to=hch@infradead.org \
--cc=bhe@redhat.com \
--cc=brijesh.singh@amd.com \
--cc=iommu@lists.linux-foundation.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=rientjes@google.com \
--cc=robin.murphy@arm.com \
--cc=rppt@linux.ibm.com \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.