All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: vgoyal@in.ibm.com
Cc: Fernando Luis Vazquez Cao <fernando@intellilink.co.jp>,
	fastboot@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [Fastboot] Re: [PATCH & RFC] kdump and stack overflows
Date: Tue, 29 Nov 2005 09:46:21 -0700	[thread overview]
Message-ID: <m18xv7fllu.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20051129132730.GA3803@in.ibm.com> (Vivek Goyal's message of "Tue, 29 Nov 2005 18:57:30 +0530")

Vivek Goyal <vgoyal@in.ibm.com> writes:

> On Mon, Nov 28, 2005 at 11:29:29AM -0700, Eric W. Biederman wrote:
>> (baring
>> nmi happening during nmis)  Hmm.  Is there anything to keep
>> us doing something bad in that case?
>> 
>> I guess as long as we don't clear the high bit of port 0x70 we
>> should be reasonably safe from the nmi firing multiple times.
>
> Are you referring to port 0x23 for IMCR register.

No.  Port 0x70 is the cmos address register.  0x71 the cmos
data register.  The high bit of 0x70 if the nmi enable.

Although with local apics generating nmis I would be surprised
if it effective in every case. :)

Eric


  reply	other threads:[~2005-11-29 16:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-28 13:11 [PATCH & RFC] kdump and stack overflows Fernando Luis Vazquez Cao
2005-11-28 13:39 ` Eric W. Biederman
2005-11-28 18:00   ` Fernando Luis Vazquez Cao
2005-11-28 18:29     ` Eric W. Biederman
2005-11-29 13:27       ` [Fastboot] " Vivek Goyal
2005-11-29 16:46         ` Eric W. Biederman [this message]
2005-11-29 15:43       ` Fernando Luis Vazquez Cao
2005-11-30  6:09       ` [Fastboot] " Vivek Goyal

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=m18xv7fllu.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=fernando@intellilink.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@in.ibm.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.