[Qemu-devel] Re: [kvm-devel] [PATCH 4/15] mark processors as presents

2008-02-26 Thread Alexander Graf 


On Feb 27, 2008, at 12:05 AM, Alexander Graf wrote:



On Feb 26, 2008, at 8:56 PM, Glauber Costa wrote:


mark processors as present through the _STA method

Signed-off-by: Glauber Costa [EMAIL PROTECTED]
---
bios/acpi-dsdt.dsl |   18 ++
1 files changed, 18 insertions(+), 0 deletions(-)

diff --git a/bios/acpi-dsdt.dsl b/bios/acpi-dsdt.dsl
index e900795..244e906 100755
--- a/bios/acpi-dsdt.dsl
+++ b/bios/acpi-dsdt.dsl
@@ -25,6 +25,24 @@ DefinitionBlock (
   0x1 // OEM Revision
   )
{
+   Scope (\_PR)
+   {
+Processor (CPU0, 0x00, 0xb010, 0x06) {Method (_STA)
{ Return(0xF)}}
+Processor (CPU1, 0x01, 0xb010, 0x06) {Method (_STA)
{ Return(0xF)}}
+Processor (CPU2, 0x02, 0xb010, 0x06) {Method (_STA)
{ Return(0xF)}}
+Processor (CPU3, 0x03, 0xb010, 0x06) {Method (_STA)
{ Return(0xF)}}
+Processor (CPU4, 0x04, 0xb010, 0x06) {Method (_STA)
{ Return(0xF)}}
+Processor (CPU5, 0x05, 0xb010, 0x06) {Method (_STA)
{ Return(0xF)}}
+Processor (CPU6, 0x06, 0xb010, 0x06) {Method (_STA)
{ Return(0xF)}}
+Processor (CPU7, 0x07, 0xb010, 0x06) {Method (_STA)
{ Return(0xF)}}
+Processor (CPU8, 0x08, 0xb010, 0x06) {Method (_STA)
{ Return(0xF)}}
+Processor (CPU9, 0x09, 0xb010, 0x06) {Method (_STA)
{ Return(0xF)}}
+Processor (CPUA, 0x0a, 0xb010, 0x06) {Method (_STA)
{ Return(0xF)}}
+Processor (CPUB, 0x0b, 0xb010, 0x06) {Method (_STA)
{ Return(0xF)}}
+Processor (CPUC, 0x0c, 0xb010, 0x06) {Method (_STA)
{ Return(0xF)}}
+Processor (CPUD, 0x0d, 0xb010, 0x06) {Method (_STA)
{ Return(0xF)}}
+Processor (CPUE, 0x0e, 0xb010, 0x06) {Method (_STA)
{ Return(0xF)}}


So if I understand this correctly, you set all possible CPUs on active
and available. What exactly happens if one of these is not usable?
I know that Darwin broke on the _PR description quite badly, as it
just allocates possible execution engines using the ACPI Processor
specification and I do not know what happens if the engine is not
available.

I have to admit that I have not tested it as I do not have the time to
do so though, so maybe it works.


I just read patch 13 ... nevermind

[Qemu-devel] Re: [kvm-devel] [PATCH 4/15] mark processors as presents

2008-02-26 Thread Alexander Graf 


On Feb 26, 2008, at 8:56 PM, Glauber Costa wrote:


mark processors as present through the _STA method

Signed-off-by: Glauber Costa [EMAIL PROTECTED]
---
bios/acpi-dsdt.dsl |   18 ++
1 files changed, 18 insertions(+), 0 deletions(-)

diff --git a/bios/acpi-dsdt.dsl b/bios/acpi-dsdt.dsl
index e900795..244e906 100755
--- a/bios/acpi-dsdt.dsl
+++ b/bios/acpi-dsdt.dsl
@@ -25,6 +25,24 @@ DefinitionBlock (
0x1 // OEM Revision
)
{
+   Scope (\_PR)
+   {
+Processor (CPU0, 0x00, 0xb010, 0x06) {Method (_STA)  
{ Return(0xF)}}
+Processor (CPU1, 0x01, 0xb010, 0x06) {Method (_STA)  
{ Return(0xF)}}
+Processor (CPU2, 0x02, 0xb010, 0x06) {Method (_STA)  
{ Return(0xF)}}
+Processor (CPU3, 0x03, 0xb010, 0x06) {Method (_STA)  
{ Return(0xF)}}
+Processor (CPU4, 0x04, 0xb010, 0x06) {Method (_STA)  
{ Return(0xF)}}
+Processor (CPU5, 0x05, 0xb010, 0x06) {Method (_STA)  
{ Return(0xF)}}
+Processor (CPU6, 0x06, 0xb010, 0x06) {Method (_STA)  
{ Return(0xF)}}
+Processor (CPU7, 0x07, 0xb010, 0x06) {Method (_STA)  
{ Return(0xF)}}
+Processor (CPU8, 0x08, 0xb010, 0x06) {Method (_STA)  
{ Return(0xF)}}
+Processor (CPU9, 0x09, 0xb010, 0x06) {Method (_STA)  
{ Return(0xF)}}
+Processor (CPUA, 0x0a, 0xb010, 0x06) {Method (_STA)  
{ Return(0xF)}}
+Processor (CPUB, 0x0b, 0xb010, 0x06) {Method (_STA)  
{ Return(0xF)}}
+Processor (CPUC, 0x0c, 0xb010, 0x06) {Method (_STA)  
{ Return(0xF)}}
+Processor (CPUD, 0x0d, 0xb010, 0x06) {Method (_STA)  
{ Return(0xF)}}
+Processor (CPUE, 0x0e, 0xb010, 0x06) {Method (_STA)  
{ Return(0xF)}}


So if I understand this correctly, you set all possible CPUs on active  
and available. What exactly happens if one of these is not usable?
I know that Darwin broke on the _PR description quite badly, as it  
just allocates possible execution engines using the ACPI Processor  
specification and I do not know what happens if the engine is not  
available.


I have to admit that I have not tested it as I do not have the time to  
do so though, so maybe it works.




+}

Scope (\)
{
--
1.4.2