From: ebiederm@xmission.com (Eric W. Biederman)
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/14] kexec: apic-virtwire-on-shutdown.i386.patch
Date: 30 Aug 2004 12:02:50 -0600 [thread overview]
Message-ID: <m14qmkfqr9.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <Pine.LNX.4.58L.0408301437260.12806@blysk.ds.pg.gda.pl>
"Maciej W. Rozycki" <macro@linux-mips.org> writes:
> On Thu, 25 Aug 2004, Eric W. Biederman wrote:
>
> > I don't think the configuration you are worrying about where
> > both the ioapic and the local apic can both be put into virtual
> > wire mode is valid according to the mp specification. Although that
> > is probably a grey area in the specification.
>
> The spec doesn't preclude a configuration where the master i8259A is
> wired both to an I/O APIC input and to local APIC inputs. If this is the
> case, it's a sole discretion of the system manufacturer to choose which
> route for the "virtual wire" is used.
>
> I don't insist on doing exact LVT restoration as at this stage it
> shouldn't really matter and the firmware should reinitialize the APIC
> subsystem completely anyway. I just wanted to be sure you are aware of
> the issue.
Thanks. I will keep it in mind.
Actually now that I think about it I believe recent Intel chipsets
Tumwater/Lindenhurst work both ways but they have a bug that can
be triggered unless you are using the IOAPIC in virtual wire
mode.
In practice I still don't think it matters as everything across the
hub interface and PCI-e is message based and I don't think 2 messages
are generated. Still I will give it some thought.
Eric
prev parent reply other threads:[~2004-08-30 18:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 17:59 Eric W. Biederman
2004-08-23 12:12 ` Maciej W. Rozycki
2004-08-23 13:33 ` Eric W. Biederman
2004-08-25 19:22 ` Maciej W. Rozycki
2004-08-26 0:52 ` Eric W. Biederman
2004-08-30 12:43 ` Maciej W. Rozycki
2004-08-30 18:02 ` Eric W. Biederman [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=m14qmkfqr9.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.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
Powered by JetHome