[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMzpN2iBk4bfFWyxrMtFanxxNAM9MYNXPZ3oQSmyBpQjuNP_Ug@mail.gmail.com>
Date: Wed, 29 Jun 2022 11:21:17 -0400
From: Brian Gerst <brgerst@...il.com>
To: Andy Lutomirski <luto@...nel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"the arch/x86 maintainers" <x86@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>,
"H . Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
"Eric W . Biederman" <ebiederm@...ssion.com>
Subject: Re: [PATCH 0/8] x86 signal code cleanups
On Tue, Jun 28, 2022 at 7:23 PM Andy Lutomirski <luto@...nel.org> wrote:
>
> On 6/6/22 13:37, Brian Gerst wrote:
> > The 32-bit signal code has significant differences from 64-bit, and
> > those are duplicated for native and compat modes. This patch series
> > merges the 32-bit code into one file, and does some general cleanups
> > in the x86 signal code. There should be no functional changes.
> >
>
> This looks generally sane. What kind of testing have you done?
I ran all of the self tests, did a parallel kernel build, and general
usage like web browsing. Do you have any suggestions for other tests?
--
Brian Gerst
Powered by blists - more mailing lists