From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Do the x86 kernel entry points need an xabort on TSX cpus?
Date: Tue, 21 Feb 2012 11:30:08 -0800 [thread overview]
Message-ID: <4F43F0C0.5050104@zytor.com> (raw)
In-Reply-To: <CALCETrVHpfW5=paX8XjGNBg3Q7sjeLptMBG6bW=iQpXk0Uo+PA@mail.gmail.com>
On 02/10/2012 09:24 AM, Andy Lutomirski wrote:
>
> Is that architecturally guaranteed? (My manual suggests that it's
> specifically *not* guaranteed, which is surprising.)
>
I asked internally for a statement, and got the following:
"Intel does not expect operating systems to require XABORT at the entry
points. Intel takes system security extremely seriously and that any
functionality added is scrutinized for security implications."
-hpa
prev parent reply other threads:[~2012-02-21 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 7:40 Do the x86 kernel entry points need an xabort on TSX cpus? Andy Lutomirski
2012-02-10 17:18 ` H. Peter Anvin
2012-02-10 17:24 ` Andy Lutomirski
2012-02-10 18:51 ` Simon Farnsworth
2012-02-21 19:30 ` 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=4F43F0C0.5050104@zytor.com \
--to=hpa@zytor.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--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