search for: arch_set_info_guest

...+++ b/xen/arch/x86/domain.c @@ -51,6 +51,7 @@ #include <asm/fixmap.h> #include <asm/hvm/hvm.h> #include <asm/hvm/support.h> +#include <asm/hvm/nestedhvm.h> #include <asm/debugreg.h> #include <asm/msr.h> #include <asm/traps.h> @@ -704,9 +705,13 @@ int arch_set_info_guest( /* PVH 32bitfixme */ ASSERT(!compat); - if ( c(ctrlreg[1]) || c(ldt_base) || c(ldt_ents) || + if ( (c(ctrlreg[0]) & HVM_CR0_GUEST_RESERVED_BITS) || + (c(ctrlreg[4]) & HVM_CR4_GUEST_RESERVED_BITS(v)) || + c(ctrlreg[1]) || c(ctrlreg[2...

...least need to ensure all frames covered by d->max_pages allocated for target domain. Then there''re two alternatives: - Keep the first piece of change on increase_reservation, which ensures all pages including extra spaces allocated immediately. - Pass the extra memory size to xen at arch_set_info_guest, and then change xen/ia64 to only tell domain maximum pfns as d->max_pages-extra_size Both need to be changed again later if balloon is ready. So I prefer to option I which is simpler and can help Alex to do sync quickly. How do you think? Thanks, Kevin ___________________________________...

The initial values of the wallclock time in the shared info page are set for PVHVM guests when the hypercall page is initialized, since the hypercall page is not reinitialized on resume, the hypervisor wallclock time is not properly set on resume. Fix it by forcing an update of the wallclock values when the shared info page is mapped. Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>

...cpu_resources(struct vcpu *v); extern void vcpu_share_privregs_with_guest(struct vcpu *v); diff -r 58d131f1fb35 -r 2c9db26f1d0e xen/include/xen/domain.h --- a/xen/include/xen/domain.h Fri Aug 24 16:32:56 2007 +0100 +++ b/xen/include/xen/domain.h Tue Aug 28 13:06:41 2007 +0900 @@ -45,7 +45,7 @@ int arch_set_info_guest(struct vcpu *, v int arch_set_info_guest(struct vcpu *, vcpu_guest_context_u); void arch_get_info_guest(struct vcpu *, vcpu_guest_context_u); -void domain_relinquish_resources(struct domain *d); +int domain_relinquish_resources(struct domain *d); void dump_pageframe_info(struct domain *d);...

...H. * Effort is made to use as much common code as possible. No separate vmcs constructor, no separate vmexit handlers. More of a "start with everything and disable if necessary" approach rather than "start with nothing and enable as needed" approach. * One exception is arch_set_info_guest(), where a small amount of code duplication meant a lot fewer "if(!is_pvh_domain())"s in awkward places * I rely on things being disabled at a higher level and passed down. For instance, I no longer explicitly disable rdtsc exiting in construct_vmcs(), since that will happen auto...

...+#ifdef __x86_64__ + v->arch.sysexit_cs = 3; + v->arch.syscall_eflags_mask = X86_EFLAGS_DF|X86_EFLAGS_TF|X86_EFLAGS_NT| + X86_EFLAGS_RF|X86_EFLAGS_VM; +#endif + return (is_pv_32on64_vcpu(v) ? setup_compat_l4(v) : 0); } @@ -625,7 +631,18 @@ int arch_set_info_guest( v->arch.flags |= TF_kernel_mode; if ( !compat ) + { memcpy(&v->arch.guest_context, c.nat, sizeof(*c.nat)); +#ifdef __x86_64__ + /* + * Despite not being correct, be backwards compatible - most + * importantly in order to prevent the gues...

1: correct LDT checks 2: add address validity check to guest_map_l1e() 3: use {rd,wr}{fs,gs}base when available 4: check for canonical address before doing page walks Signed-off-by: Jan Beulich <jbeulich@suse.com>

...populate_physmap: 216 0xffff8300001137d3 populate_physmap: 216 0xffff83000012a742 guest_console_write: 216 0xffff83000012a8de guest_console_write: 216 0xffff83000011009a do_grant_table_op: 208 0xffff8300001343e1 arch_set_info_guest: 208 0xffff83000014d382 do_set_gdt: 208 0xffff830000160c67 alloc_shadow_page: 208 0xffff83000017f103 alloc_shadow_page: 208 0xffff8300001c11c6 construct_default_ISA_mptable: 208 0xffff830000167697 shadow_l4_table:...

I''ve put together two patches. The first introduces a new dom0_op, set_max_vcpus, which with an associated variable and a check in the VCPUOP handler fixes [1]bug 288. Also included is a new VCPUOP, VCPUOP_create, which handles all of the vcpu creation tasks and leaves initialization and unpausing to VCPUOP_initialize. The separation allows for build-time allocation of vcpus which

The first patch really isn''t as much of a follow-up than what triggered the security issues to be noticed in the first place. 1: x86: preserve FPU selectors for 32-bit guest code 2: x86: fix XCR0 handling 3: x86/xsave: adjust state management 4: x86/fxsave: bring in line with recent xsave adjustments The first two I would see as candidates for 4.3 (as well as subsequent backporting,

...ntext support Signed-off-by: Zhai Edwin <edwin.zhai@intel.com> save/restore HVM vcpu 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/...

.../xen-core-devices/ A M xen: arm: allocate dom0 memory separately from preparing the dtb A xen: arm: add enable-method to cpu nodes for arm64 guests. A xen: arm: include header for for arch_do_{sys,dom}ctl prototype A xen: arm: implement XEN_DOMCTL_set_address_size A xen: arm: implement arch_set_info_guest for 64-bit vcpus A tools: check for libfdt when building for ARM A xen: arm: define guest virtual platform in API headers A libxc: arm: rename various bits of zimage load with 32 suffix A libxc: allow caller to specify guest rambase rather than hardcoding A M libxc: arm: allow passing...

Hi all, this small patch series implement guest SMP support for ARM, using the ARM PSCI interface for secondary cpu bringup. Stefano Stabellini (4): xen/arm: basic PSCI support, implement cpu_on xen/arm: support for guest SGI xen/arm: support vcpu_op hypercalls xen: move VCPUOP_register_vcpu_info to common code xen/arch/arm/domain.c | 66 ++++++++++++++++++++++++

I''ve addressed all (I think/hope) of the review comments. The main change is to expose the guest virtual platform (e.g. memory layout and interrupt usage etc) to the toolstack via the public interface. This is then used during FDT generation. I have just codified the current defacto standard layout, it''s probably not the best layout but any change can be a separate patch/series.

First off, Apologies for the massive patch series... This series boots a 32-bit dom0 kernel to a command prompt on an ARMv8 (AArch64) model. The kernel is the same one as I am currently using with the 32 bit hypervisor I haven''t yet tried starting a guest or anything super advanced like that ;-). Also there is not real support for 64-bit domains at all, although in one or two places I

This round implements all of the review comments from V2 and all patches are now acked. Unless there are any objections I intend to apply later this morning. Ian.

Hello everyone, this is the fourth version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See

Hello everyone, this is the very first version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See