From: Dave Hansen <dave@sr71.net>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, tglx@linutronix.de
Subject: Re: [PATCH 00/19] x86, mpx updates for 4.2 (take 7)
Date: Tue, 26 May 2015 09:49:17 -0700 [thread overview]
Message-ID: <5564A40D.6010002@sr71.net> (raw)
In-Reply-To: <20150520100548.GA19925@gmail.com>
On 05/20/2015 03:05 AM, Ingo Molnar wrote:
>> >
>> > This sees breakage unless either booted with 'noxsaves'
>> > or if it has Fenghua's set from here applied:
>> >
>> > http://lkml.kernel.org/r/1429678319-61356-1-git-send-email-fenghua.yu@intel.com
>> >
>> > This set is also available against 4.1-rc3 in git:
>> >
>> > git://git.kernel.org/pub/scm/linux/kernel/git/daveh/x86-mpx.git mpx-v22
> Yeah, so as a first step, could you please test that the patch below
> solves the crashes as well, without having to specify 'noxsaves' on
> the boot line?
Yes, that does seem to make it happy in lieu of Fenghua's patches.
> + /*
> + * Quirk: we don't yet handle the XSAVES* instructions
> + * correctly, as we don't correctly convert between
> + * standard and compacted format when interfacing
> + * with user-space - so disable it for now.
> + *
> + * The difference is small: with recent CPUs the
> + * compacted format is only marginally smaller than
> + * the standard FPU state format.
> + *
> + * ( This is easy to backport while we are fixing
> + * XSAVES* support. )
> + */
> + setup_clear_cpu_cap(X86_FEATURE_XSAVES);
> }
FWIW, I think it would be prudent to also clear X86_FEATURE_XSAVEC.
All of the issues I am aware of are related to the compact format, not
'xsaves' itself (although 'xsaves' does *use* the compact format of course).
The XSAVEC bit is the one that technically indicates the compact format
support, although I don't think there is any actual use of it in the
kernel at present.
next prev parent reply other threads:[~2015-05-26 16:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 6:25 [PATCH 00/19] x86, mpx updates for 4.2 (take 7) Dave Hansen
2015-05-19 6:25 ` [PATCH 01/19] x86, mpx, xsave: Fix up bad get_xsave_addr() assumptions Dave Hansen
2015-05-19 6:25 ` [PATCH 03/19] x86, mpx: Use new get_xsave_field_ptr() Dave Hansen
2015-05-19 8:16 ` Thomas Gleixner
2015-05-19 6:25 ` [PATCH 02/19] x86, fpu: Wrap get_xsave_addr() to make it safer Dave Hansen
2015-05-19 8:15 ` Thomas Gleixner
2015-05-19 6:25 ` [PATCH 04/19] x86, mpx: Cleanup: Do not pass task around when unnecessary Dave Hansen
2015-05-19 8:16 ` Thomas Gleixner
2015-05-19 6:25 ` [PATCH 05/19] x86, mpx: remove redundant MPX_BNDCFG_ADDR_MASK Dave Hansen
2015-05-19 6:25 ` [PATCH 06/19] x86, mpx: Restrict mmap size check to bounds tables Dave Hansen
2015-05-19 6:25 ` [PATCH 07/19] x86, mpx: boot-time disable Dave Hansen
2015-05-19 6:25 ` [PATCH 10/19] x86, mpx: Trace the attempts to find bounds tables Dave Hansen
2015-05-19 8:17 ` Thomas Gleixner
2015-05-19 6:25 ` [PATCH 08/19] x86, mpx: trace #BR exceptions Dave Hansen
2015-05-19 6:25 ` [PATCH 11/19] x86, mpx: trace allocation of new bounds tables Dave Hansen
2015-05-19 6:25 ` [PATCH 09/19] x86, mpx: trace entry to bounds exception paths Dave Hansen
2015-05-19 8:17 ` Thomas Gleixner
2015-05-19 6:25 ` [PATCH 12/19] x86: make is_64bit_mm() widely available Dave Hansen
2015-05-19 6:25 ` [PATCH 13/19] x86, mpx: Add temporary variable to reduce masking Dave Hansen
2015-05-19 6:25 ` [PATCH 17/19] x86, mpx: rewrite unmap code Dave Hansen
2015-05-19 6:25 ` [PATCH 15/19] x86, mpx: do 32-bit-only cmpxchg for 32-bit apps Dave Hansen
2015-05-19 8:18 ` Thomas Gleixner
2015-05-19 6:25 ` [PATCH 14/19] x86, mpx: new directory entry to addr helper Dave Hansen
2015-05-19 6:25 ` [PATCH 16/19] x86, mpx: support 32-bit binaries on 64-bit kernel Dave Hansen
2015-05-19 8:21 ` Thomas Gleixner
2015-05-19 6:25 ` [PATCH 18/19] x86, mpx: do not count MPX VMAs as neighbors when unmapping Dave Hansen
2015-05-19 6:25 ` [PATCH 19/19] x86, mpx: allow mixed binaries again Dave Hansen
2015-05-20 10:05 ` [PATCH 00/19] x86, mpx updates for 4.2 (take 7) Ingo Molnar
2015-05-26 16:49 ` Dave Hansen [this message]
2015-05-27 12:18 ` Ingo Molnar
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=5564A40D.6010002@sr71.net \
--to=dave@sr71.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--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.