[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171020193953.7814f013@alans-desktop>
Date: Fri, 20 Oct 2017 19:39:53 +0100
From: Alan Cox <gnomes@...rguk.ukuu.org.uk>
To: Brijesh Singh <brijesh.singh@....com>
Cc: x86@...nel.org, kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
Borislav Petkov <bp@...en8.de>,
Tom Lendacky <thomas.lendacky@....com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, Borislav Petkov <bp@...e.de>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
David Laight <David.Laight@...LAB.COM>,
Arnd Bergmann <arnd@...db.de>
Subject: Re: [Part1 PATCH v7 13/17] x86/io: Unroll string I/O when SEV is
active
On Fri, 20 Oct 2017 09:30:55 -0500
Brijesh Singh <brijesh.singh@....com> wrote:
> From: Tom Lendacky <thomas.lendacky@....com>
>
> Secure Encrypted Virtualization (SEV) does not support string I/O, so
> unroll the string I/O operation into a loop operating on one element at
> a time.
Does this also mean that any firmware running in the virtual machine
(EFI, BIOS, VGA etc) has to be patched and if so shouldn't that be
documented somewhere ?
Alan
Powered by blists - more mailing lists