Re: [Xen-devel] [PATCH pvops] Fix a bug that shutdown watcher is disabled on pvops

[Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>]

On Fri, 2011-03-04 at 02:09 +0000, Frank Pan wrote:
> Sorry I didn't mention it. I use jeremy's tree.
> 
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> linux-2.6-xen
> 
> The kernel version is 2.6.32.27.

Is the issue you are seeing perhaps due to this patch being missing from
that tree?

commit a947f0f8f7012a5e8689a9cff7209ec6964ec154
Author: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date:   Mon Oct 4 16:10:06 2010 +0100

    xen: do not set xenstored_ready before xenbus_probe on hvm
    
    Register_xenstore_notifier should guarantee that the caller gets
    notified even if xenstore is already up.
    Therefore we revert "do not notify callers from
    register_xenstore_notifier" and set xenstored_read at the right time for
    PV on HVM guests too.
    In fact in case of PV on HVM guests xenstored is ready only after the
    platform pci driver has completed the initialization, so do not set
    xenstored_ready before the call to xenbus_probe().
    
    This patch fixes a shutdown_event watcher registration bug that causes
    "xm shutdown" not to work properly.
    
    Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
    Acked-by: Jeremy Fitzhardinge <jeremy@xxxxxxxx>

If possible we should prefer to backport patches from newer kernels
rather than diverge in the 2.6.32 branch.

Stefano's "2.6.38-rc6-pvhvm" branch also contains this which looks
related:

commit 702d4eb9b3de4398ab99cf0a4e799e552c7ab756
Author: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date:   Thu Dec 2 17:54:50 2010 +0000

    xen: no need to delay xen_setup_shutdown_event for hvm guests anymore
    
    Now that xenstore_ready is used correctly for PV on HVM guests too, we
    don't need to delay the initialization of xen_setup_shutdown_event
    anymore.
    
    Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
    Acked-by: Jeremy Fitzhardinge <jeremy@xxxxxxxx>

Ian.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel