From: Chuck Ebbert <76306.1226@compuserve.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
"kernel-stuff@comcast.net" <kernel-stuff@comcast.net>,
Andi Kleen <ak@suse.de>
Subject: Re: X86_64: Many Lost ticks
Date: Mon, 22 Nov 2004 10:11:01 -0500 [thread overview]
Message-ID: <200411221012_MC3-1-8F2C-FF45@compuserve.com> (raw)
Zwane Mwaikambo wrote:
> The thing is, without the IOAPIC enable it's essentially a no operation
> since i8259 mode wouldn't use the pin information.
...until the user force-enables the IOAPIC. Then the timer pin
overrides will be ignored as they should be.
My goal was to fix bugs without altering default behavior, so anyone with
broken IOAPIC mode would not suddenly see problems unless they changed a
startup parameter.
--Chuck Ebbert 20-Nov-04 23:58:19
next reply other threads:[~2004-11-22 15:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 15:11 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-19 8:19 X86_64: Many Lost ticks Chuck Ebbert
2004-11-19 16:11 ` Zwane Mwaikambo
2004-11-18 19:30 kernel-stuff
2004-11-18 19:03 kernel-stuff
2004-11-18 17:19 kernel-stuff
2004-11-18 17:02 kernel-stuff
2004-11-18 17:08 ` Zwane Mwaikambo
2004-11-18 17:10 ` Alan Cox
2004-11-18 18:24 ` Zwane Mwaikambo
2004-11-18 18:50 ` Andi Kleen
2004-11-18 18:49 ` Andi Kleen
2004-11-19 1:56 ` kernel-stuff
2004-11-19 15:57 ` Zwane Mwaikambo
2004-11-20 0:17 ` kernel-stuff
2004-11-20 2:39 ` Alan Cox
2004-11-18 4:14 kernel-stuff
2004-11-18 4:02 kernel-stuff
2004-11-18 5:06 ` Andi Kleen
2004-11-18 15:54 ` Zwane Mwaikambo
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=200411221012_MC3-1-8F2C-FF45@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kernel-stuff@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linuxpower.ca \
/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;
as well as URLs for NNTP newsgroup(s).