From: Igor Mammedov <imammedo@redhat.com>
To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
Cc: "peter.maydell@linaro.org" <peter.maydell@linaro.org>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
"shannon.zhaosl@gmail.com" <shannon.zhaosl@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Linuxarm <linuxarm@huawei.com>,
Auger Eric <eric.auger@redhat.com>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
"xuwei \(O\)" <xuwei5@huawei.com>,
"sebastien.boeuf@intel.com" <sebastien.boeuf@intel.com>
Subject: Re: [Qemu-arm] [Qemu-devel] [PATCH v3 03/10] hw/arm/virt: Add virtual ACPI device
Date: Tue, 2 Apr 2019 08:31:09 +0200 [thread overview]
Message-ID: <20190402083109.4e8c354b@redhat.com> (raw)
In-Reply-To: <5FC3163CFD30C246ABAA99954A238FA839345569@lhreml524-mbb.china.huawei.com>
On Mon, 1 Apr 2019 14:21:40 +0000
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com> wrote:
> Hi Igor,
>
> > -----Original Message-----
> > From: Igor Mammedov [mailto:imammedo@redhat.com]
> > Sent: 01 April 2019 14:09
> > To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
> > Cc: Auger Eric <eric.auger@redhat.com>; qemu-devel@nongnu.org;
> > qemu-arm@nongnu.org; peter.maydell@linaro.org;
> > shannon.zhaosl@gmail.com; sameo@linux.intel.com;
> > sebastien.boeuf@intel.com; Linuxarm <linuxarm@huawei.com>; xuwei (O)
> > <xuwei5@huawei.com>
> > Subject: Re: [Qemu-devel] [PATCH v3 03/10] hw/arm/virt: Add virtual ACPI
> > device
> >
> > On Fri, 29 Mar 2019 11:22:02 +0000
> > Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com> wrote:
> >
> > > > -----Original Message-----
> > > > From: Auger Eric [mailto:eric.auger@redhat.com]
> > > > Sent: 28 March 2019 14:15
> > > > To: Shameerali Kolothum Thodi
> > <shameerali.kolothum.thodi@huawei.com>;
> > > > qemu-devel@nongnu.org; qemu-arm@nongnu.org;
> > imammedo@redhat.com;
> > > > peter.maydell@linaro.org; shannon.zhaosl@gmail.com;
> > > > sameo@linux.intel.com; sebastien.boeuf@intel.com
> > > > Cc: Linuxarm <linuxarm@huawei.com>; xuwei (O) <xuwei5@huawei.com>
> > > > Subject: Re: [PATCH v3 03/10] hw/arm/virt: Add virtual ACPI device
> > > >
> > > > Hi Shameer,
> > > >
> > > > On 3/21/19 11:47 AM, Shameer Kolothum wrote:
> > > > > From: Samuel Ortiz <sameo@linux.intel.com>
> > > > >
> > > > > This adds the skeleton to support an acpi device interface for
> > > > > HW-reduced acpi platforms via ACPI GED - Generic Event Device (ACPI
> > > > > v6.1 5.6.9).
> > > > >
> > > > > This will be used by Arm/Virt to add hotplug support.
> > > > >
> > > > > Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
> > > > > Signed-off-by: Shameer Kolothum
> > <shameerali.kolothum.thodi@huawei.com>
> > > > > ---
> > > > > hw/acpi/Kconfig | 4 ++
> > > > > hw/acpi/Makefile.objs | 1 +
> > > > > hw/acpi/generic_event_device.c | 72
> > > > ++++++++++++++++++++++++++++++++++
> > > > > include/hw/acpi/generic_event_device.h | 29 ++++++++++++++
> > > > > 4 files changed, 106 insertions(+)
> > > > > create mode 100644 hw/acpi/generic_event_device.c create mode
> > > > 100644
> > > > > include/hw/acpi/generic_event_device.h
> > > > >
> > > > > diff --git a/hw/acpi/Kconfig b/hw/acpi/Kconfig index eca3bee..01a8b41
> > > > > 100644
> > > > > --- a/hw/acpi/Kconfig
> > > > > +++ b/hw/acpi/Kconfig
> > > > > @@ -27,3 +27,7 @@ config ACPI_VMGENID
> > > > > bool
> > > > > default y
> > > > > depends on PC
> > > > > +
> > > > > +config ACPI_HW_REDUCED
> > > > > + bool
> > > > > + depends on ACPI
> > > > > diff --git a/hw/acpi/Makefile.objs b/hw/acpi/Makefile.objs index
> > > > > 2d46e37..b753232 100644
> > > > > --- a/hw/acpi/Makefile.objs
> > > > > +++ b/hw/acpi/Makefile.objs
> > > > > @@ -6,6 +6,7 @@ common-obj-$(CONFIG_ACPI_MEMORY_HOTPLUG)
> > +=
> > > > > memory_hotplug.o
> > > > > common-obj-$(CONFIG_ACPI_CPU_HOTPLUG) += cpu.o
> > > > > common-obj-$(CONFIG_ACPI_NVDIMM) += nvdimm.o
> > > > > common-obj-$(CONFIG_ACPI_VMGENID) += vmgenid.o
> > > > > +common-obj-$(CONFIG_ACPI_HW_REDUCED) +=
> > generic_event_device.o
> > > > > common-obj-$(call lnot,$(CONFIG_ACPI_X86)) += acpi-stub.o
> > > > >
> > > > > common-obj-y += acpi_interface.o
> > > > > diff --git a/hw/acpi/generic_event_device.c
> > > > > b/hw/acpi/generic_event_device.c new file mode 100644 index
> > > > > 0000000..b21a551
> > > > > --- /dev/null
> > > > > +++ b/hw/acpi/generic_event_device.c
> > > > > @@ -0,0 +1,72 @@
> > > > > +/*
> > > > > + *
> > > > > + * Copyright (c) 2018 Intel Corporation
> > > > > + *
> > > > > + * This program is free software; you can redistribute it and/or
> > > > > +modify it
> > > > > + * under the terms and conditions of the GNU General Public License,
> > > > > + * version 2 or later, as published by the Free Software Foundation.
> > > > > + *
> > > > > + * This program is distributed in the hope 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, see <http://www.gnu.org/licenses/>.
> > > > > + */
> > > > > +
> > > > > +#include "qemu/osdep.h"
> > > > > +#include "hw/sysbus.h"
> > > > > +#include "hw/acpi/acpi.h"
> > > > > +#include "hw/acpi/generic_event_device.h"
> > > > the files are named generic_event_device.c/h while the device is named
> > > > "virt-acpi". I would suggest to use the same naming as in nemu ie. ged or
> > > > acpi_ged.
> > >
> > > Agree. The naming is a bit confusing. In nemu they have a separate virt-acpi
> > > dev which makes use of GED. Here, we are rolling those two into one. I am
> > > still not very sure whether we should leave it as virt-acpi, because the actual
> > > device on which this is implemented can be changed eg, GED vs GPIO.
> >
> > I probably lacking context here, could you clarify and maybe compare
> > differences between x86 and ARM implementations and why it should be
> > different devices?
> >
>
> Right. I was not comparing against x86, but just pointing out how Nemu has
> done this. They seems to have a virt-acpi dev specific to virt platforms
> (hw/i386/virt/acpi.c) and then moved all GED related code in a separate file
> (hw/acpi/ged.c) [1].
>
> I was just thinking whether that approach makes any sense going forward where
> there are cases where platforms support GED or GPIO for hotplug support and
> virt-acpi dev can be configured to use either of those. May be not.
from what I see that nemu uses GED only as ACPI aml code, while TYPE_VIRT_ACPI
actually implements hardware part of GED (i.e. initializes and owns MMIO/IRQs).
So it is GED device in practice.
If it's possible by ACPI spec to use GPIO with GED device, then I'd add it
later when there is actual usecase for it. Otherwise GPIO is just another
device with its own AML part to go with.
So I'd second Eric's suggestion to rename virt-acpi to acpi-ged
> Thanks,
> Shameer
>
> [1]https://github.com/intel/nemu/commit/bcff7ee8588f7049cd919ee8b349f219a873ec41#diff-82ce92e28467c5894c90311f0e6a75fb
>
> >
> > > > If think you should clarify what is the exact scope of this device. The patch
> > title
> > > > make think this is bound to be used only in machvirt (+ the virt prefix used in
> > > > numerous functions?). Is it also bound to be used by other architectures?
> > > > > +
> > > > > +static void virt_device_plug_cb(HotplugHandler *hotplug_dev,
> > > > > + DeviceState *dev, Error **errp)
> > { }
> > > > > +
> > > > > +static void virt_send_ged(AcpiDeviceIf *adev, AcpiEventStatusBits ev)
> > > > > +{ }
> > > > > +
> > > > > +static void virt_device_realize(DeviceState *dev, Error **errp) { }
> > > > > +
> > > > > +static Property virt_acpi_properties[] = {
> > > > > + DEFINE_PROP_END_OF_LIST(),
> > > > > +};
> > > > > +
> > > > > +static void virt_acpi_class_init(ObjectClass *class, void *data) {
> > > > > + DeviceClass *dc = DEVICE_CLASS(class);
> > > > > + HotplugHandlerClass *hc = HOTPLUG_HANDLER_CLASS(class);
> > > > > + AcpiDeviceIfClass *adevc = ACPI_DEVICE_IF_CLASS(class);
> > > > > +
> > > > > + dc->desc = "ACPI";
> > > > > + dc->props = virt_acpi_properties;
> > > > > + dc->realize = virt_device_realize;
> > > > > +
> > > > > + hc->plug = virt_device_plug_cb;
> > > > > +
> > > > > + adevc->send_event = virt_send_ged; }
> > > > > +
> > > > > +static const TypeInfo virt_acpi_info = {
> > > > > + .name = TYPE_VIRT_ACPI,
> > > > > + .parent = TYPE_SYS_BUS_DEVICE,
> > > > > + .instance_size = sizeof(VirtAcpiState),
> > > > > + .class_init = virt_acpi_class_init,
> > > > > + .interfaces = (InterfaceInfo[]) {
> > > > > + { TYPE_HOTPLUG_HANDLER },
> > > > > + { TYPE_ACPI_DEVICE_IF },
> > > > > + { }
> > > > > + }
> > > > > +};
> > > > > +
> > > > > +static void virt_acpi_register_types(void) {
> > > > > + type_register_static(&virt_acpi_info);
> > > > > +}
> > > > > +
> > > > > +type_init(virt_acpi_register_types)
> > > > > diff --git a/include/hw/acpi/generic_event_device.h
> > > > > b/include/hw/acpi/generic_event_device.h
> > > > > new file mode 100644
> > > > > index 0000000..f314515
> > > > > --- /dev/null
> > > > > +++ b/include/hw/acpi/generic_event_device.h
> > > > > @@ -0,0 +1,29 @@
> > > > > +/*
> > > > > + *
> > > > > + * Copyright (c) 2018 Intel Corporation
> > > > > + *
> > > > > + * This program is free software; you can redistribute it and/or
> > > > > +modify it
> > > > > + * under the terms and conditions of the GNU General Public License,
> > > > > + * version 2 or later, as published by the Free Software Foundation.
> > > > > + *
> > > > > + * This program is distributed in the hope 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, see <http://www.gnu.org/licenses/>.
> > > > > + */
> > > > Add a comment in the header introducing what is the role of this device?
> > > > link to GED spec? Explain the subset of the interfaces being implemented by
> > > > the device.
> > >
> > > Ok. I have added comments to that effect in patch #10, but I think I will make
> > it
> > > clear here as well.
> > >
> > > Cheers,
> > > Shameer
> > >
> > > > > +
> > > > > +#ifndef HW_ACPI_GED_H
> > > > > +#define HW_ACPI_GED_H
> > > > > +
> > > > > +#define TYPE_VIRT_ACPI "virt-acpi"
> > > > > +#define VIRT_ACPI(obj) \
> > > > > + OBJECT_CHECK(VirtAcpiState, (obj), TYPE_VIRT_ACPI)
> > > > > +
> > > > > +typedef struct VirtAcpiState {
> > > > > + SysBusDevice parent_obj;
> > > > > +} VirtAcpiState;
> > > > > +
> > > > > +#endif
> > > > >
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Igor Mammedov <imammedo@redhat.com>
To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
Cc: "peter.maydell@linaro.org" <peter.maydell@linaro.org>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
"shannon.zhaosl@gmail.com" <shannon.zhaosl@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Linuxarm <linuxarm@huawei.com>,
Auger Eric <eric.auger@redhat.com>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
"xuwei (O)" <xuwei5@huawei.com>,
"sebastien.boeuf@intel.com" <sebastien.boeuf@intel.com>
Subject: Re: [Qemu-devel] [PATCH v3 03/10] hw/arm/virt: Add virtual ACPI device
Date: Tue, 2 Apr 2019 08:31:09 +0200 [thread overview]
Message-ID: <20190402083109.4e8c354b@redhat.com> (raw)
In-Reply-To: <5FC3163CFD30C246ABAA99954A238FA839345569@lhreml524-mbb.china.huawei.com>
On Mon, 1 Apr 2019 14:21:40 +0000
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com> wrote:
> Hi Igor,
>
> > -----Original Message-----
> > From: Igor Mammedov [mailto:imammedo@redhat.com]
> > Sent: 01 April 2019 14:09
> > To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
> > Cc: Auger Eric <eric.auger@redhat.com>; qemu-devel@nongnu.org;
> > qemu-arm@nongnu.org; peter.maydell@linaro.org;
> > shannon.zhaosl@gmail.com; sameo@linux.intel.com;
> > sebastien.boeuf@intel.com; Linuxarm <linuxarm@huawei.com>; xuwei (O)
> > <xuwei5@huawei.com>
> > Subject: Re: [Qemu-devel] [PATCH v3 03/10] hw/arm/virt: Add virtual ACPI
> > device
> >
> > On Fri, 29 Mar 2019 11:22:02 +0000
> > Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com> wrote:
> >
> > > > -----Original Message-----
> > > > From: Auger Eric [mailto:eric.auger@redhat.com]
> > > > Sent: 28 March 2019 14:15
> > > > To: Shameerali Kolothum Thodi
> > <shameerali.kolothum.thodi@huawei.com>;
> > > > qemu-devel@nongnu.org; qemu-arm@nongnu.org;
> > imammedo@redhat.com;
> > > > peter.maydell@linaro.org; shannon.zhaosl@gmail.com;
> > > > sameo@linux.intel.com; sebastien.boeuf@intel.com
> > > > Cc: Linuxarm <linuxarm@huawei.com>; xuwei (O) <xuwei5@huawei.com>
> > > > Subject: Re: [PATCH v3 03/10] hw/arm/virt: Add virtual ACPI device
> > > >
> > > > Hi Shameer,
> > > >
> > > > On 3/21/19 11:47 AM, Shameer Kolothum wrote:
> > > > > From: Samuel Ortiz <sameo@linux.intel.com>
> > > > >
> > > > > This adds the skeleton to support an acpi device interface for
> > > > > HW-reduced acpi platforms via ACPI GED - Generic Event Device (ACPI
> > > > > v6.1 5.6.9).
> > > > >
> > > > > This will be used by Arm/Virt to add hotplug support.
> > > > >
> > > > > Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
> > > > > Signed-off-by: Shameer Kolothum
> > <shameerali.kolothum.thodi@huawei.com>
> > > > > ---
> > > > > hw/acpi/Kconfig | 4 ++
> > > > > hw/acpi/Makefile.objs | 1 +
> > > > > hw/acpi/generic_event_device.c | 72
> > > > ++++++++++++++++++++++++++++++++++
> > > > > include/hw/acpi/generic_event_device.h | 29 ++++++++++++++
> > > > > 4 files changed, 106 insertions(+)
> > > > > create mode 100644 hw/acpi/generic_event_device.c create mode
> > > > 100644
> > > > > include/hw/acpi/generic_event_device.h
> > > > >
> > > > > diff --git a/hw/acpi/Kconfig b/hw/acpi/Kconfig index eca3bee..01a8b41
> > > > > 100644
> > > > > --- a/hw/acpi/Kconfig
> > > > > +++ b/hw/acpi/Kconfig
> > > > > @@ -27,3 +27,7 @@ config ACPI_VMGENID
> > > > > bool
> > > > > default y
> > > > > depends on PC
> > > > > +
> > > > > +config ACPI_HW_REDUCED
> > > > > + bool
> > > > > + depends on ACPI
> > > > > diff --git a/hw/acpi/Makefile.objs b/hw/acpi/Makefile.objs index
> > > > > 2d46e37..b753232 100644
> > > > > --- a/hw/acpi/Makefile.objs
> > > > > +++ b/hw/acpi/Makefile.objs
> > > > > @@ -6,6 +6,7 @@ common-obj-$(CONFIG_ACPI_MEMORY_HOTPLUG)
> > +=
> > > > > memory_hotplug.o
> > > > > common-obj-$(CONFIG_ACPI_CPU_HOTPLUG) += cpu.o
> > > > > common-obj-$(CONFIG_ACPI_NVDIMM) += nvdimm.o
> > > > > common-obj-$(CONFIG_ACPI_VMGENID) += vmgenid.o
> > > > > +common-obj-$(CONFIG_ACPI_HW_REDUCED) +=
> > generic_event_device.o
> > > > > common-obj-$(call lnot,$(CONFIG_ACPI_X86)) += acpi-stub.o
> > > > >
> > > > > common-obj-y += acpi_interface.o
> > > > > diff --git a/hw/acpi/generic_event_device.c
> > > > > b/hw/acpi/generic_event_device.c new file mode 100644 index
> > > > > 0000000..b21a551
> > > > > --- /dev/null
> > > > > +++ b/hw/acpi/generic_event_device.c
> > > > > @@ -0,0 +1,72 @@
> > > > > +/*
> > > > > + *
> > > > > + * Copyright (c) 2018 Intel Corporation
> > > > > + *
> > > > > + * This program is free software; you can redistribute it and/or
> > > > > +modify it
> > > > > + * under the terms and conditions of the GNU General Public License,
> > > > > + * version 2 or later, as published by the Free Software Foundation.
> > > > > + *
> > > > > + * This program is distributed in the hope 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, see <http://www.gnu.org/licenses/>.
> > > > > + */
> > > > > +
> > > > > +#include "qemu/osdep.h"
> > > > > +#include "hw/sysbus.h"
> > > > > +#include "hw/acpi/acpi.h"
> > > > > +#include "hw/acpi/generic_event_device.h"
> > > > the files are named generic_event_device.c/h while the device is named
> > > > "virt-acpi". I would suggest to use the same naming as in nemu ie. ged or
> > > > acpi_ged.
> > >
> > > Agree. The naming is a bit confusing. In nemu they have a separate virt-acpi
> > > dev which makes use of GED. Here, we are rolling those two into one. I am
> > > still not very sure whether we should leave it as virt-acpi, because the actual
> > > device on which this is implemented can be changed eg, GED vs GPIO.
> >
> > I probably lacking context here, could you clarify and maybe compare
> > differences between x86 and ARM implementations and why it should be
> > different devices?
> >
>
> Right. I was not comparing against x86, but just pointing out how Nemu has
> done this. They seems to have a virt-acpi dev specific to virt platforms
> (hw/i386/virt/acpi.c) and then moved all GED related code in a separate file
> (hw/acpi/ged.c) [1].
>
> I was just thinking whether that approach makes any sense going forward where
> there are cases where platforms support GED or GPIO for hotplug support and
> virt-acpi dev can be configured to use either of those. May be not.
from what I see that nemu uses GED only as ACPI aml code, while TYPE_VIRT_ACPI
actually implements hardware part of GED (i.e. initializes and owns MMIO/IRQs).
So it is GED device in practice.
If it's possible by ACPI spec to use GPIO with GED device, then I'd add it
later when there is actual usecase for it. Otherwise GPIO is just another
device with its own AML part to go with.
So I'd second Eric's suggestion to rename virt-acpi to acpi-ged
> Thanks,
> Shameer
>
> [1]https://github.com/intel/nemu/commit/bcff7ee8588f7049cd919ee8b349f219a873ec41#diff-82ce92e28467c5894c90311f0e6a75fb
>
> >
> > > > If think you should clarify what is the exact scope of this device. The patch
> > title
> > > > make think this is bound to be used only in machvirt (+ the virt prefix used in
> > > > numerous functions?). Is it also bound to be used by other architectures?
> > > > > +
> > > > > +static void virt_device_plug_cb(HotplugHandler *hotplug_dev,
> > > > > + DeviceState *dev, Error **errp)
> > { }
> > > > > +
> > > > > +static void virt_send_ged(AcpiDeviceIf *adev, AcpiEventStatusBits ev)
> > > > > +{ }
> > > > > +
> > > > > +static void virt_device_realize(DeviceState *dev, Error **errp) { }
> > > > > +
> > > > > +static Property virt_acpi_properties[] = {
> > > > > + DEFINE_PROP_END_OF_LIST(),
> > > > > +};
> > > > > +
> > > > > +static void virt_acpi_class_init(ObjectClass *class, void *data) {
> > > > > + DeviceClass *dc = DEVICE_CLASS(class);
> > > > > + HotplugHandlerClass *hc = HOTPLUG_HANDLER_CLASS(class);
> > > > > + AcpiDeviceIfClass *adevc = ACPI_DEVICE_IF_CLASS(class);
> > > > > +
> > > > > + dc->desc = "ACPI";
> > > > > + dc->props = virt_acpi_properties;
> > > > > + dc->realize = virt_device_realize;
> > > > > +
> > > > > + hc->plug = virt_device_plug_cb;
> > > > > +
> > > > > + adevc->send_event = virt_send_ged; }
> > > > > +
> > > > > +static const TypeInfo virt_acpi_info = {
> > > > > + .name = TYPE_VIRT_ACPI,
> > > > > + .parent = TYPE_SYS_BUS_DEVICE,
> > > > > + .instance_size = sizeof(VirtAcpiState),
> > > > > + .class_init = virt_acpi_class_init,
> > > > > + .interfaces = (InterfaceInfo[]) {
> > > > > + { TYPE_HOTPLUG_HANDLER },
> > > > > + { TYPE_ACPI_DEVICE_IF },
> > > > > + { }
> > > > > + }
> > > > > +};
> > > > > +
> > > > > +static void virt_acpi_register_types(void) {
> > > > > + type_register_static(&virt_acpi_info);
> > > > > +}
> > > > > +
> > > > > +type_init(virt_acpi_register_types)
> > > > > diff --git a/include/hw/acpi/generic_event_device.h
> > > > > b/include/hw/acpi/generic_event_device.h
> > > > > new file mode 100644
> > > > > index 0000000..f314515
> > > > > --- /dev/null
> > > > > +++ b/include/hw/acpi/generic_event_device.h
> > > > > @@ -0,0 +1,29 @@
> > > > > +/*
> > > > > + *
> > > > > + * Copyright (c) 2018 Intel Corporation
> > > > > + *
> > > > > + * This program is free software; you can redistribute it and/or
> > > > > +modify it
> > > > > + * under the terms and conditions of the GNU General Public License,
> > > > > + * version 2 or later, as published by the Free Software Foundation.
> > > > > + *
> > > > > + * This program is distributed in the hope 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, see <http://www.gnu.org/licenses/>.
> > > > > + */
> > > > Add a comment in the header introducing what is the role of this device?
> > > > link to GED spec? Explain the subset of the interfaces being implemented by
> > > > the device.
> > >
> > > Ok. I have added comments to that effect in patch #10, but I think I will make
> > it
> > > clear here as well.
> > >
> > > Cheers,
> > > Shameer
> > >
> > > > > +
> > > > > +#ifndef HW_ACPI_GED_H
> > > > > +#define HW_ACPI_GED_H
> > > > > +
> > > > > +#define TYPE_VIRT_ACPI "virt-acpi"
> > > > > +#define VIRT_ACPI(obj) \
> > > > > + OBJECT_CHECK(VirtAcpiState, (obj), TYPE_VIRT_ACPI)
> > > > > +
> > > > > +typedef struct VirtAcpiState {
> > > > > + SysBusDevice parent_obj;
> > > > > +} VirtAcpiState;
> > > > > +
> > > > > +#endif
> > > > >
>
>
next prev parent reply other threads:[~2019-04-02 6:31 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 10:47 [Qemu-arm] [PATCH v3 00/10] ARM virt: ACPI memory hotplug support Shameer Kolothum
2019-03-21 10:47 ` [Qemu-devel] [PATCH v3 01/10] hw/acpi: Make ACPI IO address space configurable Shameer Kolothum
2019-04-01 12:58 ` [Qemu-arm] " Igor Mammedov
2019-04-01 12:58 ` [Qemu-devel] " Igor Mammedov
2019-03-21 10:47 ` [Qemu-devel] [PATCH v3 02/10] hw/acpi: Do not create memory hotplug method when handler is not defined Shameer Kolothum
2019-03-28 14:14 ` [Qemu-arm] " Auger Eric
2019-03-21 10:47 ` [Qemu-arm] [PATCH v3 03/10] hw/arm/virt: Add virtual ACPI device Shameer Kolothum
2019-03-28 14:14 ` Auger Eric
2019-03-29 11:22 ` Shameerali Kolothum Thodi
2019-04-01 13:08 ` [Qemu-arm] [Qemu-devel] " Igor Mammedov
2019-04-01 13:08 ` Igor Mammedov
2019-04-01 14:21 ` Shameerali Kolothum Thodi
2019-04-01 14:21 ` Shameerali Kolothum Thodi
2019-04-02 6:31 ` Igor Mammedov [this message]
2019-04-02 6:31 ` Igor Mammedov
2019-03-21 10:47 ` [Qemu-arm] [PATCH v3 04/10] hw/arm/virt: Add memory hotplug framework Shameer Kolothum
2019-03-28 15:37 ` Auger Eric
2019-03-29 12:03 ` Shameerali Kolothum Thodi
2019-03-21 10:47 ` [Qemu-devel] [PATCH v3 05/10] hw/arm/virt: Add ACPI support for device memory cold-plug Shameer Kolothum
2019-03-29 9:31 ` [Qemu-arm] " Auger Eric
2019-03-29 10:54 ` Shameerali Kolothum Thodi
2019-04-01 13:43 ` Igor Mammedov
2019-04-01 13:43 ` [Qemu-devel] " Igor Mammedov
2019-04-01 14:51 ` [Qemu-arm] " Shameerali Kolothum Thodi
2019-04-01 14:51 ` [Qemu-devel] " Shameerali Kolothum Thodi
2019-04-02 7:19 ` [Qemu-arm] " Igor Mammedov
2019-04-02 7:19 ` Igor Mammedov
2019-04-01 14:59 ` [Qemu-arm] " Auger Eric
2019-04-01 14:59 ` Auger Eric
2019-04-01 13:34 ` [Qemu-arm] " Igor Mammedov
2019-04-01 13:34 ` [Qemu-devel] " Igor Mammedov
2019-04-01 16:24 ` [Qemu-arm] " Shameerali Kolothum Thodi
2019-04-01 16:24 ` [Qemu-devel] " Shameerali Kolothum Thodi
2019-04-02 7:22 ` Igor Mammedov
2019-04-02 7:22 ` Igor Mammedov
2019-03-21 10:47 ` [Qemu-devel] [PATCH v3 06/10] hw/arm/virt-acpi-build: Add PC-DIMM in SRAT Shameer Kolothum
2019-03-21 10:47 ` [Qemu-arm] [PATCH v3 07/10] hw/arm/virt: Introduce opt-in feature "fdt" Shameer Kolothum
2019-03-29 9:31 ` Auger Eric
2019-03-29 9:41 ` Shameerali Kolothum Thodi
2019-03-29 13:41 ` Auger Eric
2019-03-29 9:59 ` Shameerali Kolothum Thodi
2019-03-29 13:12 ` Auger Eric
2019-03-29 13:14 ` Ard Biesheuvel
2019-03-29 13:56 ` [Qemu-arm] [Qemu-devel] " Auger Eric
2019-03-29 14:08 ` Shameerali Kolothum Thodi
2019-04-01 13:07 ` Laszlo Ersek
2019-04-01 13:07 ` Laszlo Ersek
2019-04-02 7:42 ` Igor Mammedov
2019-04-02 7:42 ` Igor Mammedov
2019-04-02 10:33 ` [Qemu-arm] " Laszlo Ersek
2019-04-02 10:33 ` Laszlo Ersek
2019-04-02 15:42 ` [Qemu-arm] " Auger Eric
2019-04-02 15:42 ` Auger Eric
2019-04-02 15:52 ` Laszlo Ersek
2019-04-02 15:52 ` Laszlo Ersek
2019-04-02 15:56 ` [Qemu-arm] " Laszlo Ersek
2019-04-02 15:56 ` Laszlo Ersek
2019-04-02 16:07 ` [Qemu-arm] " Auger Eric
2019-04-02 16:07 ` Auger Eric
2019-04-02 14:26 ` [Qemu-arm] " Shameerali Kolothum Thodi
2019-04-02 14:26 ` Shameerali Kolothum Thodi
2019-04-02 15:29 ` [Qemu-arm] " Auger Eric
2019-04-02 15:29 ` Auger Eric
2019-04-02 15:38 ` Laszlo Ersek
2019-04-02 15:38 ` Laszlo Ersek
2019-04-02 15:50 ` Auger Eric
2019-04-02 15:50 ` Auger Eric
2019-04-03 9:49 ` [Qemu-arm] " Igor Mammedov
2019-04-03 9:49 ` Igor Mammedov
2019-04-03 12:10 ` [Qemu-arm] " Shameerali Kolothum Thodi
2019-04-03 12:10 ` Shameerali Kolothum Thodi
2019-04-03 13:29 ` [Qemu-arm] " Laszlo Ersek
2019-04-03 13:29 ` Laszlo Ersek
2019-04-03 16:25 ` [Qemu-arm] " Shameerali Kolothum Thodi
2019-04-03 16:25 ` Shameerali Kolothum Thodi
2019-04-08 8:11 ` [Qemu-arm] " Igor Mammedov
2019-04-08 8:11 ` Igor Mammedov
2019-04-08 8:11 ` Igor Mammedov
2019-04-09 10:43 ` [Qemu-arm] " Shameerali Kolothum Thodi
2019-04-09 10:43 ` Shameerali Kolothum Thodi
2019-04-09 10:43 ` Shameerali Kolothum Thodi
2019-04-03 13:19 ` [Qemu-arm] " Laszlo Ersek
2019-04-03 13:19 ` Laszlo Ersek
2019-04-08 8:13 ` [Qemu-arm] " Igor Mammedov
2019-04-08 8:13 ` Igor Mammedov
2019-04-08 8:13 ` Igor Mammedov
2019-04-02 8:39 ` [Qemu-arm] " Peter Maydell
2019-04-02 8:39 ` Peter Maydell
2019-03-21 10:47 ` [Qemu-arm] [PATCH v3 08/10] hw/arm/boot: Expose the PC-DIMM nodes in the DT Shameer Kolothum
2019-03-21 10:47 ` [Qemu-devel] [PATCH v3 09/10] hw/acpi: Add ACPI Generic Event Device Support Shameer Kolothum
2019-03-29 13:09 ` [Qemu-arm] " Auger Eric
2019-03-29 13:44 ` Shameerali Kolothum Thodi
2019-03-21 10:47 ` [Qemu-devel] [PATCH v3 10/10] hw/arm/virt: Init GED device and enable memory hotplug Shameer Kolothum
2019-03-29 14:16 ` [Qemu-arm] " Auger Eric
2019-03-21 11:06 ` [Qemu-arm] [Qemu-devel] [PATCH v3 00/10] ARM virt: ACPI memory hotplug support no-reply
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=20190402083109.4e8c354b@redhat.com \
--to=imammedo@redhat.com \
--cc=eric.auger@redhat.com \
--cc=linuxarm@huawei.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sameo@linux.intel.com \
--cc=sebastien.boeuf@intel.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=shannon.zhaosl@gmail.com \
--cc=xuwei5@huawei.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 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.