From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickens <hugh@veritas.com>
Subject: Re: [GIT PULL] x86/paravirt for v2.6.33
Date: Wed, 09 Dec 2009 10:18:37 -0800 [thread overview]
Message-ID: <4B1FE9FD.3030407@goop.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0912081329460.3560@localhost.localdomain>
On 12/08/09 13:34, Linus Torvalds wrote:
> I do _not_ want to add any more task_pt_regs() crap, please.
>
> Why? It's wrong for at least vm86 mode (and from kernel system calls).
>
Would the stack frame version work in these cases?
> Maybe we can't get into system calls from vm86 mode, and the kernel
> hopefully doesn't do those things anyway, but the point is, you chose the
> wrong way to go.
>
iopl doesn't make much sense as a kernel-called syscall, unless the
caller is intending to change the usermode iopl. In which case, won't
task_pt_regs() do the right thing - by pointing to the saved usermode
register set - vs modifying the ptregs the caller may pass in?
iopl is also one of the special set of syscalls which get special
handing in entry_*.S, so I don't think doing a direct call from within
the kernel is ever sensible, and it should always be possible to make
task_pt_regs return meaningful results.
I agree with you that vm86 would be a problem if its possible to call iopl.
> The old version that actually passed the stack frame was better. Why pick
> the inferior version?
>
Mainly because it exposes the difference between the 32 and 64-bit ABIs,
requiring separate code for each case; it seemed like an opportunity to
remove the differences.
Anyway, I'll post a patch to revert to the pt_regs-based version shortly.
J
next prev parent reply other threads:[~2009-12-09 18:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 21:09 [GIT PULL] x86/paravirt for v2.6.33 Ingo Molnar
2009-12-08 21:34 ` Linus Torvalds
2009-12-09 7:36 ` Ingo Molnar
2009-12-09 18:19 ` Jeremy Fitzhardinge
2009-12-09 18:31 ` Jeremy Fitzhardinge
2009-12-09 18:47 ` Linus Torvalds
2009-12-09 18:54 ` H. Peter Anvin
2009-12-09 19:08 ` Linus Torvalds
2009-12-09 19:25 ` Brian Gerst
2009-12-09 19:35 ` H. Peter Anvin
2009-12-09 19:32 ` Jeremy Fitzhardinge
2009-12-09 20:05 ` H. Peter Anvin
2009-12-09 18:49 ` H. Peter Anvin
2009-12-09 18:18 ` Jeremy Fitzhardinge [this message]
2009-12-09 21:58 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2009-12-09 18:29 H. Peter Anvin
2009-12-09 18:38 ` Linus Torvalds
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=4B1FE9FD.3030407@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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.