From: Avi Kivity <avi@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Pekka Enberg" <penberg@cs.helsinki.fi>,
"Tom Zanussi" <tzanussi@gmail.com>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
linux-perf-users@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: disabling group leader perf_event
Date: Tue, 07 Sep 2010 12:13:57 +0300 [thread overview]
Message-ID: <4C860255.7000707@redhat.com> (raw)
In-Reply-To: <AANLkTik0d=d4VfWy0WFDpsQttbZ9cFTVjqmRjgY4+7v1@mail.gmail.com>
On 09/07/2010 11:33 AM, Stefan Hajnoczi wrote:
>
> Native Client: A Sandbox for Portable, Untrusted x86 Native Code, IEEE
> Symposium on Security and Privacy, May 2009
> http://nativeclient.googlecode.com/svn/data/docs_tarball/nacl/googleclient/native_client/documentation/nacl_paper.pdf
>
> The "Inner Sandbox" they talk about verifies a subset of x86 code.
> For indirect control flow (computed jumps), they introduce a new
> instruction that can do run-time checking of the destination address.
Interesting, but appears to rely on x86 segmentation, which isn't
available on x86_64.
Removing that requirement means replacing indirect memory access by a
new instruction that does run-time checking, like indirect control flow,
which is likely to kill performance.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-09-07 9:14 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 9:12 disabling group leader perf_event Avi Kivity
2010-09-06 11:24 ` Peter Zijlstra
2010-09-06 11:34 ` Avi Kivity
2010-09-06 11:54 ` Peter Zijlstra
2010-09-06 11:58 ` Avi Kivity
2010-09-06 12:29 ` Peter Zijlstra
2010-09-06 12:40 ` Ingo Molnar
2010-09-06 13:16 ` Steven Rostedt
2010-09-06 16:42 ` Tom Zanussi
2010-09-07 12:53 ` Steven Rostedt
2010-09-07 14:16 ` Tom Zanussi
2010-09-06 12:49 ` Avi Kivity
2010-09-06 12:43 ` Ingo Molnar
2010-09-06 12:45 ` Avi Kivity
2010-09-06 12:59 ` Ingo Molnar
2010-09-06 13:41 ` Pekka Enberg
2010-09-06 13:54 ` Ingo Molnar
2010-09-06 14:57 ` Avi Kivity
2010-09-06 15:30 ` Alan Cox
2010-09-06 15:20 ` Avi Kivity
2010-09-06 15:48 ` Alan Cox
2010-09-06 17:50 ` Avi Kivity
2010-09-06 15:47 ` Ingo Molnar
2010-09-06 17:55 ` Avi Kivity
2010-09-07 3:44 ` Ingo Molnar
2010-09-07 8:33 ` Stefan Hajnoczi
2010-09-07 9:13 ` Avi Kivity [this message]
2010-09-07 22:43 ` Ingo Molnar
2010-09-07 15:55 ` Alan Cox
2010-09-08 1:44 ` Paul Mackerras
2010-09-08 6:16 ` Pekka Enberg
2010-09-08 6:44 ` Ingo Molnar
2010-09-08 7:30 ` Peter Zijlstra
2010-09-08 19:30 ` Frank Ch. Eigler
2010-09-09 7:38 ` Ingo Molnar
2010-09-08 6:19 ` Avi Kivity
2010-09-06 20:31 ` Pekka Enberg
2010-09-06 20:37 ` Pekka Enberg
2010-09-07 4:03 ` Ingo Molnar
2010-09-07 9:30 ` Pekka Enberg
2010-09-07 22:27 ` Ingo Molnar
2010-09-07 10:57 ` KOSAKI Motohiro
2010-09-07 12:14 ` Pekka Enberg
2010-09-07 13:35 ` Steven Rostedt
2010-09-07 13:47 ` Avi Kivity
2010-09-07 16:02 ` Steven Rostedt
2010-09-12 6:46 ` Pavel Machek
2010-09-12 17:54 ` Avi Kivity
2010-09-12 18:48 ` Ingo Molnar
2010-09-12 19:14 ` Pavel Machek
2010-09-12 20:32 ` Ingo Molnar
2010-09-12 21:06 ` Pavel Machek
2010-09-12 22:19 ` 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=4C860255.7000707@redhat.com \
--to=avi@redhat.com \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=stefanha@gmail.com \
--cc=tzanussi@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).