From: Andi Kleen <andi@firstfloor.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Andi Kleen <andi@firstfloor.org>,
x86@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [v8, 4/5] x86/xsave: Make XSAVE check the base CPUID features before enabling
Date: Mon, 13 Nov 2017 17:28:05 -0800 [thread overview]
Message-ID: <20171114012805.GD2482@two.firstfloor.org> (raw)
In-Reply-To: <20171112064148.GL8522@tassilo.jf.intel.com>
Guenter,
Do you have a command line that reproduces it and the exact log
output?
I can't reproduce it here with different qemu settings.
-Andi
next prev parent reply other threads:[~2017-11-14 1:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 21:52 Support generic disabling of all XSAVE features Andi Kleen
2017-10-05 21:52 ` [PATCH v8 1/5] x86/xsave: Move xsave initialization to after parsing early parameters Andi Kleen
2017-10-05 21:52 ` [PATCH v8 2/5] x86/cpuid: Add generic table for cpuid dependencies Andi Kleen
2017-10-05 22:41 ` Thomas Gleixner
2017-10-05 23:08 ` Andi Kleen
2017-10-05 23:34 ` Andi Kleen
2017-10-05 21:52 ` [PATCH v8 3/5] x86/cpuid: Make clearcpuid an early param Andi Kleen
2017-10-05 21:52 ` [PATCH v8 4/5] x86/xsave: Make XSAVE check the base CPUID features before enabling Andi Kleen
2017-11-11 23:15 ` [v8, " Guenter Roeck
2017-11-12 6:41 ` Andi Kleen
2017-11-14 1:28 ` Andi Kleen [this message]
2017-11-14 1:49 ` Guenter Roeck
2017-11-16 19:03 ` Andi Kleen
2017-11-16 22:13 ` Guenter Roeck
2017-11-14 2:33 ` Guenter Roeck
2019-06-29 15:22 ` [PATCH v8 " Vegard Nossum
2019-07-01 12:17 ` Sebastian Andrzej Siewior
2019-07-01 16:41 ` Andi Kleen
2019-07-01 16:39 ` Andi Kleen
2017-10-05 21:52 ` [PATCH v8 5/5] x86/xsave: Remove the explicit clearing of XSAVE dependend features Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171114012805.GD2482@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.