All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Eric Auger <eric.auger@redhat.com>
Cc: iommu@lists.linux.dev, Binbin Wu <binbin.wu@linux.intel.com>,
	Kevin Tian <kevin.tian@intel.com>,
	Lixiao Yang <lixiao.yang@intel.com>,
	Matthew Rosato <mjrosato@linux.ibm.com>,
	Nicolin Chen <nicolinc@nvidia.com>, Yi Liu <yi.l.liu@intel.com>
Subject: Re: [PATCH 3/3] iommufd: Change the order of MSI setup
Date: Thu, 8 Dec 2022 10:35:46 -0400	[thread overview]
Message-ID: <Y5H2Qmz2bCXYHLA1@nvidia.com> (raw)
In-Reply-To: <148ee0ee-769e-201f-f918-5c3705225aeb@redhat.com>

On Thu, Dec 08, 2022 at 03:18:49PM +0100, Eric Auger wrote:
> > -	dev_warn(
> > -		idev->dev,
> > -		"MSI interrupt window cannot be isolated by the IOMMU, this platform is insecure. Use the \"allow_unsafe_interrupts\" module parameter to override\n");
> > +		dev_warn(
> > +			idev->dev,
> > +			"MSI interrupt window cannot be isolated by the IOMMU, this platform is insecure. Use the \"allow_unsafe_interrupts\" module parameter to override\n");

> I really prefer the legacy VFIO warning message: "No interrupt remapping
> support.  Use ...". IRQ remapping is the feature that is actually
> checked. MSI interrupt window sounds confusing: is it the MSI doorbell
> or the range of addresses that correspond to MSI addresses.

Well, that is true for x86 processors, but it is not what it is
called on ARM. I wanted something more neutral, but am not fussed
about it.

And I suppose "by the IOMMU" is not really acurate either.

How about

"MSI interrupts are not secure, they cannot be isolated by the
platform. Check that platform features like interrupt remapping are
enabled. Use the \"allow_unsafe_interrupts\" module parameter to override\n"

?

Thanks,
Jason

  reply	other threads:[~2022-12-08 14:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07 20:44 [PATCH 0/3] iommufd review updates Jason Gunthorpe
2022-12-07 20:44 ` [PATCH 1/3] iommufd: Fix comment typos Jason Gunthorpe
2022-12-08  4:26   ` Tian, Kevin
2022-12-08 14:08   ` Eric Auger
2022-12-07 20:44 ` [PATCH 2/3] iommufd: Improve a few unclear bits of code Jason Gunthorpe
2022-12-08  4:32   ` Tian, Kevin
2022-12-08 14:08   ` Eric Auger
2022-12-07 20:44 ` [PATCH 3/3] iommufd: Change the order of MSI setup Jason Gunthorpe
2022-12-08  6:06   ` Tian, Kevin
2022-12-08 12:22     ` Jason Gunthorpe
2022-12-08 14:18   ` Eric Auger
2022-12-08 14:35     ` Jason Gunthorpe [this message]
2022-12-08 15:02       ` Eric Auger
2022-12-09 19:27 ` [PATCH 0/3] iommufd review updates 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=Y5H2Qmz2bCXYHLA1@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=binbin.wu@linux.intel.com \
    --cc=eric.auger@redhat.com \
    --cc=iommu@lists.linux.dev \
    --cc=kevin.tian@intel.com \
    --cc=lixiao.yang@intel.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=nicolinc@nvidia.com \
    --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 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.