From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: linux-pci@vger.kernel.org,
Jon Derrick <jonathan.derrick@intel.com>,
iommu@lists.linux-foundation.org
Cc: Krzysztof Wilczynski <kw@linux.com>,
Nirmal Patel <nirmal.patel@intel.com>,
Kapil Karkra <kapil.karkra@intel.com>,
Bjorn Helgaas <helgaas@kernel.org>
Subject: Re: [PATCH v4 0/2] VMD MSI Remapping Bypass
Date: Mon, 22 Mar 2021 14:11:00 +0000 [thread overview]
Message-ID: <161642217049.2836.9881489151722165383.b4-ty@arm.com> (raw)
In-Reply-To: <20210210161315.316097-1-jonathan.derrick@intel.com>
On Wed, 10 Feb 2021 09:13:13 -0700, Jon Derrick wrote:
> The Intel Volume Management Device acts similar to a PCI-to-PCI bridge in that
> it changes downstream devices' requester-ids to its own. As VMD supports PCIe
> devices, it has its own MSI-X table and transmits child device MSI-X by
> remapping child device MSI-X and handling like a demultiplexer.
>
> Some newer VMD devices (Icelake Server) have an option to bypass the VMD MSI-X
> remapping table. This allows for better performance scaling as the child device
> MSI-X won't be limited by VMD's MSI-X count and IRQ handler.
>
> [...]
Applied to pci/vmd, thanks!
[1/2] iommu/vt-d: Use Real PCI DMA device for IRTE
https://git.kernel.org/lpieralisi/pci/c/9b4a824b88
[2/2] PCI: vmd: Disable MSI-X remapping when possible
https://git.kernel.org/lpieralisi/pci/c/ee81ee84f8
Thanks,
Lorenzo
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
prev parent reply other threads:[~2021-03-22 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 16:13 [PATCH v4 0/2] VMD MSI Remapping Bypass Jon Derrick
2021-02-10 16:13 ` [PATCH v4 1/2] iommu/vt-d: Use Real PCI DMA device for IRTE Jon Derrick
2021-02-10 16:13 ` [PATCH v4 2/2] PCI: vmd: Disable MSI-X remapping when possible Jon Derrick
2021-03-17 19:14 ` [PATCH v4 0/2] VMD MSI Remapping Bypass Derrick, Jonathan
2021-03-18 9:07 ` joro
2021-03-18 12:38 ` Lorenzo Pieralisi
2021-03-22 14:11 ` Lorenzo Pieralisi [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=161642217049.2836.9881489151722165383.b4-ty@arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=helgaas@kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jonathan.derrick@intel.com \
--cc=kapil.karkra@intel.com \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=nirmal.patel@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;
as well as URLs for NNTP newsgroup(s).