[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190911103726.GB21988@8bytes.org>
Date: Wed, 11 Sep 2019 12:37:27 +0200
From: "joro@...tes.org" <joro@...tes.org>
To: "Mehta, Sohil" <sohil.mehta@...el.com>
Cc: "Park, Kyung Min" <kyung.min.park@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Raj, Ashok" <ashok.raj@...el.com>,
"Lu, Baolu" <baolu.lu@...el.com>,
"Shevchenko, Andriy" <andriy.shevchenko@...el.com>,
"dwmw2@...radead.org" <dwmw2@...radead.org>,
"iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
"jacob.jun.pan@...ux.intel.com" <jacob.jun.pan@...ux.intel.com>
Subject: Re: [PATCH] iommu/vt-d: Add Scalable Mode fault information
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.
Powered by blists - more mailing lists