From: "Adachi, Kenichi" <aileenja-dTzOdQ2U+/YAvxtiuMwx3w@public.gmane.org>
To: willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org
Cc: haug-X6ztD3ggwzuBAmxm6OvjtTjhTm2NLCe8@public.gmane.org,
acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org
Subject: Re: Invalid PBLK length
Date: Thu, 19 Dec 2002 00:17:40 +0900 (JST) [thread overview]
Message-ID: <4e353e0091944930a0$NiftyInterway@nifty.ne.jp> (raw)
I didn't check code, but if that said address space type 127 does mean "Functi
onal Fixed Hardware (0x7F)", then your processor expects that OS processor dri
ver knows the specific address to control voltage scaling state transition. Us
ually it's done by accessing MSRs. This has been true for AMD PowerNow! and Tr
ansmeta LongRun, and Intel's new Geyserville I/F which will be unveiled on Ban
ias in the near future. These are mostly under NDA, therefore I can't be speci
fic, however there're several public documents which explain this stuff a bit
more.
So if my guess is correct, your BIOS is not bad. To enable processor performan
ce control on your machine, Linux needs inputs from CPU vendors.
>
> > I also see in dmesg that there's an unsupported address space
> > of 127 in acpi_processor_get_performance_control because
> > reg->space_id != ACPI_ADR_SPACE_SYSTEM_IO. But I don't know
> > enough C to understand where this comes from. Could somebody
> > please give me a hint?
>
> ACPI tells you which address space a given address is in:
>
> #define ACPI_ADR_SPACE_SYSTEM_MEMORY (ACPI_ADR_SPACE_TYPE) 0
> #define ACPI_ADR_SPACE_SYSTEM_IO (ACPI_ADR_SPACE_TYPE) 1
> #define ACPI_ADR_SPACE_PCI_CONFIG (ACPI_ADR_SPACE_TYPE) 2
> #define ACPI_ADR_SPACE_EC (ACPI_ADR_SPACE_TYPE) 3
> #define ACPI_ADR_SPACE_SMBUS (ACPI_ADR_SPACE_TYPE) 4
> #define ACPI_ADR_SPACE_CMOS (ACPI_ADR_SPACE_TYPE) 5
> #define ACPI_ADR_SPACE_PCI_BAR_TARGET (ACPI_ADR_SPACE_TYPE) 6
> #define ACPI_ADR_SPACE_DATA_TABLE (ACPI_ADR_SPACE_TYPE) 7
>
> processor.c is telling you it only handles ioport (inb/outb) address
> spaces. But 127 is not a valid address space value, so you're going
> to have to get an updated BIOS from your vendor. There's really no
> reasonable way to fix this.
>
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
next reply other threads:[~2002-12-18 15:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 15:17 Adachi, Kenichi [this message]
[not found] ` <4e353e0091944930a0$NiftyInterway-fFkzxiWP14B3+QwDJ9on6Q@public.gmane.org>
2002-12-18 15:29 ` Invalid PBLK length Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2003-01-21 22:15 Grover, Andrew
2003-01-21 8:38 Jens Haug
2003-01-20 23:58 Axel Müller
2002-12-19 8:13 Jens Haug
2002-12-18 21:28 Grover, Andrew
2002-12-18 16:08 Jens Haug
2002-12-18 15:36 Jens Haug
[not found] ` <200212181536.gBIFabD09402-sBhUd1W9t4xfrO0PeCDDO4ECbGbo6+O1OOFObY0sJ7w@public.gmane.org>
2002-12-18 16:00 ` Ducrot Bruno
2002-12-18 13:26 Jens Haug
[not found] ` <200212181326.gBIDQ5D08026-sBhUd1W9t4xfrO0PeCDDO4ECbGbo6+O1OOFObY0sJ7w@public.gmane.org>
2002-12-18 14:00 ` Matthew Wilcox
[not found] ` <20021218140019.H9994-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2002-12-18 15:32 ` Adachi, Kenichi
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='4e353e0091944930a0$NiftyInterway@nifty.ne.jp' \
--to=aileenja-dtzodq2u+/yavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org \
--cc=haug-X6ztD3ggwzuBAmxm6OvjtTjhTm2NLCe8@public.gmane.org \
--cc=willy-8fiUuRrzOP0dnm+yROfE0A@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox