From: Igor Mammedov <imammedo@redhat.com>
To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
Cc: "eric.auger@redhat.com" <eric.auger@redhat.com>,
"shannon.zhaosl@gmail.com" <shannon.zhaosl@gmail.com>,
"peter.maydell@linaro.org" <peter.maydell@linaro.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
Linuxarm <linuxarm@huawei.com>, "xuwei (O)" <xuwei5@huawei.com>
Subject: Re: [Qemu-devel] [RFC PATCH 3/4] hw/arm/virt: Enable pc-dimm hotplug support
Date: Fri, 1 Mar 2019 11:26:35 +0100 [thread overview]
Message-ID: <20190301112635.40200742@redhat.com> (raw)
In-Reply-To: <5FC3163CFD30C246ABAA99954A238FA8392D81D6@lhreml524-mbs.china.huawei.com>
On Fri, 1 Mar 2019 09:23:11 +0000
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com> wrote:
> > -----Original Message-----
> > From: Igor Mammedov [mailto:imammedo@redhat.com]
> > Sent: 01 March 2019 09:12
> > To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
> > Cc: eric.auger@redhat.com; shannon.zhaosl@gmail.com;
> > peter.maydell@linaro.org; qemu-devel@nongnu.org; qemu-arm@nongnu.org;
> > Linuxarm <linuxarm@huawei.com>; xuwei (O) <xuwei5@huawei.com>
> > Subject: Re: [Qemu-devel] [RFC PATCH 3/4] hw/arm/virt: Enable pc-dimm
> > hotplug support
> >
> > On Mon, 28 Jan 2019 11:05:45 +0000
> > Shameer Kolothum <shameerali.kolothum.thodi@huawei.com> wrote:
> >
> > > pc-dimm memory hotplug is enabled using GPIO(Pin 2) based ACPI
> > > event. Hot removal functionality is not yet supported.
> > >
> > > Signed-off-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
> > > ---
> > > hw/arm/virt.c | 57
> > +++++++++++++++++++++++++++++++++++++++++++++++++++++++--
> > > 1 file changed, 55 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/hw/arm/virt.c b/hw/arm/virt.c
> > > index 884960d..cf64554 100644
> > > --- a/hw/arm/virt.c
> > > +++ b/hw/arm/virt.c
> > > @@ -62,6 +62,7 @@
> > > #include "hw/mem/pc-dimm.h"
> > > #include "hw/mem/nvdimm.h"
> > > #include "hw/acpi/acpi.h"
> > > +#include "hw/acpi/pc-hotplug.h"
> > it looks like x86 specific file, what is this here for?
>
> Yes. That is for ACPI_MEMORY_HOTPLUG_BASE which is only used by x86
> at the moment. I guess, it can be moved to hw/acpi/memory_hotplug.h ?
it's GPA and pc/q35 impl. specific so you should use it,
this address will always be board specific one.
Makeup a virt specific one
>
> > >
> > > #define DEFINE_VIRT_MACHINE_LATEST(major, minor, latest) \
> > > static void virt_##major##_##minor##_class_init(ObjectClass *oc, \
> > > @@ -1651,7 +1652,14 @@ static void machvirt_init(MachineState
> > *machine)
> > > nvdimm_init_acpi_state(acpi_nvdimm_state, sysmem,
> > > vms->fw_cfg, OBJECT(vms));
> > > }
> > > + if (vms->acpi_memhp_state.is_enabled) {
> > > + MemHotplugState *state = &vms->acpi_memhp_state;
> > > + hwaddr base;
> > >
> > > + state->hw_reduced_acpi = true;
> > > + base = vms->memmap[VIRT_ACPI_IO].base +
> > ACPI_MEMORY_HOTPLUG_BASE;
well, this is confusing, why adding 2 base addresses?
If vms->memmap[VIRT_ACPI_IO].base is already set than why not use it
as is without adding an offset?
> > > + acpi_memory_hotplug_init(sysmem, OBJECT(vms), state, base);
> > > + }
> > > vms->bootinfo.ram_size = machine->ram_size;
> > > vms->bootinfo.kernel_filename = machine->kernel_filename;
> > > vms->bootinfo.kernel_cmdline = machine->kernel_cmdline;
> > [...]
next prev parent reply other threads:[~2019-03-01 10:26 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 11:05 [Qemu-devel] [RFC PATCH 0/4] ARM virt: ACPI memory hotplug support Shameer Kolothum
2019-01-28 11:05 ` [Qemu-devel] [RFC PATCH 1/4] hw:acpi: Make ACPI IO address space configurable Shameer Kolothum
2019-02-27 16:27 ` Igor Mammedov
2019-02-28 12:14 ` Shameerali Kolothum Thodi
2019-02-27 17:52 ` Auger Eric
2019-02-28 16:09 ` Shameerali Kolothum Thodi
2019-02-28 16:44 ` Igor Mammedov
2019-01-28 11:05 ` [Qemu-devel] [RFC PATCH 2/4] hw/arm/virt: Add GPIO based pcdimm hotplug ACPI event support Shameer Kolothum
2019-02-27 16:44 ` Igor Mammedov
2019-01-28 11:05 ` [Qemu-devel] [RFC PATCH 3/4] hw/arm/virt: Enable pc-dimm hotplug support Shameer Kolothum
2019-02-27 17:14 ` Igor Mammedov
2019-02-28 9:57 ` Auger Eric
2019-02-28 12:44 ` Igor Mammedov
2019-02-28 12:27 ` Shameerali Kolothum Thodi
2019-03-01 9:12 ` Igor Mammedov
2019-03-01 9:23 ` Shameerali Kolothum Thodi
2019-03-01 10:26 ` Igor Mammedov [this message]
2019-03-01 10:33 ` Igor Mammedov
2019-03-01 10:51 ` Shameerali Kolothum Thodi
2019-03-01 13:09 ` Igor Mammedov
2019-02-22 16:03 ` [Qemu-devel] [RFC PATCH 0/4] ARM virt: ACPI memory " Auger Eric
2019-02-22 19:11 ` Laszlo Ersek
2019-02-25 9:54 ` Shameerali Kolothum Thodi
2019-02-27 12:55 ` Shameerali Kolothum Thodi
2019-02-27 16:42 ` Igor Mammedov
2019-02-27 20:14 ` Laszlo Ersek
2019-02-28 10:12 ` Auger Eric
2019-02-28 12:04 ` Shameerali Kolothum Thodi
2019-02-28 12:27 ` Laszlo Ersek
2019-02-28 13:32 ` Auger Eric
2019-02-28 13:43 ` Igor Mammedov
2019-02-28 14:02 ` Shameerali Kolothum Thodi
2019-03-01 13:49 ` Laszlo Ersek
2019-03-01 17:39 ` Igor Mammedov
2019-03-05 12:14 ` Laszlo Ersek
2019-02-25 9:47 ` Shameerali Kolothum Thodi
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=20190301112635.40200742@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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).