From: David Hildenbrand <david@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-s390x@nongnu.org, "Michael S . Tsirkin" <mst@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Marcel Apfelbaum <marcel@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>,
Eduardo Habkost <ehabkost@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>,
"Markus Armbruster --cc=qemu-ppc @ nongnu . org"
<armbru@redhat.com>
Subject: [Qemu-devel] [PATCH v1 0/3] pc-dimm: factor out MemoryDevice
Date: Thu, 12 Apr 2018 11:19:33 +0200 [thread overview]
Message-ID: <20180412091936.32446-1-david@redhat.com> (raw)
Right now we can only map PCDIMM/NVDIMM into guest address space. In the
future, we might want to do the same for virtio devices - e.g.
virtio-pmem or virtio-mem. Especially, they should be able to live side
by side to each other.
E.g. the virto based memory devices regions will not be exposed via ACPI
and friends. They will be detected just like other virtio devices and
indicate the applicable memory region. This makes it possible to also use
them on architectures without memory device detection support (e.g. s390x).
Let's factor out the memory device code into a MemoryDevice interface.
See the patch descriptions for details.
David Hildenbrand (3):
pc-dimm: factor out MemoryDevice interface
machine: make MemoryHotplugState accessible via the machine
pc-dimm: factor out address space logic into MemoryDevice code
hw/i386/acpi-build.c | 3 +-
hw/i386/pc.c | 24 ++-
hw/mem/Makefile.objs | 1 +
hw/mem/memory-device.c | 281 +++++++++++++++++++++++++
hw/mem/pc-dimm.c | 304 +++++++--------------------
hw/ppc/spapr.c | 15 +-
include/hw/boards.h | 16 ++
include/hw/mem/memory-device.h | 48 +++++
include/hw/mem/pc-dimm.h | 26 +--
numa.c | 3 +-
qmp.c | 4 +-
stubs/Makefile.objs | 2 +-
stubs/{qmp_pc_dimm.c => qmp_memory_device.c} | 4 +-
13 files changed, 460 insertions(+), 271 deletions(-)
create mode 100644 hw/mem/memory-device.c
create mode 100644 include/hw/mem/memory-device.h
rename stubs/{qmp_pc_dimm.c => qmp_memory_device.c} (61%)
--
2.14.3
next reply other threads:[~2018-04-12 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 9:19 David Hildenbrand [this message]
2018-04-12 9:19 ` [Qemu-devel] [PATCH v1 1/3] pc-dimm: factor out MemoryDevice interface David Hildenbrand
2018-04-12 9:19 ` [Qemu-devel] [PATCH v1 2/3] machine: make MemoryHotplugState accessible via the machine David Hildenbrand
2018-04-12 9:19 ` [Qemu-devel] [PATCH v1 3/3] pc-dimm: factor out address space logic into MemoryDevice code David Hildenbrand
2018-04-12 9:35 ` [Qemu-devel] [PATCH v1 0/3] pc-dimm: factor out MemoryDevice no-reply
2018-04-12 9:53 ` David Hildenbrand
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=20180412091936.32446-1-david@redhat.com \
--to=david@redhat.com \
--cc=armbru@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
/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).