From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: xen-devel@lists.xensource.com
Subject: nmi cache weirdness???
Date: Thu, 14 Aug 2008 19:20:27 -0700 [thread overview]
Message-ID: <48A4E7EB.2080509@oracle.com> (raw)
This on a 4 CPU AMD box with 64G RAM.
cpu 0 receives ext NMI, calls kdb_nmi() from do_nmi().
asmlinkage void do_nmi(struct cpu_user_regs *regs)
{
unsigned int cpu = smp_processor_id();
unsigned char reason;
++nmi_count(cpu);
if ( nmi_callback(regs, cpu) )
return;
if ( nmi_watchdog )
nmi_watchdog_tick(regs);
#ifdef XEN_KDB_CONFIG
kdb_nmi(TRAP_nmi, regs);
#endif
....
}
kdb_nmi(..):
{
watchdog_disable();
set_nmi_callback(kdb_nmi_receive);
smp_send_nmi_allbutself();
......
}
However, in do_nmi(), nmi_callback still points to dummy (receiving cpus).
What'sinteresting is, if I put two print lines back to back with nothing
in between right at the beginning, then the first prints dummy but the
second prints kdb_nmi_receive. I'm at a complete loss. Does NMI change
cache protocol? I've been looking thru Intel/AMD manuals, but nothing....
Thanks,
Mukesh
next reply other threads:[~2008-08-15 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 2:20 Mukesh Rathor [this message]
2008-08-15 5:45 ` nmi cache weirdness??? Mukesh
2008-08-15 7:52 ` Keir Fraser
2008-08-16 3:36 ` Mukesh Rathor
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=48A4E7EB.2080509@oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=xen-devel@lists.xensource.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 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.