From: "joro@8bytes.org" <joro@8bytes.org>
To: "Mehta, Sohil" <sohil.mehta@intel.com>
Cc: "Shevchenko, Andriy" <andriy.shevchenko@intel.com>,
"Lu, Baolu" <baolu.lu@intel.com>,
"Park, Kyung Min" <kyung.min.park@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"Raj, Ashok" <ashok.raj@intel.com>
Subject: Re: [PATCH] iommu/vt-d: Add Scalable Mode fault information
Date: Wed, 11 Sep 2019 12:37:27 +0200 [thread overview]
Message-ID: <20190911103726.GB21988@8bytes.org> (raw)
In-Reply-To: <1568136807.58430.11.camel@intel.com>
On Tue, Sep 10, 2019 at 05:30:09PM +0000, Mehta, Sohil wrote:
> On Tue, 2019-09-10 at 10:08 +0200, Joerg Roedel wrote:
> > > + "Unknown", "Unknown", "Unknown", "Unknown", "Unknown",
> > "Unknown", "Unknown", /* 0x49-0x4F */
> >
> > Maybe add the number (0x49-0x4f) to the respecting "Unknown" fields?
> > If
> > we can't give a reason we should give the number for easier debugging
> > in
> > the future. Same for the "Unknown" fields below.
>
> I believe a fault number is always printed in dmar_fault_do_one() even
> if the reason is unknown.
>
> DMAR: [DMA Write] Request device [00:02.0] fault addr 108a000 [fault
> reason 23] Unknown
Right, applied the patch, thanks.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: "joro@8bytes.org" <joro@8bytes.org>
To: "Mehta, Sohil" <sohil.mehta@intel.com>
Cc: "Park, Kyung Min" <kyung.min.park@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Raj, Ashok" <ashok.raj@intel.com>,
"Lu, Baolu" <baolu.lu@intel.com>,
"Shevchenko, Andriy" <andriy.shevchenko@intel.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"jacob.jun.pan@linux.intel.com" <jacob.jun.pan@linux.intel.com>
Subject: Re: [PATCH] iommu/vt-d: Add Scalable Mode fault information
Date: Wed, 11 Sep 2019 12:37:27 +0200 [thread overview]
Message-ID: <20190911103726.GB21988@8bytes.org> (raw)
In-Reply-To: <1568136807.58430.11.camel@intel.com>
On Tue, Sep 10, 2019 at 05:30:09PM +0000, Mehta, Sohil wrote:
> On Tue, 2019-09-10 at 10:08 +0200, Joerg Roedel wrote:
> > > + "Unknown", "Unknown", "Unknown", "Unknown", "Unknown",
> > "Unknown", "Unknown", /* 0x49-0x4F */
> >
> > Maybe add the number (0x49-0x4f) to the respecting "Unknown" fields?
> > If
> > we can't give a reason we should give the number for easier debugging
> > in
> > the future. Same for the "Unknown" fields below.
>
> I believe a fault number is always printed in dmar_fault_do_one() even
> if the reason is unknown.
>
> DMAR: [DMA Write] Request device [00:02.0] fault addr 108a000 [fault
> reason 23] Unknown
Right, applied the patch, thanks.
next prev parent reply other threads:[~2019-09-11 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 18:14 [PATCH] iommu/vt-d: Add Scalable Mode fault information Kyung Min Park
2019-09-06 18:14 ` Kyung Min Park
2019-09-10 8:08 ` Joerg Roedel
2019-09-10 8:08 ` Joerg Roedel
2019-09-10 17:30 ` Mehta, Sohil
2019-09-10 17:30 ` Mehta, Sohil
2019-09-11 10:37 ` joro [this message]
2019-09-11 10:37 ` joro
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=20190911103726.GB21988@8bytes.org \
--to=joro@8bytes.org \
--cc=andriy.shevchenko@intel.com \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=kyung.min.park@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sohil.mehta@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.