public inbox for kvm@vger.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,
	qemu-devel@nongnu.org, chrisw@sous-sol.org
Subject: Re: [PATCH 0/15] acpi processor hotplug
Date: Wed, 27 Feb 2008 12:55:23 +0200	[thread overview]
Message-ID: <47C5419B.3090901@qumranet.com> (raw)
In-Reply-To: <1204055805-32349-1-git-send-email-gcosta@redhat.com>

Glauber Costa wrote:
> Hi,
>
> I'm resending the series with avi's few comments merged, and a couple
> of others on my own:
>
> * _STA returns 0xF instead of 0x1. According to the specification, it means
>   that the device, besides present, is also functional, enabled, and a couple
>   of other cool things.
> * gpe_base and proc_base as #defines, not unsigned long
> * _EJ method out. It's causing a lot of troubles, and I'm not even sure it
>   makes sense for processors. We can live without it by now, and if it is needed,
>   it can be added later.
>
>   

Applied all, thanks.


-- 
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-27 10:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 19:56 [PATCH 0/15] acpi processor hotplug 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 19:56         ` [PATCH 5/15] provide gpe _L0x methods Glauber Costa
2008-02-26 19:56           ` [PATCH 6/15] provide operation region for pio to the gpes Glauber Costa
2008-02-26 19:56             ` [PATCH 7/15] implement method _L00 for GPE0 Glauber Costa
2008-02-26 19:56               ` [PATCH 8/15] isolate cpu initialization function in hw/pc.c Glauber Costa
2008-02-26 19:56                 ` [PATCH 9/15] initialize hot add system Glauber Costa
2008-02-26 19:56                   ` [PATCH 10/15] handle gpe data for pio Glauber Costa
2008-02-26 19:56                     ` [PATCH 11/15] manipulate the gpe bits and send sci up the os Glauber Costa
2008-02-26 19:56                       ` [PATCH 12/15] isolate cpu thread creation in qemu-kvm.c Glauber Costa
2008-02-26 19:56                         ` [PATCH 13/15] provide _MAT to acpi processor Glauber Costa
2008-02-26 19:56                           ` [PATCH 14/15] start a new cpu thread Glauber Costa
2008-02-26 19:56                             ` [PATCH 15/15] remove acpi_build_processor_ssdt Glauber Costa
2008-02-26 23:05         ` [PATCH 4/15] mark processors as presents Alexander Graf
2008-02-26 23:07           ` Alexander Graf
2008-02-27 10:55 ` Avi Kivity [this message]

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=47C5419B.3090901@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 \
    --cc=qemu-devel@nongnu.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