All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dan Magenheimer" <dan.magenheimer@oracle.com>
To: Samuel Thibault <samuel.thibault@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: RE: Early test for 32- vs 64-bit hvm domain?
Date: Tue, 29 Jan 2008 17:34:38 -0700	[thread overview]
Message-ID: <20080129173438062.00000002384@djm-pc> (raw)
In-Reply-To: <20080130001134.GM4386@implementation>

> Dan Magenheimer, le Tue 29 Jan 2008 17:01:22 -0700, a écrit :
> > What is the proper way to test to see if an hvm domain is destined
> > to be x86 vs x86_64 whilst still early in its initialization in the
> > hypervisor, e.g. in hvm_vcpu_initialise(v) or 
> hvm_domain_initialise(d)?
> > Is this information pased down from hvmloader or does it get
> > discovered somehow?  Or maybe it is not possible to determine
> > until a vcpu actually starts executing?
> 
> As long as e.g. Linux has not started (i.e. during bios and grub for
> instance), you can't know whether that will be a 64bit Linux 
> or a 32bit
> Linux.

That's what I was afraid of...

Then what is the earliest point in the execution of an x86_64
domain/vcpu in *xen* where hvm_long_mode_enabled(v) will work
properly? E.g. in Linux/x86_64 is long mode set early in __start?
And is this done via a hypercall or an emulated instruction?

Thanks,
Dan

  reply	other threads:[~2008-01-30  0:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30  0:01 Early test for 32- vs 64-bit hvm domain? Dan Magenheimer
2008-01-30  0:11 ` Samuel Thibault
2008-01-30  0:34   ` Dan Magenheimer [this message]
2008-01-30  8:21     ` Keir Fraser
2008-01-30 18:44       ` Andi Kleen
2008-01-30 19:28         ` 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=20080129173438062.00000002384@djm-pc \
    --to=dan.magenheimer@oracle.com \
    --cc=samuel.thibault@eu.citrix.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.