From: Igor Mammedov <imammedo@redhat.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>
Cc: linux-kernel@vger.kernel.org, Darren Hart <dvhart@infradead.org>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] pvpanic: handle missing _STA correctly
Date: Mon, 1 Jun 2015 09:33:22 +0200 [thread overview]
Message-ID: <20150601093322.4ec8de60@nial.brq.redhat.com> (raw)
In-Reply-To: <1432930732-16568-1-git-send-email-rkrcmar@redhat.com>
On Fri, 29 May 2015 22:18:52 +0200
Radim Krčmář <rkrcmar@redhat.com> wrote:
> pvpanic was not properly detected when _STA was missing.
>
> ACPI 6.0 April 2015, 6.3.7 _STA (Status)
> If a device object (including the processor object) does not have an
> _STA object, then OSPM assumes that all of the above bits are set
> (i.e., the device is present, enabled, shown in the UI, and
> functioning).
>
> Not adhering to the specification made pvpanic dormant under QEMU 2.3.
>
> Suggested-by: Igor Mammedov <imammedo@redhat.com>
> Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
> ---
> drivers/platform/x86/pvpanic.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/platform/x86/pvpanic.c b/drivers/platform/x86/pvpanic.c
> index 073a90a63dbc..7b6860333267 100644
> --- a/drivers/platform/x86/pvpanic.c
> +++ b/drivers/platform/x86/pvpanic.c
> @@ -95,8 +95,7 @@ static int pvpanic_add(struct acpi_device *device)
> acpi_status status;
> u64 ret;
>
> - status = acpi_evaluate_integer(device->handle, "_STA", NULL,
> - &ret);
> + status = acpi_bus_get_status_handle(device->handle, &ret);
>
> if (ACPI_FAILURE(status) || (ret & 0x0B) != 0x0B)
> return -ENODEV;
next prev parent reply other threads:[~2015-06-01 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 20:18 Radim Krčmář
2015-06-01 7:33 ` Igor Mammedov [this message]
2015-06-01 17:38 ` [PATCH] pvpanic: handle missing _STA correctly' Darren Hart
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=20150601093322.4ec8de60@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rkrcmar@redhat.com \
/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
all inboxes | Powered by JetHome®