From: Ian Campbell <Ian.Campbell@citrix.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: [hybrid]: unable to boot hvm due to eflags.ID
Date: Fri, 4 May 2012 10:08:22 +0100 [thread overview]
Message-ID: <1336122502.2361.7.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <20120503191025.7c2cec2e@mantra.us.oracle.com>
On Fri, 2012-05-04 at 03:10 +0100, Mukesh Rathor wrote:
> Hi guys,
>
> At a loss trying to figure why
> if (has_eflag(X86_EFLAGS_ID))
>
> returns false in my HVM domU. Standard function has_eflag() in
> cpucheck.c running in real mode. Works fine on PV dom0,
Are you sure code in cpucheck.c is even being called for the PV/dom0
case? I'm reasonably sure that PV Xen boot doesn't go anywhere near
arch/x86/boot -- we have a totally different entry point.
> but fails when guest is booting on my hybrid dom0.
What does the guest EFLAGS actually contain at this point? Is it
different to what it contains on non-hybrid dom0?
How do we execute 16 bit code in a VMX guest these days, using vm86 or
by emulation? How does that interact with EFLAGS_ID I wonder (although
why hybrid dom0 would have any bearing on this I've no idea).
> LMK if any ideas. I'll keep digging in the manuals, but nothing so far.
>
> thanks,
> Mukesh
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-05-04 9:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 2:10 [hybrid]: unable to boot hvm due to eflags.ID Mukesh Rathor
2012-05-04 7:43 ` Jan Beulich
2012-05-04 9:08 ` Ian Campbell [this message]
2012-05-04 10:49 ` Tim Deegan
2012-05-04 10:53 ` Ian Campbell
2012-05-04 11:14 ` Tim Deegan
2012-05-04 11:19 ` Tim Deegan
2012-05-04 11:27 ` Jan Beulich
2012-05-04 18:19 ` Mukesh Rathor
2012-05-04 18:54 ` Mukesh Rathor
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=1336122502.2361.7.camel@zakaz.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=Xen-devel@lists.xensource.com \
--cc=mukesh.rathor@oracle.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.