From: Matthew Wilcox <willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: "Adachi, Kenichi" <aileenja-dTzOdQ2U+/YAvxtiuMwx3w@public.gmane.org>
Cc: willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org,
haug-X6ztD3ggwzuBAmxm6OvjtTjhTm2NLCe8@public.gmane.org,
acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org
Subject: Re: Invalid PBLK length
Date: Wed, 18 Dec 2002 15:29:06 +0000 [thread overview]
Message-ID: <20021218152906.J9994@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <4e353e0091944930a0$NiftyInterway-fFkzxiWP14B3+QwDJ9on6Q@public.gmane.org>; from aileenja-dTzOdQ2U+/YAvxtiuMwx3w@public.gmane.org on Thu, Dec 19, 2002 at 12:17:40AM +0900
On Thu, Dec 19, 2002 at 12:17:40AM +0900, Adachi, Kenichi wrote:
> 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.
you're right. Andy, could we add something like this?
diff -u -p -r1.6 actypes.h
--- drivers/acpi/include/actypes.h 10 Dec 2002 22:02:09 -0000 1.6
+++ drivers/acpi/include/actypes.h 18 Dec 2002 15:28:47 -0000
@@ -579,6 +579,7 @@ typedef u8
#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
+#define ACPI_ADR_SPACE_FIXED_HARDWARE (ACPI_ADR_SPACE_TYPE) 127
/*
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
-------------------------------------------------------
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 prev parent reply other threads:[~2002-12-18 15:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 15:17 Invalid PBLK length Adachi, Kenichi
[not found] ` <4e353e0091944930a0$NiftyInterway-fFkzxiWP14B3+QwDJ9on6Q@public.gmane.org>
2002-12-18 15:29 ` Matthew Wilcox [this message]
-- 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=20021218152906.J9994@parcelfarce.linux.theplanet.co.uk \
--to=willy-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
--cc=acpi-devel-pyega4qmqnRoyOMFzWx49A@public.gmane.org \
--cc=aileenja-dTzOdQ2U+/YAvxtiuMwx3w@public.gmane.org \
--cc=haug-X6ztD3ggwzuBAmxm6OvjtTjhTm2NLCe8@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