From: Peter Zijlstra <peterz@infradead.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Paul Mackerras <paulus@samba.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
X86 ML <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, Kees Cook <keescook@chromium.org>,
Erik Bosman <ebn310@few.vu.nl>, "H. Peter Anvin" <hpa@zytor.com>,
Linux API <linux-api@vger.kernel.org>,
Michael Kerrisk-manpages <mtk.manpages@gmail.com>
Subject: Re: [PATCH] x86,seccomp,prctl: Remove PR_TSC_SIGSEGV and seccomp TSC filtering
Date: Fri, 3 Oct 2014 22:15:37 +0200 [thread overview]
Message-ID: <20141003201537.GN10583@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <CALCETrWP7QSb4dFh_phUK+7P-XookgL8UXgvHi-e4icukUF2Og@mail.gmail.com>
On Fri, Oct 03, 2014 at 10:59:15AM -0700, Andy Lutomirski wrote:
> RDPMC is controlled by CR4.PCE, whereas RDTSC is controlled by
> CR4.TSD,
This is my understanding too, they're separate things.
prev parent reply other threads:[~2014-10-03 20:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 17:18 [PATCH] x86,seccomp,prctl: Remove PR_TSC_SIGSEGV and seccomp TSC filtering Andy Lutomirski
2014-10-03 17:27 ` Andy Lutomirski
2014-10-03 20:14 ` Peter Zijlstra
2014-10-03 20:22 ` Andy Lutomirski
2014-10-03 20:27 ` Andy Lutomirski
2014-10-03 20:44 ` Peter Zijlstra
2014-10-03 20:46 ` Andy Lutomirski
2014-10-03 21:02 ` Peter Zijlstra
2014-10-03 21:04 ` Peter Zijlstra
2014-10-03 21:04 ` Andy Lutomirski
2014-10-03 21:12 ` Peter Zijlstra
2014-10-03 21:15 ` Andy Lutomirski
2014-10-04 8:13 ` Peter Zijlstra
2014-10-06 16:44 ` Andy Lutomirski
2014-10-03 20:42 ` Peter Zijlstra
2014-10-03 20:53 ` Andy Lutomirski
[not found] ` <20141003174141.GR2342@redhat.com>
2014-10-03 17:59 ` Andy Lutomirski
2014-10-03 20:15 ` Peter Zijlstra [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=20141003201537.GN10583@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=aarcange@redhat.com \
--cc=acme@kernel.org \
--cc=ebn310@few.vu.nl \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=paulus@samba.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 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).