Displaying 8 results from an estimated 8 matches for "guest_context".
2007 Aug 08
2
[PATCH] x86-64: syscall/sysenter support for 32-bit apps
.. for both 32-bit apps in 64-bit pv guests and 32on64.
This patch depends on more than just guest_context saved/restored as guest
state during save/restore/migrate (namely the new fields holding callback
addresses).
Since the 32-bit kernel doesn''t make use of syscall (it would be possible to
do so now, when running on a 64-bit hv), the compat mode guest code path for
syscall wasn''t t...
2007 Aug 09
0
[PATCH] x86-64: pv wrmsr emulation fix
...< 32) | data;
switch ( regs->ecx )
{
#ifdef CONFIG_X86_64
@@ -1704,24 +1706,21 @@ static int emulate_privileged_op(struct
goto fail;
if ( wrmsr_safe(MSR_FS_BASE, regs->eax, regs->edx) )
goto fail;
- v->arch.guest_context.fs_base =
- ((u64)regs->edx << 32) | regs->eax;
+ v->arch.guest_context.fs_base = res;
break;
case MSR_GS_BASE:
if ( is_pv_32on64_vcpu(v) )
goto fail;
if ( wrmsr_safe(MSR_GS_BASE, regs->eax,...
2007 Jun 27
0
[PATCH 1/10] Provide basic Xen PM infrastructure
...EF_RF|EF_NT|EF_DF|EF_IE|EF_TF, 0U);
+#else /* !defined(CONFIG_X86_64) */
+ if (supervisor_mode_kernel && cpu_has_sep)
+ wrmsr(MSR_IA32_SYSENTER_ESP, &t->esp1, 0);
+#endif
+
+ /* Maybe load the debug registers. */
+ if ( !is_idle_vcpu(v) &&
unlikely(v->arch.guest_context.debugreg[7]) )
+ {
+ loaddebug(&v->arch.guest_context, 0);
+ loaddebug(&v->arch.guest_context, 1);
+ loaddebug(&v->arch.guest_context, 2);
+ loaddebug(&v->arch.guest_context, 3);
+ /* no 4 and 5 */
+ loaddebug(&v->arch....
2006 Oct 04
0
[PATCH,RFC 6/17] 32-on-64 shared info handling
...sk << 9;
+ eflags |= !vcpu_info(n, evtchn_upcall_mask) << 9;
if ( !ring_1(regs) )
{
@@ -577,7 +577,7 @@ static void load_segments(struct vcpu *n
if ( test_bit(_VGCF_failsafe_disables_events,
&n->arch.guest_context.flags) )
- n->vcpu_info->evtchn_upcall_mask = 1;
+ vcpu_info(n, evtchn_upcall_mask) = 1;
regs->entry_vector = TRAP_syscall;
regs->_eflags &= 0xFFFCBEFFUL;
@@ -595,11 +595,11 @@ static void load_segments(struct vcpu *n...
2006 Sep 15
0
[HVM][XENOPROFILE][PATCH][2/3] xenoprofile HVM patches
...called from the op_module_athlon.c code,
and returns the proper eip and "mode" for use in the
xenoprof_log_event() function.
2) The vmexit handler code now checks the exitcode and if an NMI was
intercepted, then prior to the stgi(), a flag (VGCF_hvm_guest_nmi) is
set in the v->arch.guest_context.flags field. The VGCF_hvm_guest_nmi
bit is checked during NMI processing via the hvm function callback.
Tom
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2007 Jun 27
1
[PATCH 7/10] SMP support to Xen PM
.../* Then wait for context of vcpu/dom0 to be sync-ed */
+ while ( test_bit(_VPF_need_sync, &v->pause_flags) )
+ cpu_relax();
+
+ pmprintk(XENLOG_INFO, "vcpu0/dom0 has been paused\n");
+
+ /* now safe to suspend whole system from cpu 0 */
+ regs = &v->arch.guest_context.user_regs;
+ regs->eax = enter_state(acpi_sinfo.sleep_state);
+
+ /* Now unpause vcpu0/dom0 */
+ vcpu_unpause(v);
+
+ thaw_domains();
}
static int __init acpi_sleep_init(void)
@@ -268,6 +377,8 @@ static int __init acpi_sleep_init(void)
sleep_states[i] = 0;
}...
2007 Jan 11
6
[PATCH 4/8] HVM save restore: vcpu context support
...pu context such as vmcs
diff -r ee20d1905bde xen/arch/x86/domain.c
--- a/xen/arch/x86/domain.c Thu Jan 11 16:40:55 2007 +0800
+++ b/xen/arch/x86/domain.c Thu Jan 11 16:46:59 2007 +0800
@@ -573,6 +573,7 @@ int arch_set_info_guest(
else
{
hvm_load_cpu_guest_regs(v, &v->arch.guest_context.user_regs);
+ hvm_load_cpu_context(v, &v->arch.guest_context.hvmcpu_ctxt);
}
if ( test_bit(_VCPUF_initialised, &v->vcpu_flags) )
diff -r ee20d1905bde xen/arch/x86/domctl.c
--- a/xen/arch/x86/domctl.c Thu Jan 11 16:40:55 2007 +0800
+++ b/xen/arch/x86/domctl.c Thu Jan...
2006 Sep 15
10
[HVM][XENOPROFILE][RFC][0/3] xenoprofile HVM patches
...called from the op_module_athlon.c code,
and returns the proper eip and "mode" for use in the
xenoprof_log_event() function.
2) The vmexit handler code now checks the exitcode and if an NMI was
intercepted, then prior to the stgi(), a flag (VGCF_hvm_guest_nmi) is
set in the v->arch.guest_context.flags field. The VGCF_hvm_guest_nmi
bit is checked during NMI processing via the hvm function callback.
hvm_xenoprofile_3.patch -
The third patch adds the actual xenoprofile fixes for VT:
I checked (verified by Renato), that the VT traces look ok also. There
is some code that I am unsure about...