From: Jerone Young <jerone@gmail.com>
To: Arun Sharma <arun.sharma@intel.com>
Cc: Jerone Young <jyoung5@us.ibm.com>, xen-devel@lists.xensource.com
Subject: Re: VMX check in /xen/arch/x86/domain.c is invalid on x86-64 (at least AMD)
Date: Thu, 12 May 2005 00:58:05 -0500 [thread overview]
Message-ID: <9f50a7a00505112258494d7688@mail.gmail.com> (raw)
In-Reply-To: <4282EE03.9080700@intel.com>
Yes I am actually. Sorry guy. I got that one screwed up in my head.
Pressed the send button too quickly. Thanks for the respsonses though.
On 5/12/05, Arun Sharma <arun.sharma@intel.com> wrote:
> Jerone Young wrote:
> > if (!(c->flags & ECF_VMX_GUEST))
> > if ( ((c->cpu_ctxt.cs & 3) == 0) ||
> > ((c->cpu_ctxt.ss & 3) == 0) )
> > return -EINVAL;
> >
> > This check in /xen/arch/x86/domain.c (line 394) is invalid for AMD
> > x86-64 as this field 1<<1 is a reserved field in the rflags (name for
> > 64bit eflags) that reads as 1. This can be found in the AMD x86-64
> > Programming manual vol 2 on page 65. Below is the code, I'm not sure how
> > to put an ifdef around since I'm not sure if Intel's EMT64 with VMX cpus
> > have the same rflag reserved (which if this check is correct they do)?
> > This helps break x86-64 building domU domains.
> >
>
> It is a reserved bit on Intel as well. Look at:
>
> VMCS_EFLAGS_RESERVED_1 and the IA-32 vol1 Fig 3-7.
>
> Are you mixing up ctxt->user_regs.rflags and ctxt->flags in
> xc_linux_build.c?
>
> -Arun
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2005-05-12 5:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1115870256.14673@unix-os.sc.intel.com>
2005-05-12 5:47 ` VMX check in /xen/arch/x86/domain.c is invalid on x86-64 (at least AMD) Arun Sharma
2005-05-12 5:58 ` Jerone Young [this message]
2005-05-12 3:55 Jerone Young
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=9f50a7a00505112258494d7688@mail.gmail.com \
--to=jerone@gmail.com \
--cc=arun.sharma@intel.com \
--cc=jyoung5@us.ibm.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.