From: "Patel, Nirmal" <nirmal.patel@linux.intel.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
linux-pci@vger.kernel.org,
Jon Derrick <jonathan.derrick@linux.dev>,
Nirmal Patel <nirmal.patel@intel.com>
Subject: Re: [PATCH v2 1/2] PCI: vmd: Assign VMD IRQ domain before enumeration
Date: Tue, 29 Mar 2022 15:47:44 -0700 [thread overview]
Message-ID: <6b2b0c52-4b01-db11-1c89-ab291ae633b3@linux.intel.com> (raw)
In-Reply-To: <20220316155103.8415-1-nirmal.patel@intel.com>
On 3/16/2022 8:51 AM, Nirmal Patel wrote:
> From: Nirmal Patel <nirmal.patel@linux.intel.com>
>
> VMD creates and assigns a separate IRQ domain only when MSI remapping is
> enabled. For example VMD-MSI. But VMD doesn't assign IRQ domain when
> MSI remapping is disabled resulting child devices getting default
> PCI-MSI IRQ domain. Now when interrupt remapping is enabled by
> intel-iommu all the PCI devices are assigned INTEL-IR-MSI domain
> including VMD endpoints. But devices behind VMD get PCI-MSI IRQ domain
> when VMD create a root bus and configures child devices.
>
> As a result DMAR errors were observed when interrupt remapping was
> enabled on Intel Icelake CPUs. For instance:
>
> DMAR: DRHD: handling fault status reg 2
> DMAR: [INTR-REMAP] Request device [0xe2:0x00.0] fault index 0xa00 [fault reason 0x25] Blocked a compatibility format interrupt request
>
> Acked-by: Dan Williams <dan.j.williams@intel.com>
> Signed-off-by: Nirmal Patel <nirmal.patel@linux.intel.com>
> ---
> drivers/pci/controller/vmd.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/pci/controller/vmd.c b/drivers/pci/controller/vmd.c
> index cc166c683638..3a6570e5b765 100644
> --- a/drivers/pci/controller/vmd.c
> +++ b/drivers/pci/controller/vmd.c
> @@ -853,6 +853,8 @@ static int vmd_enable_domain(struct vmd_dev *vmd, unsigned long features)
> vmd_attach_resources(vmd);
> if (vmd->irq_domain)
> dev_set_msi_domain(&vmd->bus->dev, vmd->irq_domain);
> + else
> + dev_set_msi_domain(&vmd->bus->dev, dev_get_msi_domain(&vmd->dev->dev));
>
> vmd_acpi_begin();
>
Gentle ping!
Thanks
nirmal
next parent reply other threads:[~2022-03-29 22:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220316155103.8415-1-nirmal.patel@intel.com>
2022-03-29 22:47 ` Patel, Nirmal [this message]
2022-03-29 23:27 ` [PATCH v2 1/2] PCI: vmd: Assign VMD IRQ domain before enumeration Dan Williams
2022-03-30 15:54 ` Patel, Nirmal
2022-03-30 17:54 ` Bjorn Helgaas
2022-03-30 18:06 ` Patel, Nirmal
2022-03-30 18:20 ` Bjorn Helgaas
[not found] ` <20220316155103.8415-2-nirmal.patel@intel.com>
2022-03-29 22:48 ` [PATCH v2 2/2] Allow VMD to disable MSIX remapping with interrupt remapping enabled Patel, Nirmal
2022-03-30 17:49 ` Bjorn Helgaas
2022-03-30 18:07 ` Patel, Nirmal
2022-05-11 9:57 [PATCH v2 0/2] PCI: vmd: IRQ domain assignment to sub devices Nirmal Patel
2022-05-11 9:57 ` [PATCH v2 1/2] PCI: vmd: Assign VMD IRQ domain before enumeration Nirmal Patel
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=6b2b0c52-4b01-db11-1c89-ab291ae633b3@linux.intel.com \
--to=nirmal.patel@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=jonathan.derrick@linux.dev \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--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).