From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f71.google.com (mail-wm0-f71.google.com [74.125.82.71]) by kanga.kvack.org (Postfix) with ESMTP id 659BC6B000A for ; Wed, 11 Jul 2018 15:56:17 -0400 (EDT) Received: by mail-wm0-f71.google.com with SMTP id s5-v6so2533208wmc.9 for ; Wed, 11 Jul 2018 12:56:17 -0700 (PDT) Received: from mx1.yrkesakademin.fi (mx1.yrkesakademin.fi. [85.134.45.194]) by mx.google.com with ESMTPS id n186-v6si1924304wmf.112.2018.07.11.12.56.15 for (version=TLS1_2 cipher=AES128-GCM-SHA256 bits=128/128); Wed, 11 Jul 2018 12:56:16 -0700 (PDT) Subject: Re: [PATCH 00/39 v7] PTI support for x86-32 References: <1531308586-29340-1-git-send-email-joro@8bytes.org> From: Thomas Backlund Message-ID: <1225b274-534b-cc32-54eb-aba89efba494@mageia.org> Date: Wed, 11 Jul 2018 22:56:18 +0259 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Linus Torvalds , Joerg Roedel Cc: Jiri Kosina , Thomas Gleixner , Ingo Molnar , Peter Anvin , the arch/x86 maintainers , Linux Kernel Mailing List , linux-mm , Andrew Lutomirski , Dave Hansen , Josh Poimboeuf , =?UTF-8?B?SsO8cmdlbiBHcm/Dnw==?= , Peter Zijlstra , Borislav Petkov , Boris Ostrovsky , Brian Gerst , David Laight , Denys Vlasenko , Eduardo Valentin , Greg Kroah-Hartman 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 :) -- Thomas