From: Dave Hansen <dave.hansen@intel.com>
To: "Yu, Fenghua" <fenghua.yu@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: xsaves support broken?
Date: Mon, 02 Mar 2015 16:24:12 -0800 [thread overview]
Message-ID: <54F4FF2C.7030200@intel.com> (raw)
In-Reply-To: <3E5A0FA7E9CA944F9D5414FEC6C712205A7061FB@ORSMSX106.amr.corp.intel.com>
On 03/02/2015 04:09 PM, Yu, Fenghua wrote:
> Xsaves has been tested by QA since 3.17 with or without MPX. I'm not
> aware of reported issues.
>
> But MPX is the only code to call the get_xsave_addr kernel API.
> Though it has been tested before on upstream MPX code.
Has it? I'm fairly sure I've never explicitly tested it. I'm also
doubting now that I've *ever* seen it work without booting with 'noxsaves'.
> What changes in your new MPX code?
I just discovered it when adding a new feature. I actually backed out
all of my changes before reporting this issue. I'm running a completely
untouched 4.0-rc1 kernel with the config I attached a moment ago.
If I boot with 'noxsaves', MPX works fine. If I boot without it, the
kernel never sees the values that userspace sets in the "bndcsr" register.
next prev parent reply other threads:[~2015-03-03 0:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 23:59 xsaves support broken? Dave Hansen
2015-03-03 0:09 ` Yu, Fenghua
2015-03-03 0:24 ` Dave Hansen [this message]
2015-03-03 0:34 ` Yu, Fenghua
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=54F4FF2C.7030200@intel.com \
--to=dave.hansen@intel.com \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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.