[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dac081f7-d3f4-d81d-46e6-076f1e3f13a1@oracle.com>
Date: Thu, 12 Jul 2018 09:59:01 -0400
From: Boris Ostrovsky <boris.ostrovsky@...cle.com>
To: Thomas Backlund <tmb@...eia.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Joerg Roedel <joro@...tes.org>
Cc: Jiri Kosina <jikos@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>, Peter Anvin <hpa@...or.com>,
the arch/x86 maintainers <x86@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>,
Andrew Lutomirski <luto@...nel.org>,
Dave Hansen <dave.hansen@...el.com>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Jürgen Groß <jgross@...e.com>,
Peter Zijlstra <peterz@...radead.org>,
Borislav Petkov <bp@...en8.de>,
Brian Gerst <brgerst@...il.com>,
David Laight <David.Laight@...lab.com>,
Denys Vlasenko <dvlasenk@...hat.com>,
Eduardo Valentin <eduval@...zon.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH 00/39 v7] PTI support for x86-32
On 07/11/2018 03:57 PM, Thomas Backlund wrote:
> Den 2018-07-11 kl. 20:28, skrev Jiri Kosina:
>> On Wed, 11 Jul 2018, Linus Torvalds wrote:
>>
>>> It's the testing that worries me most. Pretty much no developers run
>>> 32-bit any more, and I'd be most worried about the odd interactions
>>> that
>>> might be hw-specific. Some crazy EFI mapping setup or the similar odd
>>> case that simply requires a particular configuration or setup.
>>>
>>> But I guess those issues will never be found until we just spring this
>>> all on the unsuspecting public.
>>
>> FWIW we shipped Joerg's 32bit KAISER kernel out to our 32bit users
>> (on old
>> product where we still support it) on Apr 25th already (and some issues
>> have been identified since then because of that). So it (or its port to
>> 3.0, to be more precise :p) already did receive some crowd-testing.
>>
>
> And Mageia has had v2 since February 13th patched into 4.14 -longterm,
> then updated to v3 at March 5th, and updated to v4 at March 19th and
> been running that since then (since v5 is rebased on v4.17 we stayed
> with v4)
>
>
> So, here is another "lets merge it upstream" vote :)
I had a quick boot test for Xen (PV and HVM) and they both looked OK. I
didn't boot all the way to login prompt but that's most likely due to
issues in my environment -- I haven't tried this image in a year or so
and my other setup is offline right now.
-boris
Powered by blists - more mailing lists