From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: thunder@ngforever.de (Thunder from the hill)
Cc: rmk@arm.linux.org.uk (Russell King),
alan@lxorguk.ukuu.org.uk (Alan Cox),
hpa@zytor.com (H. Peter Anvin), pavel@ucw.cz (Pavel Machek),
acahalan@cs.uml.edu (Albert D. Cahalan),
linux-kernel@vger.kernel.org
Subject: Re: [OT] /proc/cpuinfo output from some arch
Date: Thu, 11 Jul 2002 03:22:44 +0100 (BST) [thread overview]
Message-ID: <E17STbQ-0008MP-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.44.0207101744040.5067-100000@hawkeye.luckynet.adm> from "Thunder from the hill" at Jul 10, 2002 05:45:57 PM
> Yes, asymmetric multiprocessing is a much more diffcult field, but
> it's not currently an issue to us. (Well, we had this issue long ago, but
> the SMP approach won, because even though it's uncool, it's still easier
> to handle. Maybe AMP will return one day...)
Per CPU clock ratios are supported in several places. There is also a whole
research field into SMP power management that goes with it
next prev parent reply other threads:[~2002-07-11 1:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-06 9:16 [OT] /proc/cpuinfo output from some arch Witek Kręcicki
2002-07-06 11:12 ` Richard Zidlicky
2002-07-06 12:50 ` Dr. David Alan Gilbert
2002-07-06 17:46 ` Andreas Schwab
2002-07-06 21:12 ` Russell King
2002-07-06 21:25 ` Thunder from the hill
2002-07-06 22:16 ` H. Peter Anvin
2002-07-06 23:20 ` Russell King
2002-07-06 23:27 ` H. Peter Anvin
2002-07-07 0:30 ` Albert D. Cahalan
2002-07-07 16:25 ` George France
2002-07-10 0:20 ` Pavel Machek
2002-07-10 22:14 ` H. Peter Anvin
2002-07-10 23:15 ` Russell King
2002-07-10 23:47 ` Alan Cox
2002-07-10 23:37 ` Russell King
2002-07-10 23:45 ` Thunder from the hill
2002-07-11 2:22 ` Alan Cox [this message]
2002-07-11 0:52 ` Greg KH
2002-07-06 12:15 Holzrichter, Bruce
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=E17STbQ-0008MP-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=acahalan@cs.uml.edu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rmk@arm.linux.org.uk \
--cc=thunder@ngforever.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 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.