From: Vivek Goyal <vgoyal@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Robin Holt <robinmholt@gmail.com>, Baoquan He <bhe@redhat.com>,
mwhitehe@redhat.com, x86@kernel.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, Robin Holt <robinmholt@linux.com>,
davej@fedoraproject.org, mingo@redhat.com,
"Eric W. Biederman" <ebiederm@xmission.com>,
rmk+kernel@arm.linux.org.uk, tglx@linutronix.de,
chaowang@redhat.com
Subject: Re: [PATCH] x86: make reboot task only run on the appropriate processor
Date: Mon, 11 Nov 2013 10:57:11 -0500 [thread overview]
Message-ID: <20131111155711.GB11547@redhat.com> (raw)
In-Reply-To: <469ce80c-c6a0-4238-aab5-9a4d8c562387@email.android.com>
On Mon, Nov 11, 2013 at 07:39:18AM -0800, H. Peter Anvin wrote:
> Yes, unless there is a better path for it since it is not x86-specific. I am fine taking it, though.
Generally Andrew Morton routes kexec/kdump patches through his tree. Andrew,
do you think it should go through your tree?
Thanks
Vivek
>
> Vivek Goyal <vgoyal@redhat.com> wrote:
> >On Fri, Nov 08, 2013 at 08:12:00AM -0800, H. Peter Anvin wrote:
> >> On 11/08/2013 07:14 AM, Vivek Goyal wrote:
> >> >
> >> > Hi Bao,
> >> >
> >> > This patch fixes the issue for me too. I noticed that we have
> >generic
> >> > function migrate_to_reboot_cpu() to achieve what we want and rest
> >of
> >> > the reboot paths are using it. So how about using that function. I
> >> > wrote the new patch below. It works for me. Can you please give it
> >> > a try.
> >> >
> >> > Thanks
> >> > Vivek
> >> >
> >>
> >> Is this path exercised for the kdump flow? migrate_to_reboot_cpu()
> >is
> >> unsafe in that case.
> >
> >Hi Peter,
> >
> >Can you please consider queuing up this patch for next release.
> >
> >Thanks
> >Vivek
> >
> >>
> >> > Index: linux-2.6/kernel/kexec.c
> >> > ===================================================================
> >> > --- linux-2.6.orig/kernel/kexec.c 2013-10-16 00:30:50.000000000
> >-0400
> >> > +++ linux-2.6/kernel/kexec.c 2013-11-08 21:34:02.492072375 -0500
> >> > @@ -1676,6 +1676,7 @@ int kernel_kexec(void)
> >> > #endif
> >> > {
> >> > kernel_restart_prepare(NULL);
> >> > + migrate_to_reboot_cpu();
> >> > printk(KERN_EMERG "Starting new kernel\n");
> >> > machine_shutdown();
> >> > }
> >> >
>
> --
> Sent from my mobile phone. Please pardon brevity and lack of formatting.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Baoquan He <bhe@redhat.com>,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, x86@kernel.org, davej@fedoraproject.org,
rmk+kernel@arm.linux.org.uk, chaowang@redhat.com,
mwhitehe@redhat.com, kexec@lists.infradead.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Robin Holt <robinmholt@linux.com>,
Robin Holt <robinmholt@gmail.com>
Subject: Re: [PATCH] x86: make reboot task only run on the appropriate processor
Date: Mon, 11 Nov 2013 10:57:11 -0500 [thread overview]
Message-ID: <20131111155711.GB11547@redhat.com> (raw)
In-Reply-To: <469ce80c-c6a0-4238-aab5-9a4d8c562387@email.android.com>
On Mon, Nov 11, 2013 at 07:39:18AM -0800, H. Peter Anvin wrote:
> Yes, unless there is a better path for it since it is not x86-specific. I am fine taking it, though.
Generally Andrew Morton routes kexec/kdump patches through his tree. Andrew,
do you think it should go through your tree?
Thanks
Vivek
>
> Vivek Goyal <vgoyal@redhat.com> wrote:
> >On Fri, Nov 08, 2013 at 08:12:00AM -0800, H. Peter Anvin wrote:
> >> On 11/08/2013 07:14 AM, Vivek Goyal wrote:
> >> >
> >> > Hi Bao,
> >> >
> >> > This patch fixes the issue for me too. I noticed that we have
> >generic
> >> > function migrate_to_reboot_cpu() to achieve what we want and rest
> >of
> >> > the reboot paths are using it. So how about using that function. I
> >> > wrote the new patch below. It works for me. Can you please give it
> >> > a try.
> >> >
> >> > Thanks
> >> > Vivek
> >> >
> >>
> >> Is this path exercised for the kdump flow? migrate_to_reboot_cpu()
> >is
> >> unsafe in that case.
> >
> >Hi Peter,
> >
> >Can you please consider queuing up this patch for next release.
> >
> >Thanks
> >Vivek
> >
> >>
> >> > Index: linux-2.6/kernel/kexec.c
> >> > ===================================================================
> >> > --- linux-2.6.orig/kernel/kexec.c 2013-10-16 00:30:50.000000000
> >-0400
> >> > +++ linux-2.6/kernel/kexec.c 2013-11-08 21:34:02.492072375 -0500
> >> > @@ -1676,6 +1676,7 @@ int kernel_kexec(void)
> >> > #endif
> >> > {
> >> > kernel_restart_prepare(NULL);
> >> > + migrate_to_reboot_cpu();
> >> > printk(KERN_EMERG "Starting new kernel\n");
> >> > machine_shutdown();
> >> > }
> >> >
>
> --
> Sent from my mobile phone. Please pardon brevity and lack of formatting.
next prev parent reply other threads:[~2013-11-11 15:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 9:16 [PATCH] x86: make reboot task only run on the appropriate processor Baoquan He
2013-11-05 9:16 ` Baoquan He
2013-11-05 20:28 ` Vivek Goyal
2013-11-05 20:28 ` Vivek Goyal
2013-11-05 21:39 ` H. Peter Anvin
2013-11-05 21:39 ` H. Peter Anvin
2013-11-06 9:48 ` Baoquan He
2013-11-06 9:48 ` Baoquan He
2013-11-07 2:20 ` Baoquan He
2013-11-07 2:20 ` Baoquan He
2013-11-08 1:33 ` Dave Young
2013-11-08 1:33 ` Dave Young
2013-11-08 15:14 ` Vivek Goyal
2013-11-08 15:14 ` Vivek Goyal
2013-11-08 16:12 ` H. Peter Anvin
2013-11-08 16:12 ` H. Peter Anvin
2013-11-08 16:24 ` Vivek Goyal
2013-11-08 16:24 ` Vivek Goyal
2013-11-11 15:29 ` Vivek Goyal
2013-11-11 15:29 ` Vivek Goyal
2013-11-11 15:39 ` H. Peter Anvin
2013-11-11 15:39 ` H. Peter Anvin
2013-11-11 15:57 ` Vivek Goyal [this message]
2013-11-11 15:57 ` Vivek Goyal
2013-11-11 16:02 ` H. Peter Anvin
2013-11-11 16:02 ` H. Peter Anvin
2013-11-10 9:44 ` Baoquan He
2013-11-10 9:44 ` Baoquan He
2013-11-11 6:52 ` Baoquan He
2013-11-11 6:52 ` Baoquan He
2013-11-11 6:55 ` WANG Chao
2013-11-11 6:55 ` WANG Chao
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=20131111155711.GB11547@redhat.com \
--to=vgoyal@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=chaowang@redhat.com \
--cc=davej@fedoraproject.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mwhitehe@redhat.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=robinmholt@gmail.com \
--cc=robinmholt@linux.com \
--cc=tglx@linutronix.de \
--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.