From: Joerg Roedel <joro@8bytes.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Baolu Lu <baolu.lu@linux.intel.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Vasant Hegde <vasant.hegde@amd.com>,
linux-doc@vger.kernel.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org, Joerg Roedel <jroedel@suse.de>
Subject: Re: [PATCH] iommu/amd: Add kernel parameters to limit V1 page-sizes
Date: Thu, 5 Sep 2024 17:13:53 +0200 [thread overview]
Message-ID: <ZtnKsf71piBohHt_@8bytes.org> (raw)
In-Reply-To: <20240905120531.GD1358970@nvidia.com>
On Thu, Sep 05, 2024 at 09:05:31AM -0300, Jason Gunthorpe wrote:
> On Thu, Sep 05, 2024 at 09:34:07AM +0200, Joerg Roedel wrote:
> > On Thu, Sep 05, 2024 at 03:31:08PM +0800, Baolu Lu wrote:
> > > "iommu.nohugepages=1"?
> >
> > Generally yes, but that requires to touch all drivers to make the
> > behavior consistent. We can start this effort on-top of this change, if
> > desired.
>
> Let's at least use the same keyword that already exists though??
You mean amd_iommu=sp_off? I am not in favour of that, in the Linux
world the term 'hugepage' is more common than 'superpage'. So I
would avoid spreading the use of the later. We can extend that later to
the iommu.nohugepages parameter suggested by Baolu.
Regards,
Joerg
next prev parent reply other threads:[~2024-09-05 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 7:22 [PATCH] iommu/amd: Add kernel parameters to limit V1 page-sizes Joerg Roedel
2024-09-05 7:31 ` Baolu Lu
2024-09-05 7:34 ` Joerg Roedel
2024-09-05 8:09 ` Baolu Lu
2024-09-05 12:05 ` Jason Gunthorpe
2024-09-05 15:13 ` Joerg Roedel [this message]
2024-09-05 17:52 ` Jason Gunthorpe
2024-09-09 15:39 ` Jason Gunthorpe
2024-09-09 14:50 ` Vasant Hegde
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=ZtnKsf71piBohHt_@8bytes.org \
--to=joro@8bytes.org \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jroedel@suse.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@amd.com \
--cc=will@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.