From: "H. Peter Anvin" <hpa@zytor.com>
To: akataria@vmware.com
Cc: "jeremy@xensource.com" <jeremy@xensource.com>,
Daniel Hecht <dhecht@vmware.com>,
the arch/x86 maintainers <x86@kernel.org>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Haren Myneni <hbabu@us.ibm.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Ingo Molnar <mingo@elte.hu>, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [RFC PATCH] Bug during kexec...not all cpus are stopped
Date: Thu, 21 Oct 2010 14:24:42 -0700 [thread overview]
Message-ID: <4CC0AF9A.9050307@zytor.com> (raw)
In-Reply-To: <1287695406.27008.31.camel@ank32.eng.vmware.com>
On 10/21/2010 02:10 PM, Alok Kataria wrote:
>
> On Thu, 2010-10-21 at 13:26 -0700, H. Peter Anvin wrote:
>> On 10/21/2010 12:09 PM, Alok Kataria wrote:
>>>
>>> I don't think this patch was picked up for tip, now that the 2.6.37
>>> merge window is open can you please pick this up push it upstream.
>>> This patch fixes a legitimate regression, which was introduced during
>>> 2.6.30, by commit id 4ef702c10b5df18ab04921fc252c26421d4d6c75.
>>>
>>
>> It probably would have helped if the patch had had a proper patch header
>> and so on, and *in particular* not buried in a tree with [RFC PATCH].
>> RFC strongly implies that the patch is intended as a base for
>> discussion, and is explicitly not intended to be committed.
>
> I see, I have sent another mail with the patch.
>
I already took the patch and am running it through compile tests, but
that was mostly for future reference.
-hpa
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: akataria@vmware.com
Cc: Ingo Molnar <mingo@elte.hu>, Vivek Goyal <vgoyal@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
Haren Myneni <hbabu@us.ibm.com>,
the arch/x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Daniel Hecht <dhecht@vmware.com>,
"jeremy@xensource.com" <jeremy@xensource.com>
Subject: Re: [RFC PATCH] Bug during kexec...not all cpus are stopped
Date: Thu, 21 Oct 2010 14:24:42 -0700 [thread overview]
Message-ID: <4CC0AF9A.9050307@zytor.com> (raw)
In-Reply-To: <1287695406.27008.31.camel@ank32.eng.vmware.com>
On 10/21/2010 02:10 PM, Alok Kataria wrote:
>
> On Thu, 2010-10-21 at 13:26 -0700, H. Peter Anvin wrote:
>> On 10/21/2010 12:09 PM, Alok Kataria wrote:
>>>
>>> I don't think this patch was picked up for tip, now that the 2.6.37
>>> merge window is open can you please pick this up push it upstream.
>>> This patch fixes a legitimate regression, which was introduced during
>>> 2.6.30, by commit id 4ef702c10b5df18ab04921fc252c26421d4d6c75.
>>>
>>
>> It probably would have helped if the patch had had a proper patch header
>> and so on, and *in particular* not buried in a tree with [RFC PATCH].
>> RFC strongly implies that the patch is intended as a base for
>> discussion, and is explicitly not intended to be committed.
>
> I see, I have sent another mail with the patch.
>
I already took the patch and am running it through compile tests, but
that was mostly for future reference.
-hpa
next prev parent reply other threads:[~2010-10-21 21:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 20:34 [RFC PATCH] Bug during kexec...not all cpus are stopped Alok Kataria
2010-10-08 20:34 ` Alok Kataria
2010-10-11 17:09 ` Alok Kataria
2010-10-11 17:09 ` Alok Kataria
2010-10-11 18:07 ` Eric W. Biederman
2010-10-11 18:07 ` Eric W. Biederman
2010-10-11 19:41 ` Alok Kataria
2010-10-11 19:41 ` Alok Kataria
2010-10-11 21:17 ` Eric W. Biederman
2010-10-11 21:17 ` Eric W. Biederman
2010-10-11 21:37 ` Alok Kataria
2010-10-11 21:37 ` Alok Kataria
2010-10-21 21:40 ` [tip:x86/urgent] x86, kexec: Make sure to stop all CPUs before exiting the kernel tip-bot for Alok Kataria
2010-10-11 21:39 ` [RFC PATCH] Bug during kexec...not all cpus are stopped Vivek Goyal
2010-10-11 21:39 ` Vivek Goyal
2010-10-11 21:47 ` Alok Kataria
2010-10-11 21:47 ` Alok Kataria
2010-10-11 22:10 ` Eric W. Biederman
2010-10-11 22:10 ` Eric W. Biederman
2010-10-12 22:17 ` Vivek Goyal
2010-10-12 22:17 ` Vivek Goyal
2010-10-13 0:23 ` Alok Kataria
2010-10-13 0:23 ` Alok Kataria
2010-10-21 19:09 ` Alok Kataria
2010-10-21 19:09 ` Alok Kataria
2010-10-21 20:26 ` H. Peter Anvin
2010-10-21 20:26 ` H. Peter Anvin
2010-10-21 21:10 ` Alok Kataria
2010-10-21 21:10 ` Alok Kataria
2010-10-21 21:24 ` H. Peter Anvin [this message]
2010-10-21 21:24 ` H. Peter Anvin
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=4CC0AF9A.9050307@zytor.com \
--to=hpa@zytor.com \
--cc=akataria@vmware.com \
--cc=dhecht@vmware.com \
--cc=ebiederm@xmission.com \
--cc=hbabu@us.ibm.com \
--cc=jeremy@xensource.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vgoyal@redhat.com \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.