public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	iommu@lists.linux.dev, Jason Gunthorpe <jgg@nvidia.com>,
	Lu Baolu <baolu.lu@linux.intel.com>,
	Joerg Roedel <joro@8bytes.org>,
	Jean-Philippe Brucker <jean-philippe@linaro.com>,
	Robin Murphy <robin.murphy@arm.com>,
	Will Deacon <will@kernel.org>, Raj Ashok <ashok.raj@intel.com>,
	"Tian, Kevin" <kevin.tian@intel.com>, Yi Liu <yi.l.liu@intel.com>,
	"Yu, Fenghua" <fenghua.yu@intel.com>,
	jacob.jun.pan@linux.intel.com
Subject: Re: [PATCH] iommu: Add Kconfig help text for IOMMU_SVA
Date: Sat, 6 May 2023 15:07:41 -0700	[thread overview]
Message-ID: <20230506150741.2e3d2dcc@jacob-builder> (raw)
In-Reply-To: <CAHk-=wgUiAtiszwseM1p2fCJ+sC4XWQ+YN4TanFhUgvUqjr9Xw@mail.gmail.com>

Hi Linus,

On Sat, 6 May 2023 08:43:08 -0700, Linus Torvalds
<torvalds@linux-foundation.org> wrote:

> On Sat, May 6, 2023 at 6:27 AM Jacob Pan <jacob.jun.pan@linux.intel.com>
> wrote:
> >
> > Shared Virtual Addressing (SVA) is not immediately intuitive to people
> > who work outside IOMMU subsystem, add some explanation to make it less
> > opaque.  
> 
> So the patch has at least two problems.
> 
> The first is that you corrupted the SPDX line.
> 
Sorry, my mistake. Will not try sending patches before fully waking up.

> But the second is that the change from
> 
> -       bool
> +       bool "Shared Virtual Addressing"
> 
> means that now Kconfig *asks* about this thing, which was never the
> intent. The other Kconfig options that need it all do a
> 
>         select IOMMU_SVA
> 
> to get it picked.
> 
> I suspect that's why it then causes errors - because now the test
> robot can enable the option even in situations where it makes no sense
> and doesn't work.
> 
> So no, it's not that the option needs a help entry that can be queried
> at Kconfig time. It's that the option needs a name that makes sense
> and isn't some random jumble of letters that is only understandable to
> people who already know exactly what it is.
Right, how about IOMMU_SHARING_CPU_PGTABLE?

Since this is more of a one-sided relationship where IOMMU walks CPU page
tables.


Thanks,

Jacob

  reply	other threads:[~2023-05-06 22:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06 13:31 [PATCH] iommu: Add Kconfig help text for IOMMU_SVA Jacob Pan
2023-05-06 15:19 ` kernel test robot
2023-05-06 15:39 ` kernel test robot
2023-05-06 15:39 ` kernel test robot
2023-05-06 15:43 ` Linus Torvalds
2023-05-06 22:07   ` Jacob Pan [this message]
2023-05-07 18:52     ` Linus Torvalds
2023-05-08 16:40       ` Jacob Pan
2023-05-08 16:42         ` Linus Torvalds
2023-05-08 16:55           ` Jason Gunthorpe
2023-05-08 17:17             ` Linus Torvalds
2023-05-08 20:21               ` Jacob Pan
2023-05-09  0:13                 ` Tian, Kevin
2023-05-09  1:55                 ` Baolu Lu
2023-05-09  0:10               ` Tian, Kevin
2023-05-09 23:06               ` Jason Gunthorpe

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=20230506150741.2e3d2dcc@jacob-builder \
    --to=jacob.jun.pan@linux.intel.com \
    --cc=ashok.raj@intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=jean-philippe@linaro.com \
    --cc=jgg@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=will@kernel.org \
    --cc=yi.l.liu@intel.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