From: Vivek Goyal <vgoyal@in.ibm.com>
To: Andi Kleen <ak@muc.de>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Fastboot mailing list <fastboot@lists.osdl.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Morton Andrew Morton <akpm@osdl.org>
Subject: Inclusion of x86_64 memorize ioapic at bootup patch
Date: Tue, 3 Jan 2006 10:16:32 +0530 [thread overview]
Message-ID: <20060103044632.GA4969@in.ibm.com> (raw)
Hi Andi,
Can you please include the following patch. This patch has already been pushed
by Andrew.
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc5/2.6.15-rc5-mm3/broken-out/x86_64-io_apicc-memorize-at-bootup-where-the-i8259-is.patch
This patch is regarding remembering at boot up time where i8259 is connected
and restore the APIC settings back during kexec boot or kdump boot. This
enables getting timer interrupts in new kernel in legacy mode.
This patch is needed to make kexec and kdump work on some systems,
especially opteron boxes. Otherwise the second kernel does not receive
timer interrupts during early boot hence hangs.
I understand, that you are inclined towards remembering all the APIC states
and simply restore it back instead of putting hooks. This will work
well for kexec but not for kdump because in kdump system can crash on
non-boot cpu.
Restoring BIOS APIC state can make sure that BIOS designated boot cpu will
always be able to see timer interrupts in legacy mode but same does not
hold good if new kernel boots on some other cpu as is the case with kdump.
In case of kexec boot, we relocate to boot cpu but in case of kdump we
don't because it was suggested that in some extreme cases of crash, boot cpu
might not respond even to NMI and relocation to boot cpu will not be
possible.
Can you please re-consider this patch for inclusion.
Thanks
Vivek
next reply other threads:[~2006-01-03 4:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 4:46 Vivek Goyal [this message]
2006-01-06 0:30 ` Inclusion of x86_64 memorize ioapic at bootup patch Yinghai Lu
2006-01-06 0:38 ` Andrew Morton
2006-01-06 4:50 ` Vivek Goyal
2006-01-06 8:02 ` Eric W. Biederman
2006-01-06 15:26 ` [LinuxBIOS] " Ronald G Minnich
2006-01-06 18:59 ` Andi Kleen
2006-01-06 8:14 ` [PATCH] i386 io_apic: Use correct index variable when computing the apic that is in ExtInt mode Eric W. Biederman
2006-01-06 8:20 ` [PATCH] x86_64 io_apic: memorize at bootup where the i8259 is Eric W. Biederman
2006-01-07 0:44 ` Yinghai Lu
2006-01-07 1:29 ` [PATCH] x86_64 io_apic: memorize at bootup where the i8259 is (typo fix) Eric W. Biederman
2006-01-06 8:24 ` Inclusion of x86_64 memorize ioapic at bootup patch Eric W. Biederman
2006-01-06 23:48 ` Andi Kleen
2006-01-07 0:00 ` Yinghai Lu
2006-01-07 0:29 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2006-01-07 0:35 Lu, Yinghai
2006-01-07 1:14 ` Eric W. Biederman
2006-01-07 1:32 Lu, Yinghai
2006-01-07 2:32 ` yhlu
2006-01-07 6:38 ` yhlu
2006-01-07 7:20 ` yhlu
2006-01-07 9:43 ` yhlu
2006-01-07 12:46 ` Eric W. Biederman
2006-01-07 19:36 ` yhlu
2006-01-07 19:44 ` Eric W. Biederman
2006-01-07 21:35 ` yhlu
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=20060103044632.GA4969@in.ibm.com \
--to=vgoyal@in.ibm.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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