From: Ren Qiaowei <qiaowei.ren@intel.com>
To: Dave Hansen <dave.hansen@intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/3] x86, mpx: add documentation on Intel MPX
Date: Thu, 27 Feb 2014 09:58:30 +0800 [thread overview]
Message-ID: <530E9BC6.5090207@intel.com> (raw)
In-Reply-To: <530E5A7D.9060902@intel.com>
On 02/27/2014 05:19 AM, Dave Hansen wrote:
> On 02/23/2014 05:27 AM, Qiaowei Ren wrote:
>> +The other case that generates a #BR is when a BNDSTX instruction
>> +attempts to save bounds to a BD entry marked as invalid. This is
>> +an indication that no BT exists for this entry. In this case the
>> +fault handler will allocate a new BT.
>
> Hi Qiaowei,
>
> Can you make an effort to move these comments over to the code? The
> bounds-table allocation function is a much more appropriate place for
> this text than the Documentation/ file.
>
Ok. They will be moved.
Thanks,
Qiaowei
next prev parent reply other threads:[~2014-02-27 2:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 13:27 [PATCH v5 0/3] Intel MPX support Qiaowei Ren
2014-02-23 13:27 ` [PATCH v5 1/3] x86, mpx: add documentation on Intel MPX Qiaowei Ren
2014-02-26 19:17 ` Dave Hansen
2014-02-26 20:58 ` Dave Hansen
2014-02-26 21:44 ` H. Peter Anvin
2014-02-27 2:03 ` Ren Qiaowei
2014-02-26 21:19 ` Dave Hansen
2014-02-27 1:58 ` Ren Qiaowei [this message]
2014-02-23 13:27 ` [PATCH v5 2/3] x86, mpx: hook #BR exception handler to allocate bound tables Qiaowei Ren
2014-02-24 17:27 ` Dave Hansen
2014-02-24 17:51 ` H. Peter Anvin
2014-02-25 13:34 ` Ren, Qiaowei
2014-02-23 13:27 ` [PATCH v5 3/3] x86, mpx: extend siginfo structure to include bound violation information Qiaowei Ren
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=530E9BC6.5090207@intel.com \
--to=qiaowei.ren@intel.com \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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.