[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5720F1D6.7020400@arm.com>
Date: Wed, 27 Apr 2016 18:07:34 +0100
From: Robin Murphy <robin.murphy@....com>
To: Pavel Machek <pavel@....cz>, Borislav Petkov <bp@...en8.de>
Cc: linux-efi@...r.kernel.org, kvm@...r.kernel.org,
Radim Krčmář <rkrcmar@...hat.com>,
Matt Fleming <matt@...eblueprint.co.uk>, x86@...nel.org,
linux-mm@...ck.org, Alexander Potapenko <glider@...gle.com>,
"H. Peter Anvin" <hpa@...or.com>, linux-arch@...r.kernel.org,
Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
kasan-dev@...glegroups.com, Ingo Molnar <mingo@...hat.com>,
Andrey Ryabinin <aryabinin@...tuozzo.com>,
Tom Lendacky <thomas.lendacky@....com>,
Arnd Bergmann <arnd@...db.de>,
Thomas Gleixner <tglx@...utronix.de>,
Dmitry Vyukov <dvyukov@...gle.com>,
linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org,
Paolo Bonzini <pbonzini@...hat.com>
Subject: Re: [RFC PATCH v1 02/18] x86: Secure Memory Encryption (SME) build
enablement
On 27/04/16 17:41, Pavel Machek wrote:
> On Wed 2016-04-27 17:41:40, Borislav Petkov wrote:
>> On Wed, Apr 27, 2016 at 05:30:10PM +0200, Pavel Machek wrote:
>>> Doing it early will break bisect, right?
>>
>> How exactly? Please do tell.
>
> Hey look, SME slowed down 30% since being initially merged into
> kernel!
As opposed to "well, bisection shows these n+1 complicated changes are
all fine and the crash is down to this Kconfig patch", presumably. I'm
sure we all love spending a whole afternoon only to find that, right? :P
Robin.
> Pavel
>
Powered by blists - more mailing lists