All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Beulich <jbeulich@novell.com>
Cc: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
	Xen-devel <xen-devel@lists.xensource.com>,
	Ian Campbell <ijc@hellion.org.uk>
Subject: sysenter/syscall support for 32-on-64 guests?
Date: Thu, 28 Feb 2008 08:49:56 -0800	[thread overview]
Message-ID: <47C6E634.3080609@goop.org> (raw)

I just spent quite a while working out why pvops-Xen kernels weren't 
booting for me in a 64-bit hypervisor.  It turned out to be because 
32-on-64 supports SEP even though 32-on-32 doesn't, so the guest kernel 
was trying to use it without having set up the Xen side, resulting in 
syscalls jumping to 0:0, generating a mysterious GP.  Once I worked that 
out, the fix was simple, of course.

Anyway, I wonder if you had a specific reason for allowing this, other 
than "because we can"?  It seems to me that we should try to minimize 
the number of differences between 32-on-32 and 32-on-64 as much as possible.

    J

             reply	other threads:[~2008-02-28 16:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-28 16:49 Jeremy Fitzhardinge [this message]
2008-02-28 17:14 ` sysenter/syscall support for 32-on-64 guests? Jan Beulich
2008-02-28 20:19   ` Jeremy Fitzhardinge
2008-02-28 21:22   ` Keir Fraser

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=47C6E634.3080609@goop.org \
    --to=jeremy@goop.org \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=ijc@hellion.org.uk \
    --cc=jbeulich@novell.com \
    --cc=xen-devel@lists.xensource.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 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.