[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180220142512.039309aa@jacob-builder>
Date: Tue, 20 Feb 2018 14:25:12 -0800
From: Jacob Pan <jacob.jun.pan@...ux.intel.com>
To: Yves-Alexis Perez <corsac@...ian.org>
Cc: "Raj, Ashok" <ashok.raj@...el.com>, Joerg Roedel <joro@...tes.org>,
Sohil Mehta <sohil.mehta@...el.com>,
Alex Williamson <alex.williamson@...hat.com>,
David Woodhouse <dwmw2@...radead.org>,
iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
Gayatri Kammela <gayatri.kammela@...el.com>,
Ravi V Shankar <ravi.v.shankar@...el.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Lu Baolu <baolu.lu@...ux.intel.com>,
Fenghua Yu <fenghua.yu@...el.com>,
jacob.jun.pan@...ux.intel.com
Subject: Re: [PATCH v7 0/5] Add Intel IOMMU debugfs support
On Sun, 18 Feb 2018 23:15:32 +0100
Yves-Alexis Perez <corsac@...ian.org> wrote:
> On Tue, 2018-02-13 at 13:40 -0800, Raj, Ashok wrote:
> > This version has only hw dumps for now, but we plan to add some
> > other things like walking 2nd level page-tables, or get some SVM
> > specific data from the driver in the future.
>
> Hi,
>
> I'm not sure how much you know about chipsec [1], but with a oneliner
> [2] you can have it print a lot of data from Vt-d configuration,
> including page tables. As far as I remember, it doesn't need access
> to /dev/mem (but I gidn't dig to check how it does it).
>
> It might still be useful to have everything from debugfs because
> it'll always be consistent with the current running kernel, but at
> least it might help users reporting bugs.
>
> [1] https://github.com/chipsec/chipsec
> [2] http://paste.debian.net/1010105
I didn't know about chipsec but reading the code seems to rely on an
out-of-tree kernel module. I don't think it matches what we need here.
Powered by blists - more mailing lists