From: Huang Adrian <adrianhuang0701@gmail.com>
To: Jon Derrick <jonathan.derrick@intel.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Rob Herring <robh@kernel.org>, "kw@linux.com" <kw@linux.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Nirmal Patel <nirmal.patel@linux.intel.com>,
Joerg Roedel <jroedel@suse.de>,
Adrian Huang <ahuang12@lenovo.com>
Subject: Re: [PATCH 1/1] PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
Date: Fri, 1 Oct 2021 15:51:49 +0800 [thread overview]
Message-ID: <CAHKZfL2pGNqj2j_VHyJG_tZ531SO4fuaEVvQrUWMF2Dnp_icGg@mail.gmail.com> (raw)
In-Reply-To: <5120b110-693a-79d3-2793-ac53c036897f@intel.com>
Hi,
On Wed, Sep 1, 2021 at 11:18 PM Jon Derrick <jonathan.derrick@intel.com> wrote:
>
> Thank you Adrian
>
> On 9/1/21 6:40 AM, Adrian Huang wrote:
> > From: Adrian Huang <ahuang12@lenovo.com>
> >
> > When enabling VMD in BIOS setup (Ice Lake Processor: Whitley platform),
> > the host OS cannot boot successfully with the following error message:
> >
> > nvme nvme0: I/O 12 QID 0 timeout, completion polled
> > nvme nvme0: Shutdown timeout set to 6 seconds
> > DMAR: DRHD: handling fault status reg 2
> > DMAR: [INTR-REMAP] Request device [0x00:0x00.5] fault index 0xa00 [fault reason 0x25] Blocked a compatibility format interrupt request
>
> I know we'd really prefer to support interrupt remapping with the VMD feature,
> and I'm not certain how EIME differs from the interrupt remapping modes that
> were tested while developing the VMD feature.
>
> I think this will have to be acceptable for now.
>
> Reviewed-by: Jon Derrick <jonathan.derrick@intel.com>
>
Gentle ping. Any comments about this patch (with Jon's Reviewed-by)?
-- Adrian
next prev parent reply other threads:[~2021-10-01 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 12:40 [PATCH 1/1] PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU Adrian Huang
2021-09-01 15:17 ` Jon Derrick
2021-10-01 7:51 ` Huang Adrian [this message]
2021-10-12 13:54 ` Lorenzo Pieralisi
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=CAHKZfL2pGNqj2j_VHyJG_tZ531SO4fuaEVvQrUWMF2Dnp_icGg@mail.gmail.com \
--to=adrianhuang0701@gmail.com \
--cc=ahuang12@lenovo.com \
--cc=bhelgaas@google.com \
--cc=jonathan.derrick@intel.com \
--cc=jroedel@suse.de \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=nirmal.patel@linux.intel.com \
--cc=robh@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).