[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180222090929.12cc8344@jacob-builder>
Date: Thu, 22 Feb 2018 09:09:29 -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 Thu, 22 Feb 2018 08:48:37 +0100
Yves-Alexis Perez <corsac@...ian.org> wrote:
> On Tue, 2018-02-20 at 14:25 -0800, Jacob Pan wrote:
> > 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.
>
> Yes good indeed, I had forgot about that. Maybe the userland part is
> still useful, but there's definitely a need for (protected) access to
> privileged memory (and access to /dev/mem is less practical than
> debugfs, I guess).
>
Another reason we can't use /dev/mem is that the context entries are
not static, they are created for each device when the first map()
comes. So we need to rely on the list in the intel iommu driver to dump
the context.
> Regards,
[Jacob Pan]
Powered by blists - more mailing lists