From: "Alejandro Bonilla" <abonilla@linuxwireless.org>
To: linux-kernel@vger.kernel.org
Subject: Dual Core on Linux questions
Date: Sat, 18 Mar 2006 02:35:33 -0600 [thread overview]
Message-ID: <20060318082434.M33432@linuxwireless.org> (raw)
Hi,
I have a few questions about the PM Dual Core and how could it really work
with Linux. Sorry if there are new patches on LKML about any of these things:
Could each processor or die, have it's own cpufreq scaling governor?
Is there a way to allow one die to be idle and let the other one normal?
So in other words, could we manage these processors speedstep, utilization and
workload individually?
Thanks!
.Alejandro
next reply other threads:[~2006-03-18 8:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-18 8:35 Alejandro Bonilla [this message]
2006-03-18 8:58 ` Dual Core on Linux questions Jeff Garzik
2006-03-18 9:03 ` Alejandro Bonilla
2006-03-18 10:49 ` Mattia Dongili
2006-03-18 9:21 ` Arjan van de Ven
2006-03-20 19:23 ` Wes Felter
-- strict thread matches above, loose matches on Subject: below --
2006-03-23 3:36 Pallipadi, Venkatesh
2006-03-23 3:44 ` Jeff Garzik
2006-03-29 19:51 ` Bill Davidsen
2006-03-30 20:31 ` Jeff Garzik
2006-04-04 19:30 ` Bill Davidsen
2006-03-23 17:55 ` Mattia Dongili
2006-03-23 3:51 Pallipadi, Venkatesh
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=20060318082434.M33432@linuxwireless.org \
--to=abonilla@linuxwireless.org \
--cc=linux-kernel@vger.kernel.org \
/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