[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1363750040.24132.483.camel@bling.home>
Date: Tue, 19 Mar 2013 21:27:20 -0600
From: Alex Williamson <alex.williamson@...hat.com>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Matthew Garrett <matthew.garrett@...ula.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-security-module@...r.kernel.org"
<linux-security-module@...r.kernel.org>,
"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
"kexec@...ts.infradead.org" <kexec@...ts.infradead.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Subject: Re: [PATCH 01/12] Security: Add CAP_COMPROMISE_KERNEL
On Tue, 2013-03-19 at 20:22 -0700, H. Peter Anvin wrote:
> On 03/19/2013 08:18 PM, Alex Williamson wrote:
> >>
> >> The "pinning" process needs to involve a call to the kernel to process
> >> the page for DMA (pinning the page and opening it in the iommu) and
> >> return a transaction address, of course.
> >>
> >> I think we have the interface for that in vfio, but I haven't followed
> >> that work.
> >
> > Yes, vfio does this and is meant to provide a secure-boot-friendly PCI
> > passthrough interface. Thanks,
> >
>
> Right, and presumably vfio does *not* require CAP_SYS_RAWIO, right?
Correct
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists