Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: "Patel, Nirmal" <nirmal.patel@linux.intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>, linux-pci@vger.kernel.org
Subject: Re: [PATCH v3 1/2] PCI: vmd: Assign VMD IRQ domain before enumeration
Date: Thu, 28 Apr 2022 09:40:41 +0100	[thread overview]
Message-ID: <20220428084041.GA15506@lpieralisi> (raw)
In-Reply-To: <b2b73869-9889-a70f-73a9-bb7215ab7daf@linux.intel.com>

On Wed, Apr 27, 2022 at 07:21:08PM -0700, Patel, Nirmal wrote:
> On 4/5/2022 10:10 AM, Nirmal Patel wrote:
> > 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>
> > ---
> > v2->v3: Update commit log.
> > v1->v2: Split patch into two separate patches. One applies the fix and
> > 	other reverts the commit 2565e5b69c44 which was added as a
> > 	workaround.
> > ---
> >  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 reminder.

Instead of sending these reminders, could you please, as Bjorn
requested, fix your patch posting flow to make sure your patches are
logged in lore and patchwork/linux-pci, where I look for patches to
review please ?

There is no point in sending reminders for something I don't see,
I have no idea you are waiting for me to review this series if it
does not show up in patchwork/linux-pci, if it is not there for
me it does not exist.

Thanks,
Lorenzo



      reply	other threads:[~2022-04-28  8:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220405171005.45586-1-nirmal.patel@linux.intel.com>
2022-04-28  2:21 ` [PATCH v3 1/2] PCI: vmd: Assign VMD IRQ domain before enumeration Patel, Nirmal
2022-04-28  8:40   ` 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=20220428084041.GA15506@lpieralisi \
    --to=lorenzo.pieralisi@arm.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=nirmal.patel@linux.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