From: ebiederm@xmission.com (Eric W. Biederman)
To: Adrian Bunk <bunk@stusta.de>
Cc: Linus Torvalds <torvalds@osdl.org>,
Tobias Diedrich <ranma+kernel@tdiedrich.de>,
Yinghai Lu <yinghai.lu@amd.com>, Andrew Morton <akpm@osdl.org>,
Andi Kleen <ak@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
mingo@redhat.com, discuss@x86-64.org
Subject: Re: [PATCH 4/4] x86_64 ioapic: Improve the heuristics for when check_timer fails.
Date: Mon, 08 Jan 2007 16:18:33 -0700 [thread overview]
Message-ID: <m1bql9gl9y.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20070108223355.GI6167@stusta.de> (Adrian Bunk's message of "Mon, 8 Jan 2007 23:33:55 +0100")
Adrian Bunk <bunk@stusta.de> writes:
> On Mon, Jan 08, 2007 at 02:45:00PM -0700, Eric W. Biederman wrote:
>> Adrian Bunk <bunk@stusta.de> writes:
>
> We just got a completely different bug reported that was confirmed to be
> caused by Andi's patch:
> AMD64/ATI : timer is running twice as fast as it should [1]
Odd. I didn't think Andi's code worked well enough that we could hit
anything but the default trust the BIOS case. I guess someone had
the right hardware to perform that miracle.
>> I really don't care how we do it, or in what timeframe. But what I have
>> posted is the only way I can see of making it better, than what we had
>> in 2.6.19.
>>...
>
> My whole point is that for 2.6.20, we can live with simply reverting
> Andi's commit.
>
> What to do for 2.6.21 is a completely different story.
That is where I figured we were when we first hit this bug.
I have always found the ways of stable tree maintainers to be
mysterious. Sometimes holding back code with minimal risk sometimes
insisting we cleanup things instead of reverting things.
So I have just decided to write the code and let other people figure
out when it should be merged :) And of course when my code has
problems to address them.
Eric
next prev parent reply other threads:[~2007-01-08 23:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5986589C150B2F49A46483AC44C7BCA490733F@ssvlexmb2.amd.com>
2007-01-03 6:23 ` 2.6.20-rc3: known unfixed regressions - x86_64 boot failure: "IO-APIC + timer doesn't work" Yinghai Lu
2007-01-08 0:55 ` Tobias Diedrich
2007-01-08 1:09 ` Linus Torvalds
2007-01-08 15:49 ` [PATCH 1/4] x86_64 io_apic: Implement remove_pin_to_irq Eric W. Biederman
2007-01-08 15:53 ` PATCH 2/4] x86_64 io_apic: Implement irq_from_pin Eric W. Biederman
2007-01-08 15:56 ` [PATCH 3/4] x86_64 io_apic: Implment update_irq0_entry Eric W. Biederman
2007-01-08 16:11 ` [PATCH 4/4] x86_64 ioapic: Improve the heuristics for when check_timer fails Eric W. Biederman
2007-01-08 20:21 ` Adrian Bunk
2007-01-08 21:45 ` Eric W. Biederman
2007-01-08 22:33 ` Adrian Bunk
2007-01-08 22:57 ` Linus Torvalds
2007-01-08 23:14 ` [discuss] " Andi Kleen
2007-01-08 23:21 ` Adrian Bunk
2007-01-08 23:18 ` Eric W. Biederman [this message]
2007-01-09 22:00 ` Tobias Diedrich
2007-01-08 17:16 Lu, Yinghai
2007-01-08 20:46 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2007-01-08 17:41 Lu, Yinghai
2007-01-08 20:39 ` Eric W. Biederman
2007-01-08 20:53 Lu, Yinghai
2007-01-08 21:33 ` Eric W. Biederman
2007-01-09 22:15 Lu, Yinghai
2007-01-10 10:30 ` Tobias Diedrich
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=m1bql9gl9y.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ranma+kernel@tdiedrich.de \
--cc=torvalds@osdl.org \
--cc=yinghai.lu@amd.com \
/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