[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgobPe0U=Sc-PH08vF-ZbG00KrzftEpQMQ=n0LLNn7y6A@mail.gmail.com>
Date: Mon, 8 May 2023 09:42:18 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Jacob Pan <jacob.jun.pan@...ux.intel.com>
Cc: LKML <linux-kernel@...r.kernel.org>, iommu@...ts.linux.dev,
Jason Gunthorpe <jgg@...dia.com>,
Lu Baolu <baolu.lu@...ux.intel.com>,
Joerg Roedel <joro@...tes.org>,
Jean-Philippe Brucker <jean-philippe@...aro.com>,
Robin Murphy <robin.murphy@....com>,
Will Deacon <will@...nel.org>, Raj Ashok <ashok.raj@...el.com>,
"Tian, Kevin" <kevin.tian@...el.com>, Yi Liu <yi.l.liu@...el.com>,
"Yu, Fenghua" <fenghua.yu@...el.com>,
"Hansen, Dave" <dave.hansen@...el.com>
Subject: Re: [PATCH] iommu: Add Kconfig help text for IOMMU_SVA
On Mon, May 8, 2023 at 9:35 AM Jacob Pan <jacob.jun.pan@...ux.intel.com> wrote:
>
> Conversely, we could also have some part of PASID that is not about SVA.
If that's the case, then we should *definitely* have that IOMMU_PASID
kind of config option.
Then IOMMU_SVA - that needs PASID - can "select" it, but any other use
- that doesn't bother about SVA but might want PASID for its own
nefarious purposes - can also select it.
This is why we have config options. Not just for legibility, but also
for "there are different scenarios".
Linus
Powered by blists - more mailing lists