From: Andrew Morton <akpm@linux-foundation.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
john stultz <johnstul@us.ibm.com>
Subject: Re: 2.6.22-rc6-mm1
Date: Sat, 14 Jul 2007 02:07:13 -0700 [thread overview]
Message-ID: <20070714020713.36f604d2.akpm@linux-foundation.org> (raw)
In-Reply-To: <469879A2.1000002@shaw.ca>
On Sat, 14 Jul 2007 01:22:10 -0600 Robert Hancock <hancockr@shaw.ca> wrote:
> Andrew Morton wrote:
> > +x86_64-dynticks-disable-hpet_id_legsup-hpets.patch
> >
> > pretend to fix it
>
> I'm not sure what this patch does on x86_64, but it seems like it
> trashes all HPET support on i386?
>
It might do, if your i386 is old and has the HPET_ID_LEGSUP bit set.
The code path which that patch disables:
--- a/arch/i386/kernel/hpet.c~x86_64-dynticks-disable-hpet_id_legsup-hpets
+++ a/arch/i386/kernel/hpet.c
@@ -376,7 +376,7 @@ int __init hpet_enable(void)
clocksource_register(&clocksource_hpet);
- if (id & HPET_ID_LEGSUP) {
+ if (0 && (id & HPET_ID_LEGSUP)) {
hpet_enable_int();
hpet_reserve_platform_timers(id);
/*
_
will, if executed (on x86_64, at least), instaoops the machine. It might
take down i386 as well, dunno.
I'd forgotten about this problem, and it seems that Thomas & John have too.
It's a showstopper.
next prev parent reply other threads:[~2007-07-14 9:08 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.GKNLH/oj9PSCnQCxx9ZAggjc5uA@ifi.uio.no>
[not found] ` <fa.WYdi9Gj/0/XomcQpW4CEW5a4kKI@ifi.uio.no>
2007-06-29 0:58 ` 2.6.22-rc6-mm1 Intel DMAR crash on AMD x86_64 Robert Hancock
2007-06-29 1:14 ` Li, Shaohua
2007-06-29 15:28 ` Keshavamurthy, Anil S
2007-06-29 16:23 ` Muli Ben-Yehuda
2007-06-29 19:23 ` Keshavamurthy, Anil S
2007-06-29 21:18 ` Muli Ben-Yehuda
2007-06-30 19:50 ` Andi Kleen
2007-06-29 21:56 ` Rafael J. Wysocki
2007-07-14 7:22 ` 2.6.22-rc6-mm1 Robert Hancock
2007-07-14 9:07 ` Andrew Morton [this message]
2007-07-14 18:23 ` 2.6.22-rc6-mm1 Thomas Gleixner
2007-06-28 10:43 2.6.22-rc6-mm1 Andrew Morton
2007-06-28 12:08 ` 2.6.22-rc6-mm1 Gabriel C
2007-06-28 17:54 ` 2.6.22-rc6-mm1 Andrew Morton
2007-06-29 12:32 ` 2.6.22-rc6-mm1 Mariusz Kozlowski
2007-06-29 12:54 ` 2.6.22-rc6-mm1 Sergei Shtylyov
2007-07-02 13:49 ` 2.6.22-rc6-mm1 Jason Wessel
2007-07-02 14:23 ` 2.6.22-rc6-mm1 Sergei Shtylyov
2007-07-02 14:45 ` 2.6.22-rc6-mm1 Jason Wessel
2007-07-02 23:21 ` 2.6.22-rc6-mm1 Paul Mackerras
2007-06-29 20:47 ` 2.6.22-rc6-mm1 Andrew Morton
2007-06-30 8:40 ` 2.6.22-rc6-mm1 Michal Marek
2007-06-29 14:17 ` 2.6.22-rc6-mm1 Roman Zippel
2007-06-29 20:58 ` 2.6.22-rc6-mm1 Andrew Morton
2007-07-01 1:48 ` 2.6.22-rc6-mm1 Roman Zippel
2007-06-29 14:50 ` 2.6.22-rc6-mm1 Valdis.Kletnieks
2007-06-29 21:01 ` 2.6.22-rc6-mm1 Andrew Morton
2007-06-30 4:17 ` 2.6.22-rc6-mm1 Valdis.Kletnieks
2007-06-30 5:15 ` 2.6.22-rc6-mm1 Andrew Morton
2007-06-30 16:22 ` 2.6.22-rc6-mm1 Jeremy Fitzhardinge
2007-06-30 21:10 ` 2.6.22-rc6-mm1 Sam Ravnborg
2007-06-30 21:39 ` 2.6.22-rc6-mm1 Andrew Morton
2007-07-01 1:53 ` 2.6.22-rc6-mm1 Roman Zippel
2007-07-03 20:36 ` 2.6.22-rc6-mm1 Andrew Morton
2007-07-01 5:31 ` 2.6.22-rc6-mm1 Satyam Sharma
2007-07-01 6:52 ` 2.6.22-rc6-mm1 Sam Ravnborg
2007-07-06 21:31 ` 2.6.22-rc6-mm1 Badari Pulavarty
2007-07-14 0:58 ` 2.6.22-rc6-mm1 Nish Aravamudan
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=20070714020713.36f604d2.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hancockr@shaw.ca \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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