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: 25 Aug 2004 18:52:37 -0600 [thread overview]
Message-ID: <m1vff6vhyi.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <Pine.LNX.4.58L.0408252118150.18088@blysk.ds.pg.gda.pl>
"Maciej W. Rozycki" <macro@linux-mips.org> writes:
> On Mon, 23 Aug 2004, Eric W. Biederman wrote:
>
> > The local apic still needs to be put into virtual wire mode in that
> > case.
>
> Well, depending on actual wiring you may need to mask LINT0 in this case
> to avoid duplicate interrupts. I think the safest approach would be
> remembering the initial values of LVT0 and LVT1 registers of the BSP --
> they are just four bytes each, so it would not be a terrible memory waste.
If I was seeing problems I guess I would worry about it. As I have
tested on both Opteron's which require the ioapic to be in
virtual wire mode, and on Xeons which require the local apic to be in
virtual wire mode and both work I am not too concerned.
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.
It is more code to save off and then restore the registers,
then simply hard coding a value into them.
It is nice to have hard coded values when you can as then
you don't have to guess how something was configured on this occasion.
As my code is simpler than your suggestion and it works I'm not
a fan of changing it until I see a case where it breaks.
Eric
next prev parent reply other threads:[~2004-08-26 0:54 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 [this message]
2004-08-30 12:43 ` Maciej W. Rozycki
2004-08-30 18:02 ` 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=m1vff6vhyi.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