From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: hpa@zytor.com, mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [patch 00/11] tip/x86/nmi nmi-32/64.c merge v3
Date: Sun, 25 May 2008 21:00:04 +0400 [thread overview]
Message-ID: <20080525170004.GA6911@cvg> (raw)
In-Reply-To: <alpine.LFD.1.10.0805251842360.3295@apollo.tec.linutronix.de>
[Thomas Gleixner - Sun, May 25, 2008 at 06:44:28PM +0200]
| On Sat, 24 May 2008, Cyrill Gorcunov wrote:
|
| > This series tries to merge down nmi_32/64.c to nmi.c. It is done by small
| > steps in hope it would help to bisect problems (which will appear anyway ;)
| > Please review *carefully* since it is NMI what I've touched (and I'm not
| > nmi specialist). So I really apreciate _ANY_ comments on this. The series
| > is produced over today 'tip' tree branch 'x86/nmi'.
|
| Cyrill,
|
| very good job. I did a short review and found no obvious problems
| yet. Will have a closer look when I apply it.
|
| Thanks,
| tglx
|
|
|
thanks Thomas, unfortunelly I think the problems will arise soon,
I've just noticed the commit
commit 57b2b8947a5f68e59d5f50ab749efdc79d9ba040
Author: Mike Travis <travis@sgi.com>
Date: Mon May 12 21:21:12 2008 +0200
x86: fix remove cpu_pda table patch
in tip/testing tree
so we will need some workaround for check_nmi_watchdog() 'cause of changing
...
- prev_nmi_count = kmalloc(NR_CPUS * sizeof(int), GFP_KERNEL);
+ prev_nmi_count = kmalloc(nr_cpu_ids * sizeof(int), GFP_KERNEL);
...
- for (cpu = 0; cpu < NR_CPUS; cpu++)
+ for (cpu = 0; cpu < nr_cpu_ids; cpu++)
...
didn't take a precise look on this, but will take as only be able to ;)
- Cyrill -
next prev parent reply other threads:[~2008-05-25 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-24 15:36 [patch 00/11] tip/x86/nmi nmi-32/64.c merge v3 Cyrill Gorcunov
2008-05-25 16:44 ` Thomas Gleixner
2008-05-25 17:00 ` Cyrill Gorcunov [this message]
2008-05-25 17:07 ` Thomas Gleixner
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=20080525170004.GA6911@cvg \
--to=gorcunov@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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