From: Eric Auger <eric.auger@redhat.com>
To: eric.auger.pro@gmail.com, eric.auger@redhat.com,
qemu-devel@nongnu.org, qemu-arm@nongnu.org,
peter.maydell@linaro.org, shameerali.kolothum.thodi@huawei.com,
imammedo@redhat.com, david@redhat.com, pbonzini@redhat.com,
ehabkost@redhat.com, richard.henderson@linaro.org,
sbhat@linux.ibm.com, philmd@redhat.com
Subject: [Qemu-devel] [PATCH v3 0/2] machine: Move nvdimms state into struct MachineState
Date: Fri, 8 Mar 2019 16:25:09 +0100 [thread overview]
Message-ID: <20190308152511.10882-1-eric.auger@redhat.com> (raw)
As NVDIMM support is looming for ARM and SPAPR, let's
move the acpi_nvdimm_state to the generic machine struct
instead of duplicating the same code in several machines.
nvdimm and nvdimm-persistence become generic machine options.
They become guarded by a nvdimm_supported machine class member.
Best regards
Eric
https://github.com/eauger/qemu/tree/nvdimms_state_v3
Eric Auger (2):
nvdimm: Rename AcpiNVDIMMState into NVDIMMState
machine: Move nvdimms state into struct MachineState
hw/acpi/nvdimm.c | 18 ++++++------
hw/core/machine.c | 65 +++++++++++++++++++++++++++++++++++++++++
hw/i386/acpi-build.c | 6 ++--
hw/i386/pc.c | 57 ++++--------------------------------
hw/i386/pc_piix.c | 4 +--
hw/i386/pc_q35.c | 4 +--
include/hw/boards.h | 2 ++
include/hw/i386/pc.h | 4 ---
include/hw/mem/nvdimm.h | 10 +++----
9 files changed, 93 insertions(+), 77 deletions(-)
--
2.20.1
next reply other threads:[~2019-03-08 15:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 15:25 Eric Auger [this message]
2019-03-08 15:25 ` [Qemu-devel] [PATCH v3 1/2] nvdimm: Rename AcpiNVDIMMState into NVDIMMState Eric Auger
2019-03-08 17:59 ` Philippe Mathieu-Daudé
2019-03-08 15:25 ` [Qemu-devel] [PATCH v3 2/2] machine: Move nvdimms state into struct MachineState Eric Auger
2019-03-08 17:42 ` Eduardo Habkost
2019-03-08 17:45 ` Eduardo Habkost
2019-03-08 18:02 ` Philippe Mathieu-Daudé
2019-03-08 18:16 ` Auger Eric
2019-03-08 21:04 ` Philippe Mathieu-Daudé
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=20190308152511.10882-1-eric.auger@redhat.com \
--to=eric.auger@redhat.com \
--cc=david@redhat.com \
--cc=ehabkost@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sbhat@linux.ibm.com \
--cc=shameerali.kolothum.thodi@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).