On 10/27/15 at 09:01am, 河合英宏 / KAWAI，HIDEHIRO wrote:
> Hi,
>
> > I just have a look at this thread. I am wondering why we don't use
> > existing is_kdump_kernel() directly to disable external NMI if it's
> > in kdump kernel. Then no need to introduce another boot option "noextnmi"
> > which is use
Hi,
> I just have a look at this thread. I am wondering why we don't use
> existing is_kdump_kernel() directly to disable external NMI if it's
> in kdump kernel. Then no need to introduce another boot option "noextnmi"
> which is used only for kdump kernel.
As I stated in another mail, there is a
Hi,
I just have a look at this thread. I am wondering why we don't use
existing is_kdump_kernel() directly to disable external NMI if it's
in kdump kernel. Then no need to introduce another boot option "noextnmi"
which is used only for kdump kernel.
Thanks
Baoquan
On 09/25/15 at 08:28pm, Hidehir
> > By the way, I have a pending patch which expands this option like
> > this:
> >
> > apic_extnmi={ bsp | all | none }
> >
> > If apic_extnmi=all is specified, external NMIs are broadcast to
> > all CPUs. This raises the successful rate of kernel panic in the case
> > where an external NMI t
> * Thomas Gleixner wrote:
>
> > Borislav,
> >
> > On Mon, 5 Oct 2015, Borislav Petkov wrote:
> > > On Mon, Oct 05, 2015 at 02:03:58AM +, 河合英宏 / KAWAI，HIDEHIRO wrote:
> > > > That's different from my point of view. I'm not going to pass
> > > > some data from the first kernel to the second k
* Thomas Gleixner wrote:
> Borislav,
>
> On Mon, 5 Oct 2015, Borislav Petkov wrote:
> > On Mon, Oct 05, 2015 at 02:03:58AM +, 河合英宏 / KAWAI，HIDEHIRO wrote:
> > > That's different from my point of view. I'm not going to pass
> > > some data from the first kernel to the second kernel. I'm jus
> On Fri, 25 Sep 2015, Hidehiro Kawai wrote:
>
> > This patch introduces new boot option "noextnmi" which disables
> > external NMI. This option is useful for the dump capture kernel
> > so that an HA application or administrator wouldn't mistakenly
> > shoot down the kernel by NMI.
> >
> > Curre
On Fri, 25 Sep 2015, Hidehiro Kawai wrote:
> This patch introduces new boot option "noextnmi" which disables
> external NMI. This option is useful for the dump capture kernel
> so that an HA application or administrator wouldn't mistakenly
> shoot down the kernel by NMI.
>
> Currently, only x86
Hello, Boris
Sorry for the late reply.
> On Mon, Oct 05, 2015 at 09:21:02AM +, 河合英宏 / KAWAI，HIDEHIRO wrote:
> > So, the problem for you is that "noextnmi" option is visible and effective
> > in the first kernel, isn't it?
>
> No, such an option shouldn't exist at all. You should be passing
>
On Mon, Oct 05, 2015 at 09:21:02AM +, 河合英宏 / KAWAI，HIDEHIRO wrote:
> So, the problem for you is that "noextnmi" option is visible and effective
> in the first kernel, isn't it?
No, such an option shouldn't exist at all. You should be passing
information *in* *a* *different* *manner* to the kdu
> On Mon, Oct 05, 2015 at 02:03:58AM +, 河合英宏 / KAWAI，HIDEHIRO wrote:
> > That's different from my point of view. I'm not going to pass
> > some data from the first kernel to the second kernel. I'm just going to
> > provide a configurable option for the second kernel to users.
>
> Dude, WTF?!
On Mon, Oct 05, 2015 at 02:03:58AM +, 河合英宏 / KAWAI，HIDEHIRO wrote:
> That's different from my point of view. I'm not going to pass
> some data from the first kernel to the second kernel. I'm just going to
> provide a configurable option for the second kernel to users.
Dude, WTF?! You're addin
> On Fri, Oct 02, 2015 at 12:58:02AM +, 河合英宏 / KAWAI，HIDEHIRO wrote:
> > > On Thu, Oct 01, 2015 at 10:24:19AM +, 河合英宏 / KAWAI，HIDEHIRO wrote:
> > > > But how do we check if the starting kernel is a dump capture kernel?
> > >
> > > How does that first kernel pass info to the capture kernel?
On Fri, Oct 02, 2015 at 12:58:02AM +, 河合英宏 / KAWAI，HIDEHIRO wrote:
> > On Thu, Oct 01, 2015 at 10:24:19AM +, 河合英宏 / KAWAI，HIDEHIRO wrote:
> > > But how do we check if the starting kernel is a dump capture kernel?
> >
> > How does that first kernel pass info to the capture kernel?
>
> As I
> On Thu, Oct 01, 2015 at 10:24:19AM +, 河合英宏 / KAWAI，HIDEHIRO wrote:
> > But how do we check if the starting kernel is a dump capture kernel?
>
> How does that first kernel pass info to the capture kernel?
As I described in the previous mail, You just have to add "noextnmi"
to KDUMP_COMMANDLI
On Thu, Oct 01, 2015 at 10:24:19AM +, 河合英宏 / KAWAI，HIDEHIRO wrote:
> But how do we check if the starting kernel is a dump capture kernel?
How does that first kernel pass info to the capture kernel?
> I think using cmdline option is the simplest way.
More often than not, simplest != correct.
> On Thu, Oct 01, 2015 at 07:01:50AM +, 河合英宏 / KAWAI，HIDEHIRO wrote:
> > I suppose that a sever which uses this feature will equip a BMC
> > and BMC mandatorily supports hard reset command for the server.
> > If the HA clustering software detects no response from the server
> > after relatively
On Thu, Oct 01, 2015 at 07:01:50AM +, 河合英宏 / KAWAI，HIDEHIRO wrote:
> I suppose that a sever which uses this feature will equip a BMC
> and BMC mandatorily supports hard reset command for the server.
> If the HA clustering software detects no response from the server
> after relatively long time
> On Thu, Oct 01, 2015 at 02:33:18AM +, 河合英宏 / KAWAI，HIDEHIRO wrote:
> > > On Fri, Sep 25, 2015 at 08:28:11PM +0900, Hidehiro Kawai wrote:
> > > > This patch introduces new boot option "noextnmi" which disables
> > > > external NMI. This option is useful for the dump capture kernel
> > > > so
On Thu, Oct 01, 2015 at 02:33:18AM +, 河合英宏 / KAWAI，HIDEHIRO wrote:
> > On Fri, Sep 25, 2015 at 08:28:11PM +0900, Hidehiro Kawai wrote:
> > > This patch introduces new boot option "noextnmi" which disables
> > > external NMI. This option is useful for the dump capture kernel
> > > so that an HA
> On Fri, Sep 25, 2015 at 08:28:11PM +0900, Hidehiro Kawai wrote:
> > This patch introduces new boot option "noextnmi" which disables
> > external NMI. This option is useful for the dump capture kernel
> > so that an HA application or administrator wouldn't mistakenly
> > shoot down the kernel by
On Fri, Sep 25, 2015 at 08:28:11PM +0900, Hidehiro Kawai wrote:
> This patch introduces new boot option "noextnmi" which disables
> external NMI. This option is useful for the dump capture kernel
> so that an HA application or administrator wouldn't mistakenly
> shoot down the kernel by NMI.
So t
22 matches
Mail list logo
