[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <EFBC6B60-D0EC-4518-A38E-076D3933AA0E@amacapital.net>
Date: Tue, 26 Nov 2019 14:30:10 -0800
From: Andy Lutomirski <luto@...capital.net>
To: Borislav Petkov <bp@...en8.de>
Cc: Barret Rhoden <brho@...gle.com>, austin@...gle.com,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Rik van Riel <riel@...riel.com>, x86@...nel.org,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>
Subject: Re: AVX register corruption from signal delivery
> On Nov 26, 2019, at 2:14 PM, Borislav Petkov <bp@...en8.de> wrote:
>
> On Tue, Nov 26, 2019 at 04:23:40PM -0500, Barret Rhoden wrote:
>> Thanks; config attached. I've been able to recreate it in QEMU with at
>> least 2 cores.
>
> Yap, I can too, in my VM.
>
> Btw, would you guys like to submit that reproducer test program
>
> https://bugzilla.kernel.org/attachment.cgi?id=286073
>
> into the kernel selftests pile here:
>
> tools/testing/selftests/x86/
>
> ?
>
> It needs proper cleanup to fit kernel coding style but it could be a
> good start for collecting interesting FPU test cases.
If we do this, we should have selftests/x86/slow or otherwise have a fast vs slow mode. I really like that the entire suite takes under 2s.
Powered by blists - more mailing lists