linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: 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 parameter to limit V1 page-sizes to 4 KiB
Date: Wed, 4 Sep 2024 15:15:16 +0200	[thread overview]
Message-ID: <ZthdZElA6KEMtYxt@8bytes.org> (raw)
In-Reply-To: <20240904130329.GC3915968@nvidia.com>

On Wed, Sep 04, 2024 at 10:03:29AM -0300, Jason Gunthorpe wrote:
> Why is this a kernel command line? Surely it should be negotiated
> automaticaly with capability registers or ACPI like everone else does
> if there is something functionally wrong with the vIOMMU??

In the affected setups there is no vIOMMU. This is not about secure-IO,
the assigned devices will not be part of the trusted base.

> If we are doing this we also have a problem on mlx5 devices where
> there are too many page sizes in the v1 table and it blows up the ATS
> caching. It would be nice to widen this option to limit the page sizes
> to other combinations (4k/2M/1G or something).

Okay, I will update the patch to allow more settings.

Regards,

	Joerg

      reply	other threads:[~2024-09-04 13:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04 12:59 [PATCH] iommu/amd: Add parameter to limit V1 page-sizes to 4 KiB Joerg Roedel
2024-09-04 13:03 ` Jason Gunthorpe
2024-09-04 13:15   ` Joerg Roedel [this message]

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=ZthdZElA6KEMtYxt@8bytes.org \
    --to=joro@8bytes.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).