All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ren, Qiaowei" <qiaowei.ren@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>,
	"Hansen, Dave" <dave.hansen@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>
Cc: "x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v5 2/3] x86, mpx: hook #BR exception handler to allocate bound tables
Date: Tue, 25 Feb 2014 13:34:24 +0000	[thread overview]
Message-ID: <9E0BE1322F2F2246BD820DA9FC397ADE0151FC9E@SHSMSX102.ccr.corp.intel.com> (raw)
In-Reply-To: <530B86A5.6060100@zytor.com>


> -----Original Message-----
> From: H. Peter Anvin [mailto:hpa@zytor.com]
> Sent: Tuesday, February 25, 2014 1:52 AM
> To: Hansen, Dave; Ren, Qiaowei; Thomas Gleixner; Ingo Molnar
> Cc: x86@kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v5 2/3] x86, mpx: hook #BR exception handler to allocate
> bound tables
> 
> On 02/24/2014 09:27 AM, Dave Hansen wrote:
> >
> > Can you talk a little bit about what the design is here?  Why does the
> > kernel have to do the allocation of the virtual address space?  Does
> > it really need to MAP_POPULATE?  bt_size looks like 4MB, and that's an
> > awful lot of memory to eat up at once.  Shouldn't we just let the
> > kernel demand-fault this like everything else?
> >
> 
> MAP_POPULATE definitely seems like the wrong thing.
> 
Oh. This option should be removed.

Thanks,
Qiaowei

  reply	other threads:[~2014-02-25 13:34 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
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 [this message]
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=9E0BE1322F2F2246BD820DA9FC397ADE0151FC9E@SHSMSX102.ccr.corp.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.