All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Hu Tao <hutao@cn.fujitsu.com>,
	platform-driver-x86@vger.kernel.org, kvm@vger.kernel.org,
	Matthew Garrett <matthew.garrett@nebula.com>
Subject: Re: [PATCH v17 RESEND] pvpanic: pvpanic device driver
Date: Mon, 06 May 2013 15:18:39 +0200	[thread overview]
Message-ID: <5187ADAF.4020103@redhat.com> (raw)
In-Reply-To: <20130506113850.GA5603@amt.cnet>

Il 06/05/2013 13:38, Marcelo Tosatti ha scritto:
> On Mon, May 06, 2013 at 11:39:35AM +0800, Hu Tao wrote:
>> On Fri, May 03, 2013 at 06:59:18PM -0300, Marcelo Tosatti wrote:
>>> On Fri, May 03, 2013 at 10:47:10AM +0800, Hu Tao wrote:
>>>> pvpanic device is a qemu simulated device through which guest panic
>>>> event is sent to host.
>>>>
>>>> Signed-off-by: Hu Tao <hutao@cn.fujitsu.com>
>>>> ---
>>>>  drivers/platform/x86/Kconfig   |   7 +++
>>>>  drivers/platform/x86/Makefile  |   2 +
>>>>  drivers/platform/x86/pvpanic.c | 115 +++++++++++++++++++++++++++++++++++++++++
>>>>  3 files changed, 124 insertions(+)
>>>>  create mode 100644 drivers/platform/x86/pvpanic.c
>>>>
>>>> diff --git a/drivers/platform/x86/Kconfig b/drivers/platform/x86/Kconfig
>>>> index 3338437..527ed04 100644
>>>> --- a/drivers/platform/x86/Kconfig
>>>> +++ b/drivers/platform/x86/Kconfig
>>>> @@ -781,4 +781,11 @@ config APPLE_GMUX
>>>>  	  graphics as well as the backlight. Currently only backlight
>>>>  	  control is supported by the driver.
>>>>  
>>>> +config PVPANIC
>>>> +	tristate "pvpanic device support"
>>>> +	depends on ACPI
>>>> +	---help---
>>>> +	  This driver provides support for pvpanic device, which is a qemu
>>>> +	  simulated device through which guest panic event is sent to host.
>>>> +
>>>>  endif # X86_PLATFORM_DEVICES
>>>> diff --git a/drivers/platform/x86/Makefile b/drivers/platform/x86/Makefile
>>>> index ace2b38..ef0ec74 100644
>>>> --- a/drivers/platform/x86/Makefile
>>>> +++ b/drivers/platform/x86/Makefile
>>>> @@ -51,3 +51,5 @@ obj-$(CONFIG_INTEL_OAKTRAIL)	+= intel_oaktrail.o
>>>>  obj-$(CONFIG_SAMSUNG_Q10)	+= samsung-q10.o
>>>>  obj-$(CONFIG_APPLE_GMUX)	+= apple-gmux.o
>>>>  obj-$(CONFIG_CHROMEOS_LAPTOP)	+= chromeos_laptop.o
>>>> +
>>>> +obj-$(CONFIG_PVPANIC)           += pvpanic.o
>>>> diff --git a/drivers/platform/x86/pvpanic.c b/drivers/platform/x86/pvpanic.c
>>>> new file mode 100644
>>>> index 0000000..81c95ec
>>>> --- /dev/null
>>>> +++ b/drivers/platform/x86/pvpanic.c
>>>> @@ -0,0 +1,115 @@
>>>> +/*
>>>> + *  pvpanic.c - pvpanic Device Support
>>>> + *
>>>> + *  Copyright (C) 2013 Fujitsu.
>>>> + *
>>>> + *  This program is free software; you can redistribute it and/or modify
>>>> + *  it under the terms of the GNU General Public License as published by
>>>> + *  the Free Software Foundation; either version 2 of the License, or
>>>> + *  (at your option) any later version.
>>>> + *
>>>> + *  This program is distributed in the hope that it will be useful,
>>>> + *  but WITHOUT ANY WARRANTY; without even the implied warranty of
>>>> + *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>>>> + *  GNU General Public License for more details.
>>>> + *
>>>> + *  You should have received a copy of the GNU General Public License
>>>> + *  along with this program; if not, write to the Free Software
>>>> + *  Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
>>>> + */
>>>> +
>>>> +#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
>>>> +
>>>> +#include <linux/kernel.h>
>>>> +#include <linux/module.h>
>>>> +#include <linux/init.h>
>>>> +#include <linux/types.h>
>>>> +#include <acpi/acpi_bus.h>
>>>> +#include <acpi/acpi_drivers.h>
>>>> +
>>>> +MODULE_AUTHOR("Hu Tao <hutao@cn.fujitsu.com>");
>>>> +MODULE_DESCRIPTION("pvpanic device driver");
>>>> +MODULE_LICENSE("GPL");
>>>> +
>>>> +static int pvpanic_add(struct acpi_device *device);
>>>> +static int pvpanic_remove(struct acpi_device *device);
>>>> +
>>>> +static const struct acpi_device_id pvpanic_device_ids[] = {
>>>> +	{ "QEMU0001", 0},
>>>> +	{ "", 0},
>>>> +};
>>>> +MODULE_DEVICE_TABLE(acpi, pvpanic_device_ids);
>>>> +
>>>> +#define PVPANIC_PANICKED	(1 << 0)
>>>> +
>>>> +static acpi_handle handle;
>>>> +
>>>> +static struct acpi_driver pvpanic_driver = {
>>>> +	.name =		"pvpanic",
>>>> +	.class =	"QEMU",
>>>> +	.ids =		pvpanic_device_ids,
>>>> +	.ops =		{
>>>> +				.add =		pvpanic_add,
>>>> +				.remove =	pvpanic_remove,
>>>> +			},
>>>> +	.owner =	THIS_MODULE,
>>>> +};
>>>> +
>>>> +static void
>>>> +pvpanic_send_event(unsigned int event)
>>>> +{
>>>> +	union acpi_object arg;
>>>> +	struct acpi_object_list arg_list;
>>>> +
>>>> +	if (!handle)
>>>> +		return;
>>>> +
>>>> +	arg.type = ACPI_TYPE_INTEGER;
>>>> +	arg.integer.value = event;
>>>> +
>>>> +	arg_list.count = 1;
>>>> +	arg_list.pointer = &arg;
>>>> +
>>>> +	acpi_evaluate_object(handle, "WRPT", &arg_list, NULL);
>>>> +}
>>>
>>> Is it safe to call acpi_evaluate_object from a panic notifier? For
>>> example:
>>>
>>> - Has it been confirmed that no code invoked via acpi_evaluate_object can panic() ?
>>
>> Confirmed.
>>
>>> - acpi_ex_enter_interpreter grabs a mutex. Is that path ever used?
>>
>> Unfortunately yes. As I can tell, there are 2 places in the path to grab
>> a mutex: when searching the namespace for the method, and when executing
>> the method. I didn't find a non-blocking version of acpi_evaluate_object.
> 
> Then thats a bug because the pvpanic notifier is called with interrupts
> disabled.
> 
> Suppose its safer to use an OUT instruction?

Yeah, it probably is...  You can still use acpi_walk_resources to find
the port number instead of hard-coding 0x505...

Paolo

  reply	other threads:[~2013-05-06 13:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03  2:47 [PATCH v17 RESEND] pvpanic: pvpanic device driver Hu Tao
2013-05-03  9:17 ` Paolo Bonzini
2013-05-03 21:59 ` Marcelo Tosatti
2013-05-06  3:39   ` Hu Tao
2013-05-06 11:38     ` Marcelo Tosatti
2013-05-06 13:18       ` Paolo Bonzini [this message]
2013-05-07  3:39         ` [PATCH v18] " Hu Tao
2013-05-07  8:10           ` Paolo Bonzini
2013-05-07  9:27             ` Hu Tao

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=5187ADAF.4020103@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=hutao@cn.fujitsu.com \
    --cc=kvm@vger.kernel.org \
    --cc=matthew.garrett@nebula.com \
    --cc=mtosatti@redhat.com \
    --cc=platform-driver-x86@vger.kernel.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.