From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Mark McLoughlin <markmc@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] fix sysenter for 32-on-64 processes
Date: Mon, 21 Jul 2008 16:49:50 -0700 [thread overview]
Message-ID: <4885209E.8050003@goop.org> (raw)
Hi Ingo,
Here's a little two-part patch series which fixes 32-on-64 syscalls
using sysenter.
The first is a difference in ordering in arch_setup(); the 64-bit code
was calling early_init_cpu() way too late. Moving it earlier, to the
same place as the 32-bit code, works for me, but I wonder if it might
cause problems with other configurations. Certainly it makes logical
sense that both architectures do the same cpu setup at the same place.
The other fix is an outright Xen-specific bug, which resulted in
usermode registers being trashed as a result of an over-enthusiastic use
of sysret.
Both patches are .27 material, but I expect the arch_setup() change
needs to cooking before being comfortable with it.
Thanks,
J
reply other threads:[~2008-07-21 23:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4885209E.8050003@goop.org \
--to=jeremy@goop.org \
--cc=ehabkost@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mingo@elte.hu \
/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