From: Andi Kleen <ak@muc.de>
To: vgoyal@in.ibm.com
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Fastboot mailing list <fastboot@lists.osdl.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC][PATCH] kdump: x86_64 timer interrupt lockup due to pending interrupt
Date: Wed, 8 Mar 2006 06:31:55 +0100 [thread overview]
Message-ID: <200603080631.56754.ak@muc.de> (raw)
In-Reply-To: <20060308012654.GB25543@in.ibm.com>
> o Though today only timer seems to be the special case because in early
> boot it thinks interrupts are coming from i8259 and uses
> mask_and_ack_8259A() as ack handler and does not issue LAPIC EOI. But
> probably doing it in generic manner for all vectors makes sense.
Applied thanks.
Not sure if this is still 2.6.16 material though. Might be too late for that.
-Andi
prev parent reply other threads:[~2006-03-08 13:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 16:40 [RFC][PATCH] kdump: x86_64 timer interrupt lockup due to pending interrupt Vivek Goyal
2006-03-06 21:43 ` Andi Kleen
2006-03-07 22:20 ` Vivek Goyal
2006-03-07 23:43 ` Eric W. Biederman
2006-03-08 1:26 ` Vivek Goyal
2006-03-08 4:04 ` Eric W. Biederman
2006-03-08 5:31 ` Andi Kleen [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=200603080631.56754.ak@muc.de \
--to=ak@muc.de \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox