On 01/31/2013 12:52 PM, Alex Williamson wrote:
> On Thu, 2013-01-31 at 22:00 +0200, Gleb Natapov wrote:
>> On Thu, Jan 31, 2013 at 02:34:27PM -0500, Don Zickus wrote:
>>> On Thu, Jan 31, 2013 at 08:52:00PM +0200, Gleb Natapov wrote:
>
On 01/31/2013 12:52 PM, Alex Williamson wrote:
On Thu, 2013-01-31 at 22:00 +0200, Gleb Natapov wrote:
On Thu, Jan 31, 2013 at 02:34:27PM -0500, Don Zickus wrote:
On Thu, Jan 31, 2013 at 08:52:00PM +0200, Gleb Natapov wrote:
On Thu, 2013-01-31 at 22:00 +0200, Gleb Natapov wrote:
> On Thu, Jan 31, 2013 at 02:34:27PM -0500, Don Zickus wrote:
> > On Thu, Jan 31, 2013 at 08:52:00PM +0200, Gleb Natapov wrote:
> > > > http://www.invisiblethingslab.com/resources/2011/Software%20Attacks%20on%20Intel%20VT-d.pdf
> > > >
> > >
On Thu, Jan 31, 2013 at 02:34:27PM -0500, Don Zickus wrote:
> On Thu, Jan 31, 2013 at 08:52:00PM +0200, Gleb Natapov wrote:
> > > http://www.invisiblethingslab.com/resources/2011/Software%20Attacks%20on%20Intel%20VT-d.pdf
> > >
> > > After talking with folks, the threat of irq injections on
On Thu, Jan 31, 2013 at 08:52:00PM +0200, Gleb Natapov wrote:
> > http://www.invisiblethingslab.com/resources/2011/Software%20Attacks%20on%20Intel%20VT-d.pdf
> >
> > After talking with folks, the threat of irq injections on virtual guests
> > made sense. However, when discussing if this was
On Thu, Jan 31, 2013 at 11:40:35AM -0500, Don Zickus wrote:
> In commit "41750d3 x86, x2apic: Enable the bios request for x2apic optout"
> it was explained how OEMs are trying to opt out of using x2apics.
>
> That commit moved code around and screamed with a WARN if the BIOS
> opted out of x2apic
In commit "41750d3 x86, x2apic: Enable the bios request for x2apic optout"
it was explained how OEMs are trying to opt out of using x2apics.
That commit moved code around and screamed with a WARN if the BIOS
opted out of x2apic mode. Fair enough.
This code hit our RHEL distro and OEMs started
In commit 41750d3 x86, x2apic: Enable the bios request for x2apic optout
it was explained how OEMs are trying to opt out of using x2apics.
That commit moved code around and screamed with a WARN if the BIOS
opted out of x2apic mode. Fair enough.
This code hit our RHEL distro and OEMs started
On Thu, Jan 31, 2013 at 11:40:35AM -0500, Don Zickus wrote:
In commit 41750d3 x86, x2apic: Enable the bios request for x2apic optout
it was explained how OEMs are trying to opt out of using x2apics.
That commit moved code around and screamed with a WARN if the BIOS
opted out of x2apic mode.
On Thu, Jan 31, 2013 at 08:52:00PM +0200, Gleb Natapov wrote:
http://www.invisiblethingslab.com/resources/2011/Software%20Attacks%20on%20Intel%20VT-d.pdf
After talking with folks, the threat of irq injections on virtual guests
made sense. However, when discussing if this was possible on
On Thu, Jan 31, 2013 at 02:34:27PM -0500, Don Zickus wrote:
On Thu, Jan 31, 2013 at 08:52:00PM +0200, Gleb Natapov wrote:
http://www.invisiblethingslab.com/resources/2011/Software%20Attacks%20on%20Intel%20VT-d.pdf
After talking with folks, the threat of irq injections on virtual guests
On Thu, 2013-01-31 at 22:00 +0200, Gleb Natapov wrote:
On Thu, Jan 31, 2013 at 02:34:27PM -0500, Don Zickus wrote:
On Thu, Jan 31, 2013 at 08:52:00PM +0200, Gleb Natapov wrote:
http://www.invisiblethingslab.com/resources/2011/Software%20Attacks%20on%20Intel%20VT-d.pdf
After talking
12 matches
Mail list logo