From: "Jan Beulich" <JBeulich@novell.com>
To: "Andi Kleen" <ak@suse.de>
Cc: "Andrew Morton" <akpm@osdl.org>, "Rafael Wysocki" <rjw@sisk.pl>,
<linux-kernel@vger.kernel.org>,
"Discuss x86-64" <discuss@x86-64.org>
Subject: Re: [discuss] Re: 2.6.15-rc5-mm1 (x86_64-hpet-overflow.patch breaks resume from disk)
Date: Fri, 09 Dec 2005 11:57:30 +0100 [thread overview]
Message-ID: <4399712A.76F0.0078.0@novell.com> (raw)
In-Reply-To: <20051209091605.GE11190@wotan.suse.de>
>> >Also I think vgettimeofday doesn't handle 64bit HPET correctly
>> >yet. Also why does it not use hpet_readq?
>>
>> For the simple reason that there is no way to know whether the
entire
>> interconnect from CPU to HPET is (at least) 64 bits wide. At least
>> theoretically implementations are permitted to use 32-bit
components;
>> the HPET spec specifically warns about that.
>
>Doesn't that refer to the CPUs ?
No, all bus components and other chips between CPU and the implementing
chip (including the latter) must have 64-bit data paths and guarantee
not to break up 64-bit reads into pairs of 32-bit ones. Actually, it's
the other way around - since most modern 32-but x86 CPUs have (as far as
I know) 64-bit data busses, it is normally not the CPU that restricts
accesses to 32 bits.
Jan
next prev parent reply other threads:[~2005-12-09 10:56 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 7:21 2.6.15-rc5-mm1 Andrew Morton
2005-12-05 6:49 ` 2.6.15-rc5-mm1 Carlos Martín
2005-12-06 3:04 ` 2.6.15-rc5-mm1 Andrew Morton
2005-12-06 6:59 ` 2.6.15-rc5-mm1 Ingo Molnar
2005-12-05 19:06 ` 2.6.15-rc5-mm1: git-alsa-vs-git-pcmcia.patch introduces new compile errors Adrian Bunk
2005-12-05 20:05 ` Takashi Iwai
2005-12-05 21:40 ` 2.6.15-rc5-mm1: USB_IP problems Adrian Bunk
2005-12-07 0:02 ` Greg KH
2005-12-07 0:08 ` Adrian Bunk
2005-12-05 23:05 ` 2.6.15-rc5-mm1 J.A. Magallon
2005-12-05 23:06 ` 2.6.15-rc5-mm1 Randy.Dunlap
2005-12-10 23:36 ` 2.6.15-rc5-mm1 Greg KH
2005-12-10 23:46 ` 2.6.15-rc5-mm1 J.A. Magallon
2005-12-11 21:36 ` 2.6.15-rc5-mm1 J.A. Magallon
2005-12-12 22:58 ` 2.6.15-rc5-mm1 Andrew Morton
2005-12-13 3:44 ` [linux-usb-devel] 2.6.15-rc5-mm1 Alan Stern
2005-12-13 13:51 ` J.A. Magallon
2005-12-13 15:35 ` Alan Stern
2005-12-13 16:47 ` David Brownell
2005-12-06 13:33 ` 2.6.15-rc5-mm1 KAMEZAWA Hiroyuki
2005-12-07 0:46 ` 2.6.15-rc5-mm1 (x86_64-hpet-overflow.patch breaks resume from disk) Rafael J. Wysocki
2005-12-07 23:15 ` Rafael J. Wysocki
2005-12-08 8:43 ` [discuss] " Jan Beulich
2005-12-08 10:53 ` Rafael J. Wysocki
2005-12-08 22:35 ` Rafael J. Wysocki
2005-12-09 9:15 ` Jan Beulich
2005-12-09 9:16 ` Andi Kleen
2005-12-09 11:20 ` Rafael J. Wysocki
2005-12-09 12:41 ` Jan Beulich
2005-12-09 13:10 ` Rafael J. Wysocki
2005-12-09 17:34 ` Rafael J. Wysocki
2005-12-12 7:58 ` Jan Beulich
2005-12-12 8:05 ` [discuss] " Andi Kleen
2005-12-08 22:47 ` Andi Kleen
2005-12-08 23:00 ` Rafael J. Wysocki
2005-12-09 9:08 ` Jan Beulich
2005-12-09 9:16 ` Andi Kleen
2005-12-09 10:57 ` Jan Beulich [this message]
2005-12-08 19:09 ` 2.6.15-rc5-mm1 Badari Pulavarty
2005-12-08 21:14 ` 2.6.15-rc5-mm1 James Courtier-Dutton
2005-12-08 23:02 ` 2.6.15-rc5-mm1 Adrian Bunk
2005-12-09 7:15 ` [Alsa-devel] 2.6.15-rc5-mm1 Jaroslav Kysela
2005-12-09 7:15 ` Jaroslav Kysela
2005-12-08 23:02 ` 2.6.15-rc5-mm1 Adrian Bunk
2005-12-09 1:09 ` 2.6.15-rc5-mm1 Alexander E. Patrakov
2005-12-09 1:52 ` 2.6.15-rc5-mm1 Jeff Garzik
2005-12-12 16:12 ` 2.6.15-rc5-mm1 Alan Cox
2005-12-13 22:49 ` 2.6.15-rc5-mm1 J.A. Magallon
2005-12-13 23:24 ` 2.6.15-rc5-mm1 Andrew Morton
2005-12-14 0:17 ` 2.6.15-rc5-mm1 J.A. Magallon
2005-12-14 0:22 ` 2.6.15-rc5-mm1 Andrew Morton
2005-12-14 1:33 ` 2.6.15-rc5-mm1 Dmitry Torokhov
2005-12-14 0:31 ` 2.6.15-rc5-mm1 Ben Pfaff
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=4399712A.76F0.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.