lkml.org 
[lkml]   [2016]   [Feb]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Date
    Subject[PATCH 3.2 31/87] x86/xen: don't reset vcpu_info on a cancelled suspend
    3.2.77-rc1 review patch.  If anyone has any objections, please let me know.

    ------------------

    From: "Ouyang Zhaowei (Charles)" <ouyangzhaowei@huawei.com>

    commit 6a1f513776b78c994045287073e55bae44ed9f8c upstream.

    On a cancelled suspend the vcpu_info location does not change (it's
    still in the per-cpu area registered by xen_vcpu_setup()). So do not
    call xen_hvm_init_shared_info() which would make the kernel think its
    back in the shared info. With the wrong vcpu_info, events cannot be
    received and the domain will hang after a cancelled suspend.

    Signed-off-by: Charles Ouyang <ouyangzhaowei@huawei.com>
    Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
    Signed-off-by: David Vrabel <david.vrabel@citrix.com>
    Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
    ---
    arch/x86/xen/suspend.c | 3 ++-
    1 file changed, 2 insertions(+), 1 deletion(-)

    --- a/arch/x86/xen/suspend.c
    +++ b/arch/x86/xen/suspend.c
    @@ -30,7 +30,8 @@ void xen_arch_hvm_post_suspend(int suspe
    {
    #ifdef CONFIG_XEN_PVHVM
    int cpu;
    - xen_hvm_init_shared_info();
    + if (!suspend_cancelled)
    + xen_hvm_init_shared_info();
    xen_callback_vector();
    xen_unplug_emulated_devices();
    if (xen_feature(XENFEAT_hvm_safe_pvclock)) {
    \
     
     \ /
      Last update: 2016-02-09 01:21    [W:4.133 / U:0.060 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site