From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Dave Hansen <dave@sr71.net>, linux-kernel@vger.kernel.org
Cc: dave.hansen@linux.intel.com, x86@kernel.org,
qiaowei.ren@intel.com, fenghua.yu@intel.com
Subject: Re: [RFC][PATCH] x86 mpx: give bndX registers actual names
Date: Fri, 31 Oct 2014 14:50:10 -0700 [thread overview]
Message-ID: <54540412.4000405@linux.intel.com> (raw)
In-Reply-To: <20141031212237.30B94E08@viggo.jf.intel.com>
On 10/31/2014 02:22 PM, Dave Hansen wrote:
>
> -struct bndregs_struct {
> - u64 bndregs[8];
> +struct bndreg_struct {
> + u64 lb; /* lower bound */
> + u64 ub; /* upper bound */
> } __packed;
>
> struct bndcsr_struct {
> @@ -394,7 +395,7 @@ struct xsave_struct {
> struct xsave_hdr_struct xsave_hdr;
> struct ymmh_struct ymmh;
> struct lwp_struct lwp;
> - struct bndregs_struct bndregs;
> + struct bndreg_struct bnd[4];
> struct bndcsr_struct bndcsr;
> /* new processor state extensions will go here */
> } __attribute__ ((packed, aligned (64)));
> _
>
How about "struct bndreg"?
-hpa
prev parent reply other threads:[~2014-10-31 21:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 21:22 [RFC][PATCH] x86 mpx: give bndX registers actual names Dave Hansen
2014-10-31 21:50 ` H. Peter Anvin [this message]
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=54540412.4000405@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave@sr71.net \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qiaowei.ren@intel.com \
--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.