From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: Dino Klein <dinoklein-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Via 694X based SMB boards (Apollo Pro133A)
Date: Thu, 15 Jan 2004 15:39:32 -0800 (PST) [thread overview]
Message-ID: <20040115153450.J73140@root.org> (raw)
In-Reply-To: <Law11-OE71YaEv1Kq2E0000cace-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
On Thu, 15 Jan 2004, Dino Klein wrote:
> > If you're looking to do throttling, some SMP boards support it. The most
> > common way is with a shared P_BLK. Either both Processor objects in the
> > ASL will have the same P_BLK or one will have it and the other will have a
> > NULL entry. Either way, setting throttling through the P_BLK _ONCE_ (not
> > once per processor) sets the throttling level.
>
> Actually, I did play with the throttling, but not through the ACPI
> driver. I wrote directly to the register, and the system was reduced to
> ~5% (according to the datasheets) of it's former glory. I did that with
> both CPUs on the board, which makes me wonder - is there some way to
> figure out what is the clock speed of a particular CPU? maybe this way I
> can figure out whether my actions operate on both CPUs or only one one.
What are your Processor objects? Here's a dual processor Xeon board with
a duplicated P_BLK. The extra two objects are for the hyperthreading
logical CPUs.
IntelSE7501BR2.asl: Processor (CPU1, 0x01, 0x00000410, 0x06) {}
IntelSE7501BR2.asl: Processor (CPU2, 0x02, 0x00000410, 0x06) {}
IntelSE7501BR2.asl: Processor (CPU3, 0x06, 0x00000410, 0x06) {}
IntelSE7501BR2.asl: Processor (CPU4, 0x07, 0x00000410, 0x06) {}
No idea how to check clock speed of a particular CPU. Try running a
benchmark pinned to one CPU and then the other. I don't know the Linux
command for setting CPU affinity. You could also run two tasks in
parallel that are a CPU benchmark. Since throttling is linear, if you set
50% throttling and you get both tasks taking twice the time with
throttling as without, both CPUs are throttled. If both tasks finish in
25% of the time, one processor is not throttled.
-Nate
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-01-15 23:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 21:40 Via 694X based SMB boards (Apollo Pro133A) Dino Klein
[not found] ` <LAW11-OE34hRDT6Z3Ls000131c1-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
2004-01-15 22:13 ` Nate Lawson
2004-01-15 22:36 ` Dino Klein
[not found] ` <Law11-OE71YaEv1Kq2E0000cace-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
2004-01-15 23:39 ` Nate Lawson [this message]
2004-01-17 0:19 ` Dino Klein
[not found] ` <LAW11-OE12KYXlz705N000297c0-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.org>
2004-01-16 0:29 ` Nate Lawson
2004-01-17 0:33 ` Dino Klein
2004-01-15 22:50 ` Ian Pilcher
2004-01-15 22:58 ` Dino Klein
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=20040115153450.J73140@root.org \
--to=nate-y6vguytwhu0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=dinoklein-PkbjNfxxIARBDgjK7y7TUQ@public.gmane.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 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.