public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "Alan J. Wylie" <alan@wylie.me.uk>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Sander Eikelenboom <linux@eikelenboom.it>
Subject: Re: Xen domU kernel no longer shuts down (Was Linux 2.6.32.26)
Date: Fri, 26 Nov 2010 16:37:16 -0800	[thread overview]
Message-ID: <20101127003716.GA12074@suse.de> (raw)
In-Reply-To: <4CF036CF.20606@goop.org>

On Fri, Nov 26, 2010 at 02:38:07PM -0800, Jeremy Fitzhardinge 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.
> 
> I'll try to get to a fix next week.

I'll revert this patch from the next .32 release to prevent the
regression.  Please resend this patch, and the fix, when you figure it
out.

thanks,

greg k-h

  reply	other threads:[~2010-11-27  0:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22 19:15 Linux 2.6.32.26 Greg KH
2010-11-22 19:15 ` Greg KH
2010-11-26 14:07 ` Xen domU kernel no longer shuts down (Was Linux 2.6.32.26) Alan J. Wylie
2010-11-26 22:38   ` Jeremy Fitzhardinge
2010-11-27  0:37     ` Greg KH [this message]
     [not found]     ` <AANLkTikH+GnpJCjYvn2+LDV30=kNMwNfkA94z+GRpJHG@mail.gmail.com>
2010-11-29 21:37       ` Alok Kataria
2010-11-29 22:10       ` Jeremy Fitzhardinge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101127003716.GA12074@suse.de \
    --to=gregkh@suse.de \
    --cc=alan@wylie.me.uk \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@eikelenboom.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox