[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <p734po33hhl.fsf@bingen.suse.de>
Date: 29 Mar 2007 22:46:46 +0200
From: Andi Kleen <andi@...stfloor.org>
To: Ingo Molnar <mingo@...e.hu>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Maxim Levitsky <maximlevitsky@...il.com>,
Jeff Chua <jeff.chua.linux@...il.com>,
linux-ide@...r.kernel.org,
Sergei Shtylyov <sshtylyov@...mvista.com>, gregkh@...e.de,
linux-pm@...ts.osdl.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Adrian Bunk <bunk@...sta.de>, linux-acpi@...r.kernel.org,
linux-pci@...ey.karlin.mff.cuni.cz,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Jens Axboe <jens.axboe@...cle.com>,
"Michael S. Tsirkin" <mst@...lanox.co.il>,
Thomas Gleixner <tglx@...utronix.de>, jgarzik@...ox.com,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH v2] Add suspend/resume for HPET
Ingo Molnar <mingo@...e.hu> writes:
>
> there's no fundamental reason. x86_64 COW-ed hpet_timer.c and
> time_hpet.c years ago and drifted off into different areas.
Not quite -- x86-64 did HPET long before i386; the only stuff cowed
was the character driver support code. But the core HPET code
was always totally different code streams. We never did the complicated
pluggable clock code i386 did though -- i never quite saw the point of that
because there aren't that many timers there.
Of course it is already obsolete with clocksources now.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists