From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PULL 1/2] hw/i386: allow SHPC for Q35 machine
Date: Tue, 8 Aug 2017 00:41:07 +0300 [thread overview]
Message-ID: <20170808004052-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1502142009-9370-2-git-send-email-mst@redhat.com>
On Tue, Aug 08, 2017 at 12:40:08AM +0300, Michael S. Tsirkin wrote:
> From: Aleksandr Bezzubikov <zuban32s@gmail.com>
>
> Unmask previously masked SHPC feature in _OSC method.
>
> Signed-off-by: Aleksandr Bezzubikov <zuban32s@gmail.com>
> Reviewed-by: Marcel Apfelbaum <marcel@redhat.com>
> Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Cc: qemu-stable@nongnu.org
> ---
> hw/i386/acpi-build.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
> index b9c245c..98dd424 100644
> --- a/hw/i386/acpi-build.c
> +++ b/hw/i386/acpi-build.c
> @@ -1862,9 +1862,9 @@ static Aml *build_q35_osc_method(void)
>
> /*
> * Always allow native PME, AER (no dependencies)
> - * Never allow SHPC (no SHPC controller in this system)
> + * Allow SHPC (PCI bridges can have SHPC controller)
> */
> - aml_append(if_ctx, aml_and(a_ctrl, aml_int(0x1D), a_ctrl));
> + aml_append(if_ctx, aml_and(a_ctrl, aml_int(0x1F), a_ctrl));
>
> if_ctx2 = aml_if(aml_lnot(aml_equal(aml_arg(1), aml_int(1))));
> /* Unknown revision */
> --
> MST
next prev parent reply other threads:[~2017-08-07 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 21:40 [Qemu-devel] [PULL 0/2] virtio: fix for rc2 Michael S. Tsirkin
2017-08-07 21:40 ` [Qemu-devel] [PULL 1/2] hw/i386: allow SHPC for Q35 machine Michael S. Tsirkin
2017-08-07 21:41 ` Michael S. Tsirkin [this message]
2017-08-07 21:40 ` [Qemu-devel] [PULL 2/2] cpu: add APIs to allocate/free CPU environment Michael S. Tsirkin
2017-08-08 10:05 ` [Qemu-devel] [PULL 0/2] virtio: fix for rc2 Peter Maydell
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=20170808004052-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 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.