All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Glauber Costa <gcosta@redhat.com>
Cc: kvm-devel@lists.sourceforge.net, marcelo@kvack.org, chrisw@sous-sol.org
Subject: Re: [PATCH 4/15] mark processors as presents
Date: Sun, 24 Feb 2008 11:33:57 +0200	[thread overview]
Message-ID: <47C13A05.5090607@qumranet.com> (raw)
In-Reply-To: <1203716079-4872-5-git-send-email-gcosta@redhat.com>

Glauber Costa wrote:
> mark processors as present through the _STA method
>
> Signed-off-by: Glauber Costa <gcosta@redhat.com>
> ---
>  bios/acpi-dsdt.dsl |   19 +++++++++++++++++++
>  1 files changed, 19 insertions(+), 0 deletions(-)
>
> diff --git a/bios/acpi-dsdt.dsl b/bios/acpi-dsdt.dsl
> index e900795..cd42e23 100755
> --- a/bios/acpi-dsdt.dsl
> +++ b/bios/acpi-dsdt.dsl
> @@ -25,9 +25,28 @@ DefinitionBlock (
>      0x1                 // OEM Revision
>      )
>  {
> +   Scope (\_PR)
> +   {
> +        Processor (CPU0, 0x00, 0x0000b010, 0x06) {Method (_STA) { Return(0x1)}}
> +        Processor (CPU1, 0x01, 0x0000b010, 0x06) {Method (_STA) { Return(0x1)}}
> +        Processor (CPU2, 0x02, 0x0000b010, 0x06) {Method (_STA) { Return(0x1)}}
> +        Processor (CPU3, 0x03, 0x0000b010, 0x06) {Method (_STA) { Return(0x1)}}
> +        Processor (CPU4, 0x04, 0x0000b010, 0x06) {Method (_STA) { Return(0x1)}}
> +        Processor (CPU5, 0x05, 0x0000b010, 0x06) {Method (_STA) { Return(0x1)}}
> +        Processor (CPU6, 0x06, 0x0000b010, 0x06) {Method (_STA) { Return(0x1)}}
> +        Processor (CPU7, 0x07, 0x0000b010, 0x06) {Method (_STA) { Return(0x1)}}
> +        Processor (CPU8, 0x08, 0x0000b010, 0x06) {Method (_STA) { Return(0x1)}}
> +        Processor (CPU9, 0x09, 0x0000b010, 0x06) {Method (_STA) { Return(0x1)}}
> +        Processor (CPUA, 0x0a, 0x0000b010, 0x06) {Method (_STA) { Return(0x1)}}
> +        Processor (CPUB, 0x0b, 0x0000b010, 0x06) {Method (_STA) { Return(0x1)}}
> +        Processor (CPUC, 0x0c, 0x0000b010, 0x06) {Method (_STA) { Return(0x1)}}
> +        Processor (CPUD, 0x0d, 0x0000b010, 0x06) {Method (_STA) { Return(0x1)}}
> +        Processor (CPUE, 0x0e, 0x0000b010, 0x06) {Method (_STA) { Return(0x1)}}
> +    }
>   

There is now code in rombios32.c to do this.  It needs to be removed.  
See acpi_build_processor_ssdt().

>  
>      Scope (\)
>      {
> +
>          /* CMOS memory access */
>          OperationRegion (CMS, SystemIO, 0x70, 0x02)
>          Field (CMS, ByteAcc, NoLock, Preserve)
>   

-

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2008-02-24  9:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22 21:34 [PATCH 0/15] Review: acpi processor hotplug Glauber Costa
2008-02-22 21:34 ` [PATCH 1/15] Make a GPE register block be acessible Glauber Costa
2008-02-22 21:34   ` [PATCH 2/15] mark extra cpus as present Glauber Costa
2008-02-22 21:34     ` [PATCH 3/15] introduce cpu_set to qemu monitor Glauber Costa
2008-02-22 21:34       ` [PATCH 4/15] mark processors as presents Glauber Costa
2008-02-22 21:34         ` [PATCH 5/15] provide gpe _L0x methods Glauber Costa
2008-02-22 21:34           ` [PATCH 6/15] provide operation region for pio to the gpes Glauber Costa
2008-02-22 21:34             ` [PATCH 7/15] implement method _L00 for GPE0 Glauber Costa
2008-02-22 21:34               ` [PATCH 8/15] isolate cpu initialization function in hw/pc.c Glauber Costa
2008-02-22 21:34                 ` [PATCH 9/15] initialize hot add system Glauber Costa
2008-02-22 21:34                   ` [PATCH 10/15] handle gpe data for pio Glauber Costa
2008-02-22 21:34                     ` [PATCH 11/15] manipulate the gpe bits and send sci up the os Glauber Costa
2008-02-22 21:34                       ` [PATCH 12/15] isolate cpu thread creation in qemu-kvm.c Glauber Costa
2008-02-22 21:34                         ` [PATCH 13/15] provide _MAT to acpi processor Glauber Costa
2008-02-22 21:34                           ` [PATCH 14/15] start a new cpu thread Glauber Costa
2008-02-22 21:34                             ` [PATCH 15/15] provide _EJ0 method for processor removal Glauber Costa
2008-02-24  9:33         ` Avi Kivity [this message]
2008-02-25 14:38           ` [PATCH 4/15] mark processors as presents Glauber Costa
2008-02-25 14:49             ` Avi Kivity
2008-02-25 14:43               ` Glauber Costa
2008-02-24  9:34       ` [PATCH 3/15] introduce cpu_set to qemu monitor Avi Kivity
2008-02-24  9:44 ` [PATCH 0/15] Review: acpi processor hotplug Avi Kivity
  -- strict thread matches above, loose matches on Subject: below --
2008-02-26 19:56 [PATCH 0/15] " Glauber Costa
2008-02-26 19:56 ` [PATCH 1/15] Make a GPE register block be acessible Glauber Costa
2008-02-26 19:56   ` [PATCH 2/15] mark extra cpus as present Glauber Costa
2008-02-26 19:56     ` [PATCH 3/15] introduce cpu_set to qemu monitor Glauber Costa
2008-02-26 19:56       ` [PATCH 4/15] mark processors as presents Glauber Costa
2008-02-26 23:05         ` Alexander Graf
2008-02-26 23:07           ` Alexander Graf

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=47C13A05.5090607@qumranet.com \
    --to=avi@qumranet.com \
    --cc=chrisw@sous-sol.org \
    --cc=gcosta@redhat.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=marcelo@kvack.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.