From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Keir Fraser <keir.xen@gmail.com>, Tim Deegan <tim@xen.org>
Subject: Re: RFC: PVH set vcpu info context in vmcs....
Date: Wed, 14 Aug 2013 17:25:15 -0700 [thread overview]
Message-ID: <20130814172515.11fb949a@mantra.us.oracle.com> (raw)
In-Reply-To: <520B661202000078000EBC88@nat28.tlf.novell.com>
On Wed, 14 Aug 2013 10:12:18 +0100
"Jan Beulich" <JBeulich@suse.com> wrote:
> >>> On 14.08.13 at 04:12, Mukesh Rathor <mukesh.rathor@oracle.com>
> >>> wrote:
> > On Tue, 13 Aug 2013 11:56:36 +0100
> > "Jan Beulich" <JBeulich@suse.com> wrote:
> >
...
> >> > if ( v->vcpu_id == 0 )
> >> > return 0;
> >>
> >> Bogus/pointless.
> >
> > No, we don't have anything for the boot vcpu. It's totally coming up
> > on the flat address space. For non boot, the vcpu is coming up on
> > the kernel GDT. Recall it's a PV guest (coming up in an HVM
> > container).
>
> No, that's the wrong perspective. You either should never get here
> for vCPU 0, or you should refuse this for all already initialized
> vCPU-s.
Ok, i'll move the check to caller. FWIW, the vcpu->is_initialised is
inapplicable here because this is relevant for non-boot vcpus only.
>>
>> if ( ctxtp->user_regs.cs == 0 || (ctxtp->user_regs.cs & 3) == 3 )
>> return -EINVAL;
>Perhaps better check for any non-zero RPL, as the RPL needs
>to match of the (enforced) CS hidden fields?
Well, we now load the descriptor provided by the guest in the GDT
so that's kinda un needed now.. thats why i thought we don't need to
enforce RPL or check VGCF_in_kernel. But, that would work too...
thanks,
mukesh
Final(hopefully) version:
/*
* Set vmcs fields in support of vcpu_op -> VCPUOP_initialise hcall used
* to initialise a secondary vcpu prior to boot. (boot vcpu 0 context is
* set by the tools via do_domctl -> vcpu_initialise). Called from
* arch_set_info_guest() which sets the (PVH relevant) non-vmcs fields.
*
* In case of linux:
* The call comes from cpu_initialize_context().
*
* PVH 32bitfixme: this function needs to be modified for 32bit guest.
*/
int vmx_pvh_set_vcpu_info(struct vcpu *v, struct vcpu_guest_context *ctxtp)
{
int rc;
if ( !(ctxtp->flags & VGCF_in_kernel) )
return -EINVAL;
if ( ctxtp->ldt_base || ctxtp->ldt_ents ||
ctxtp->user_regs.ss || ctxtp->user_regs.es || ctxtp->user_regs.ds ||
ctxtp->user_regs.fs || ctxtp->user_regs.gs )
return -EINVAL;
if ( ctxtp->user_regs.cs == 0 || (ctxtp->user_regs.cs & 7) )
return -EINVAL;
vmx_vmcs_enter(v);
__vmwrite(GUEST_GDTR_BASE, ctxtp->gdt.pvh.addr);
__vmwrite(GUEST_GDTR_LIMIT, ctxtp->gdt.pvh.limit);
/* IA-32e: ss/es/ds are ignored. */
if ( (rc = hvm_load_segment_selector(v, x86_seg_cs, ctxtp->user_regs.cs)) )
goto out;
__vmwrite(GUEST_FS_BASE, ctxtp->fs_base);
__vmwrite(GUEST_GS_BASE, ctxtp->gs_base_kernel);
if ( (rc = vmx_add_guest_msr(MSR_SHADOW_GS_BASE)) )
goto out;
vmx_write_guest_msr(MSR_SHADOW_GS_BASE, ctxtp->gs_base_user);
out:
vmx_vmcs_exit(v);
return rc;
}
next prev parent reply other threads:[~2013-08-15 0:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 1:45 RFC: PVH set vcpu info context in vmcs Mukesh Rathor
2013-08-13 9:16 ` Tim Deegan
2013-08-13 12:10 ` Jan Beulich
2013-08-13 10:56 ` Jan Beulich
2013-08-14 2:12 ` Mukesh Rathor
2013-08-14 9:12 ` Jan Beulich
2013-08-14 9:57 ` George Dunlap
2013-08-15 0:25 ` Mukesh Rathor [this message]
2013-08-15 1:58 ` Mukesh Rathor
2013-08-15 6:34 ` Jan Beulich
2013-08-15 6:31 ` Jan Beulich
2013-08-16 2:26 ` Mukesh Rathor
2013-08-16 7:28 ` Jan Beulich
2013-08-16 22:28 ` Mukesh Rathor
2013-08-17 1:37 ` Mukesh Rathor
2013-08-17 10:22 ` Tim Deegan
2013-08-19 21:45 ` Mukesh Rathor
2013-08-19 9:34 ` Jan Beulich
2013-08-19 21:46 ` 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=20130814172515.11fb949a@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=JBeulich@suse.com \
--cc=keir.xen@gmail.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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).