From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
Chuck Ebbert <76306.1226@compuserve.com>,
In Cognito <defend.the.world@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
bcrl@kvack.org, Zachary Amsden <zach@vmware.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Chris Wright <chrisw@sous-sol.org>,
Jeremy Fitzhardinge <jeremy@xensource.com>
Subject: Re: Sysenter crash with Nested Task Bit set
Date: Mon, 18 Sep 2006 09:24:53 -0700 [thread overview]
Message-ID: <450EC855.6020200@goop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0609180904360.4388@g5.osdl.org>
Linus Torvalds wrote:
> Final note (I promise): now that we save/restore eflags again, we
> should probably revert the set_iopl_mask() in task switching too. However,
> that apparently has some para-virtualization issues, so I'm going to
> ignore that part from now.
>
I'm wondering if we shouldn't have a (__)switch_to paravirt hook, so we
can wrap the context switch in whatever we like.
> However, I'd really like people who know and care about the
> paravirtualization to take a good long look at it: because right now, with
> the addition of the eflags save/restore, the set_iopl_mask() in
> __switch_to() is entirely useless for non-virtualized environments, afaik.
>
Hm. Zach removed the pushf/popf in switch_to this last Sept, with the
comment "The pushf/popf in switch_to are ONLY used to switch IOPL.
Making this explicit in C code is more clear. This pushf/popf pair was
added as a bugfix for leaking IOPL to unprivileged processes when using
sysenter/sysexit based system calls (sysexit does not restore flags)."
> Zack added to the cc. Who else needs to know?
Rusty, Chris Wright and me.
next prev parent reply other threads:[~2006-09-18 16:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 3:51 Sysenter crash with Nested Task Bit set Chuck Ebbert
2006-09-18 5:25 ` Andrew Morton
2006-09-18 8:44 ` Mike Galbraith
2006-09-18 15:11 ` Linus Torvalds
2006-09-18 15:06 ` Ingo Molnar
2006-09-18 15:29 ` Andi Kleen
2006-09-18 15:24 ` Ingo Molnar
2006-09-18 16:02 ` Linus Torvalds
2006-09-18 16:10 ` Linus Torvalds
2006-09-18 16:24 ` Jeremy Fitzhardinge [this message]
2006-09-18 16:12 ` Benjamin LaHaise
2006-09-18 16:39 ` Andi Kleen
2006-09-18 19:01 ` Jeremy Fitzhardinge
[not found] <5a20704e0609171603s55ca52bap71dc2fa2c05d6741@mail.gmail.com>
2006-09-17 23:08 ` In Cognito
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=450EC855.6020200@goop.org \
--to=jeremy@goop.org \
--cc=76306.1226@compuserve.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bcrl@kvack.org \
--cc=chrisw@sous-sol.org \
--cc=defend.the.world@gmail.com \
--cc=jeremy@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@osdl.org \
--cc=zach@vmware.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