From: Andi Kleen <ak@muc.de>
To: Andreas Deresch <aderesch@fs.tum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: panic during IO-APIC detection
Date: Tue, 15 Feb 2005 21:12:41 +0100 [thread overview]
Message-ID: <m1sm3xh9ae.fsf@muc.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0502161701300.10460@Magrathea> (Andreas Deresch's message of "Wed, 16 Feb 2005 17:26:22 +0100 (CET)")
Andreas Deresch <aderesch@fs.tum.de> writes:
>
> The question is, should io_apic_get_unique_id be more fault tolerant, or
> where else should this be fixed?
Patch makes sense in theory, but I suspect there is more state to fix
up to get rid of the IO-APIC than just decreasing nr_ioapics.
-Andi
prev parent reply other threads:[~2005-02-15 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 16:26 panic during IO-APIC detection Andreas Deresch
2005-02-15 20:12 ` 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=m1sm3xh9ae.fsf@muc.de \
--to=ak@muc.de \
--cc=aderesch@fs.tum.de \
--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 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.