From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>,
"Tim.Deegan@citrix.com" <Tim.Deegan@citrix.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [hybrid]: unable to boot hvm due to eflags.ID
Date: Fri, 4 May 2012 11:19:35 -0700 [thread overview]
Message-ID: <20120504111935.7553aaed@mantra.us.oracle.com> (raw)
In-Reply-To: <1336122502.2361.7.camel@zakaz.uk.xensource.com>
On Fri, 4 May 2012 10:08:22 +0100
Ian Campbell <Ian.Campbell@citrix.com> wrote:
> 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.
I didn't make myself clear (rushing to type email and leave with a
brain fried from debugging all day :).)
I'm talking about HVM domU on PV/dom0.
Basically, I've the PV linux kernel modified for hybrid. I can boot it
as both hybrid domU (say Lu) and hybrid dom0 (say L0).
Orig/normal PV DOM0: Lu boots in hybrid mode, PV mode, HVM mode.
L0 as Dom0: Lu boots in hybrid mode, PV mode but in HVM mode fails.
HVM mode is failing because very early during boot its failing the
eflags.ID test, which should be simple. It should be running
in real mode in the VMX. I just got outb working, so I can debug
further now. It's not doing vmexit's so should be running in the
'unrestricted mode' in the container, which is why i'm baffled.
Anyways, i'll dig further.
thanks a lot,
Mukesh
next prev parent reply other threads:[~2012-05-04 18:19 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
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 [this message]
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=20120504111935.7553aaed@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=Tim.Deegan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).