From: Martin Wilck <martin.wilck@fujitsu-siemens.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "vgoyal@in.ibm.com" <vgoyal@in.ibm.com>,
Haren Myneni <hbabu@us.ibm.com>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: PATCH/RFC: [kdump] fix APIC shutdown sequence
Date: Wed, 08 Aug 2007 20:22:54 +0200 [thread overview]
Message-ID: <46BA09FE.2070909@fujitsu-siemens.com> (raw)
In-Reply-To: <m1myx1c3lj.fsf@ebiederm.dsl.xmission.com>
Eric W. Biederman wrote:
>> I think a lot would be gained if disable_IO_APIC() would just mask the IRQs
>> (like the function in my patch does), and perhaps fix the dest ID, instead of
>> totally clearing the registers.
>
> Even masked we still won't see the EOI, because then we are in i8259
> mode. So masked versus totally cleared really should make no
> difference.
You are talking about EOI sent in the kdump kernel, correct? With my patch
the EOI (sent in the "old" kernel) is seen.
> I guess right now I can see work put into cleaning things up a little
> or not having to call disable_IO_APIC() at all. that was supposed
> to be a short term hack, until we fixed things properly.
>
> So far no one has been brave enough to mess with the kernel apic
> initialization order so we can remove disable_IO_APIC. If our
> goal isn't to fix things properly by removing the need for
> disable_IO_APIC I don't feel like putting much effort into this
> code path.
Who is working on this? Can you give a reference to a list of things that
would need to be done to do this right?
Martin
--
Martin Wilck
PRIMERGY System Software Engineer
FSC IP ESP DE6
Fujitsu Siemens Computers GmbH
Heinz-Nixdorf-Ring 1
33106 Paderborn
Germany
Tel: ++49 5251 8 15113
Fax: ++49 5251 8 20409
Email: mailto:martin.wilck@fujitsu-siemens.com
Internet: http://www.fujitsu-siemens.com
Company Details: http://www.fujitsu-siemens.com/imprint.html
next prev parent reply other threads:[~2007-08-08 18:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 15:08 Martin Wilck
2007-08-07 14:29 ` Vivek Goyal
2007-08-07 17:41 ` Martin Wilck
2007-08-08 1:04 ` Eric W. Biederman
2007-08-08 9:03 ` Martin Wilck
2007-08-08 9:33 ` Vivek Goyal
2007-08-08 12:04 ` Martin Wilck
2007-08-08 15:21 ` Eric W. Biederman
2007-08-08 17:35 ` Martin Wilck
2007-08-08 17:56 ` Eric W. Biederman
2007-08-08 18:22 ` Martin Wilck [this message]
2007-08-08 18:38 ` Martin Wilck
2007-08-08 10:36 ` Vivek Goyal
2007-08-08 14:06 ` Chip Coldwell
2007-08-08 14:42 ` Vivek Goyal
2007-08-08 18:15 ` Martin Wilck
2007-08-09 10:11 ` Vivek Goyal
2007-08-09 17:35 ` Martin Wilck
2007-08-07 19:44 ` Chip Coldwell
2007-08-08 0:29 ` Andrew Morton
2007-08-08 8:32 ` Martin Wilck
2007-08-08 11:38 ` Vivek Goyal
2007-08-08 18:07 ` Martin Wilck
2007-08-08 21:25 ` Eric W. Biederman
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=46BA09FE.2070909@fujitsu-siemens.com \
--to=martin.wilck@fujitsu-siemens.com \
--cc=ebiederm@xmission.com \
--cc=hbabu@us.ibm.com \
--cc=kexec@lists.infradead.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
Powered by JetHome