search for: hvm_s3_resum

...xen/arch/x86/hvm/hvm.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c index 3b353ec..3d48978 100644 --- a/xen/arch/x86/hvm/hvm.c +++ b/xen/arch/x86/hvm/hvm.c @@ -3736,8 +3736,13 @@ static void hvm_s3_suspend(struct domain *d) static void hvm_s3_resume(struct domain *d) { + struct vcpu *v; if ( test_and_clear_bool(d->arch.hvm_domain.is_s3_suspended) ) + { + for_each_vcpu( d, v ) + hvm_set_guest_tsc( v, 0 ); domain_unpause(d); + } } static int hvmop_set_isa_irq_level( -- 1.8.4.rc3

[Patch 4/4]: Xend interface for HVM S3 - extend "xm resume <domid>" to be able to S3 resume HVM domain. - when user issue "xm resume" command for HVM domain, xend will use xc lib API to call HVMOP_s3_resume hypercall. Note: it may not appropriate use xm resume for HVM s3, since xm resume is originally designed for save/restor purpose. It will be fine that

Hi all, this patch series makes the necessary changes to make sure that the current ARM hypercall ABI can be used as-is on 64 bit ARM platforms: - it defines xen_ulong_t as uint64_t on ARM; - it introduces a new macro to handle guest pointers, called XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to have size 8 bytes on aarch64); - it replaces all the occurrences of

Hi all, this patch series makes the necessary changes to make sure that the current ARM hypercall ABI can be used as-is on 64 bit ARM platforms: - it defines xen_ulong_t as uint64_t on ARM; - it introduces a new macro to handle guest pointers, called XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to have size 8 bytes on aarch64); - it replaces all the occurrences of