From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: pbonzini@redhat.com, mst@redhat.com, qemu-devel@nongnu.org,
rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH] pc: acpi: keep pvpanic backward compatible
Date: Fri, 29 May 2015 13:24:40 +0200 [thread overview]
Message-ID: <20150529112436.GA11629@potion.brq.redhat.com> (raw)
In-Reply-To: <20150529105155.22255ce9@nial.brq.redhat.com>
2015-05-29 10:51+0200, Igor Mammedov:
> On Wed, 27 May 2015 18:29:17 +0200
> Radim Krčmář <rkrcmar@redhat.com> wrote:
> > In the old times, we always had pvpanic in ACPI and a _STA function told
> > the guest not to use it. Now, we only include pvpanic in ACPI if it is
> > enabled, so the _STA function is useless from qemu's point of view, but
> > guests still want to query availability. Make them happy.
> maybe also fix guest's driver not to do since absence of _STA
> implies that device is present according to ACPI6.0 6.3.7 _STA
Will do.
> or only fix driver and drop this patch so that QEMU wouldn't carry
> useless junk.
I think we still want to run old guests on new versions of QEMU.
We could have kept the incremented _HID otherwise, it would be better.
> > (Why Linux does '& 0xb' on this result is completely beyond me.)
> check _STA related comment in SMC
(Time to actually open the spec ...)
> > + method = aml_method("_STA", 0);
> > + aml_append(method, aml_return(aml_int(0xf)));
> > + aml_append(dev, method);
> doesn't have to be method,
>
> make it like this:
> /* device present, functioning, decoding, not shown in UI */
> aml_append(dev, aml_name_decl("_STA", aml_int(0xB)));
Nice, I didn't expect that much from the evaluator.
Thank you for all the information.
(v2 coming after I read few hundred pages.)
prev parent reply other threads:[~2015-05-29 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 16:29 [Qemu-devel] [PATCH] pc: acpi: keep pvpanic backward compatible Radim Krčmář
2015-05-29 8:51 ` Igor Mammedov
2015-05-29 11:24 ` Radim Krčmář [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=20150529112436.GA11629@potion.brq.redhat.com \
--to=rkrcmar@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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.