[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0b58fa72-73f1-b3d8-73e9-254f42f0fa08@intel.com>
Date: Wed, 27 Feb 2019 14:30:47 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Yu-cheng Yu <yu-cheng.yu@...el.com>, linux-kernel@...r.kernel.org,
x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, linux-kselftest@...r.kernel.org
Cc: Andy Lutomirski <luto@...nel.org>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Ingo Molnar <mingo@...nel.org>, Shuah Khan <shuah@...nel.org>
Subject: Re: [PATCH] x86/selftests/xsave: Introduce XSAVE tests
On 2/27/19 2:19 PM, Yu-cheng Yu wrote:
> I am hoping that, should any test fail, one can easily modify the test to find
> out why.
Yeah, but that's what error messages are for. If we did this for
protection_keys, we would have about 30 .c files. :)
Powered by blists - more mailing lists