From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Jan Beulich <JBeulich@suse.com>, Tim Deegan <tim@xen.org>,
Keir Fraser <keir.xen@gmail.com>,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: RFC: PVH set vcpu info context in vmcs....
Date: Mon, 12 Aug 2013 18:45:13 -0700 [thread overview]
Message-ID: <20130812184513.56188d29@mantra.us.oracle.com> (raw)
I just decided to create a new thread... Here's the code I wanted
to propose.
thanks,
Mukesh
/*
* Set vmcs fields in support of vcpu_op -> VCPUOP_initialise hcall used
* to initialise a secondary vcpu prior to boot. 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(). (boot vcpu 0 context is
* set by the tools via do_domctl -> vcpu_initialise).
*
* 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 ( v->vcpu_id == 0 )
return 0;
if ( !(ctxtp->flags & VGCF_in_kernel) )
return -EINVAL;
if ( ctxtp->ldt_base || ctxtp->ldt_ents ||
(ctxtp->user_regs.cs & 4) || ctxtp->user_regs.ss ||
ctxtp->user_regs.es || ctxtp->user_regs.ds )
return -EINVAL;
if ( ctxtp->user_regs.cs == 0 )
return -EINVAL;
vmx_vmcs_enter(v);
__vmwrite(GUEST_GDTR_BASE, ctxtp->gdt.pvh.addr);
__vmwrite(GUEST_GDTR_LIMIT, ctxtp->gdt.pvh.limit);
__vmwrite(GUEST_FS_BASE, ctxtp->fs_base);
__vmwrite(GUEST_GS_BASE, ctxtp->gs_base_kernel);
/* IA-32e: ss/es/ds are ignored, we load cs only. */
__vmwrite(GUEST_CS_SELECTOR, ctxtp->user_regs.cs);
if ( (rc = hvm_load_segment_selector(x86_seg_cs, ctxtp->user_regs.cs)) )
return rc;
__vmwrite(GUEST_FS_SELECTOR, ctxtp->user_regs.fs);
__vmwrite(GUEST_GS_SELECTOR, ctxtp->user_regs.gs);
if ( (rc = vmx_add_guest_msr(MSR_SHADOW_GS_BASE)) )
{
vmx_vmcs_exit(v);
return rc;
}
vmx_write_guest_msr(MSR_SHADOW_GS_BASE, ctxtp->gs_base_user);
vmx_vmcs_exit(v);
return 0;
}
next reply other threads:[~2013-08-13 1:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 1:45 Mukesh Rathor [this message]
2013-08-13 9:16 ` RFC: PVH set vcpu info context in vmcs 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
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=20130812184513.56188d29@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=JBeulich@suse.com \
--cc=Xen-devel@lists.xensource.com \
--cc=keir.xen@gmail.com \
--cc=tim@xen.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).