Messages in this thread | | | Date | Mon, 29 Nov 2010 13:37:56 -0800 | Subject | Re: Xen domU kernel no longer shuts down (Was Linux 2.6.32.26) | From | Alok Kataria <> |
| |
[resending my reply, apologies if you get it twice]
On Mon, Nov 29, 2010 at 1:35 PM, Alok Kataria <alokkataria1@gmail.com> wrote: > > > On Fri, Nov 26, 2010 at 2:38 PM, Jeremy Fitzhardinge <jeremy@goop.org> wrote: >> >> On 11/26/2010 06:07 AM, Alan J. Wylie wrote: >> > Greg KH <gregkh@suse.de> writes: >> > >> >> I'm announcing the release of the 2.6.32.26 kernel. >> > ... >> > >> >> Alok Kataria (1): >> >> x86, kexec: Make sure to stop all CPUs before exiting the kernel >> > This patch (ae832c21a08514fd11d2d1d6e217c8a537764bb0) stops my Xen DomU from >> > shutting down iff vcpus in the xen config file is > 1. >> > >> > Simply reverting the commit gets things working properly again. >> >> Thanks for confirming this. I had seen the same thing and suspected >> this change, but hadn't investigated it yet. > > > To get the old behavior back for Xen you can replace this call > smp_call_function(stop_self, NULL, wait); > > in xen_stop_other_cpus with > > smp_call_function(stop_self, NULL, 0); > > That should fix your hang and fallback to the original behavior, though please note that there might still be a fundamental problem about why some of the AP's don't respond to stop_send IPI on XEN. > > Alok -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |