From: Cyrill Gorcunov <gorcunov@openvz.org>
To: Dongdong Deng <libfetion@gmail.com>
Cc: Jason Wessel <jason.wessel@windriver.com>,
Ingo Molnar <mingo@redhat.com>, Lin Ming <ming.m.lin@intel.com>,
Don Zickus <dzickus@redhat.com>,
lkml <linux-kernel@vger.kernel.org>,
KGDB Mailing List <Kgdb-bugreport@lists.sourceforge.net>
Subject: Re: [PATCH -tip] kgdb, x86: Pull up NMI notifier handler priority
Date: Fri, 01 Apr 2011 15:39:22 +0400 [thread overview]
Message-ID: <4D95B96A.3090600@openvz.org> (raw)
In-Reply-To: <AANLkTikhbKnMuOuVxHSWk2stNGgvEBO1XvGAQ1tVMc8s@mail.gmail.com>
On 04/01/2011 01:26 PM, Dongdong Deng wrote:
...
>>
>> The net result. I'll sign-off on the kgdb change and add a TODO item to wait for the jump patching to enter the kernel.
>>
>> Cyrill, I am assuming this is something we want to aim to merge into the 2.6.39 as a regression fix? I'll try to get a
>> version of Deng Dongdong's patch into linux-next as soon as possible in the mean time.
>
> Hi Jason,
>
> Do I need to send a patch to you? :-)
>
> BR,
> Dongdong
I've started latest -tip on some ancient p4 machine today and got unknown nmi issue even without kgdb compiled :(
Didn't reveal all the details yet (seems I'll be able to continue investigation at monday only in best case).
But still your patch looks correct to me.
--
Cyrill
prev parent reply other threads:[~2011-04-01 11:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 20:32 [PATCH -tip] kgdb, x86: Pull up NMI notifier handler priority Cyrill Gorcunov
2011-03-23 21:16 ` Don Zickus
2011-03-23 21:33 ` Cyrill Gorcunov
2011-03-24 3:30 ` Dongdong Deng
2011-03-24 5:24 ` Cyrill Gorcunov
2011-03-31 17:40 ` Jason Wessel
2011-03-31 20:25 ` Cyrill Gorcunov
2011-04-01 9:26 ` Dongdong Deng
2011-04-01 11:39 ` Cyrill Gorcunov [this message]
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=4D95B96A.3090600@openvz.org \
--to=gorcunov@openvz.org \
--cc=Kgdb-bugreport@lists.sourceforge.net \
--cc=dzickus@redhat.com \
--cc=jason.wessel@windriver.com \
--cc=libfetion@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).