qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel@nongnu.org, Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH for-2.0] dsdt: tweak ACPI ID for hotplug resource device
Date: Mon, 7 Apr 2014 11:59:41 +0300	[thread overview]
Message-ID: <20140407085941.GA14183@redhat.com> (raw)
In-Reply-To: <20140407105702.2562dfb1@nial.usersys.redhat.com>

On Mon, Apr 07, 2014 at 10:57:02AM +0200, Igor Mammedov wrote:
> On Sun, 6 Apr 2014 12:47:37 +0300
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
> 
> > ACPI0004 seems too new:
> > Windows XP complains about an unrecognized device.
> > This is a regression since 1.7.
> > Use PNP0A06 instead - Generic Container Device.
> > 
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > ---
> > 
> > Note: Igor has RFC patches to use PNP0C02 under PCI0,
> > but that's not ready for 2.0.
> > Igor, could you comment on whether PNP0C02 is preferable for
> > some OS-es?
> > 
> > For PNP0A06 ACPI spec says:
> >     PNP0A06
> >     Generic Container Device. This device behaves exactly the same as the
> >     PNP0A05 device.
> >     This was originally known as Extended I/O Bus. This ID should only be
> >     used for containers
> >     that do not produce resources for consumption by child devices. Any
> >     system resources
> >     claimed by a PNP0A06 device’s _CRS object must be consumed by the
> >     container itself.
> > 
> > PNP0C02 is not in ACPI spec. It does appear in MicroSoft legacy PNP ID
> > document:
> >     PNP0C02         General ID for reserving resources required by Plug and
> >     Play motherboard registers. (Not specific to a particular device.)
> > 
> > Thoughts?
> > 
> >  hw/i386/acpi-dsdt-cpu-hotplug.dsl | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/hw/i386/acpi-dsdt-cpu-hotplug.dsl b/hw/i386/acpi-dsdt-cpu-hotplug.dsl
> > index dee4843..34aab5a 100644
> > --- a/hw/i386/acpi-dsdt-cpu-hotplug.dsl
> > +++ b/hw/i386/acpi-dsdt-cpu-hotplug.dsl
> > @@ -93,7 +93,7 @@ Scope(\_SB) {
> >      }
> >  
> >      Device(CPU_HOTPLUG_RESOURCE_DEVICE) {
> > -        Name(_HID, "ACPI0004")
> > +        Name(_HID, EisaId("PNP0A06"))
> >  
> >          Name(_CRS, ResourceTemplate() {
> >              IO(Decode16, CPU_STATUS_BASE, CPU_STATUS_BASE, 0, CPU_STATUS_LEN)
> 
> Reviewed-By: Igor Mammedov <imammedo@redhat.com>

Thanks!
Peter, could you pick this up for 2.0 please?

-- 
MST

  reply	other threads:[~2014-04-07  8:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-06  9:47 [Qemu-devel] [PATCH for-2.0] dsdt: tweak ACPI ID for hotplug resource device Michael S. Tsirkin
2014-04-07  7:46 ` Igor Mammedov
2014-04-07  8:36   ` Michael S. Tsirkin
2014-04-07  8:57 ` Igor Mammedov
2014-04-07  8:59   ` Michael S. Tsirkin [this message]
2014-04-07 20:40 ` Michael S. Tsirkin

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=20140407085941.GA14183@redhat.com \
    --to=mst@redhat.com \
    --cc=aliguori@amazon.com \
    --cc=imammedo@redhat.com \
    --cc=peter.maydell@linaro.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;
as well as URLs for NNTP newsgroup(s).