From: Igor Mammedov <imammedo@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: qemu-devel@nongnu.org, Pankaj Gupta <pagupta@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-s390x@nongnu.org, qemu-ppc@nongnu.org,
Paolo Bonzini <pbonzini@redhat.com>,
Marcel Apfelbaum <marcel@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v3 0/3] pc-dimm: factor out MemoryDevice
Date: Mon, 23 Apr 2018 14:31:47 +0200 [thread overview]
Message-ID: <20180423143147.6b4df2ac@redhat.com> (raw)
In-Reply-To: <20180420123456.22196-1-david@redhat.com>
On Fri, 20 Apr 2018 14:34:53 +0200
David Hildenbrand <david@redhat.com> wrote:
> 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.
A couple of high level questions as relevant code is not here:
1. what would hotplug/unplug call chain look like in case of virtio-pmem device
(reason I'm asking is that pmem being PCI device would trigger
PCI bus hotplug controller and then it somehow should piggyback
to Machine provided hotplug handlers, so I wonder what kind of
havoc it would cause on hotplug infrastructure)
2. why not use PCI bar mapping mechanism to do mapping since pmem is PCI device?
> v2 -> v3:
> - "pc-dimm: factor out MemoryDevice interface"
> --> Lookup both classes when comparing (David Gibson)
>
> v1 -> v2:
> - Fix compile issues on ppc (still untested )
>
>
> 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 | 282 +++++++++++++++++++++++++
> hw/mem/pc-dimm.c | 304 +++++++--------------------
> hw/ppc/spapr.c | 24 ++-
> hw/ppc/spapr_hcall.c | 1 +
> 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 +-
> 14 files changed, 465 insertions(+), 277 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%)
>
next prev parent reply other threads:[~2018-04-23 12:32 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 12:34 [Qemu-devel] [PATCH v3 0/3] pc-dimm: factor out MemoryDevice David Hildenbrand
2018-04-20 12:34 ` [Qemu-devel] [PATCH v3 1/3] pc-dimm: factor out MemoryDevice interface David Hildenbrand
2018-04-22 4:26 ` David Gibson
2018-04-22 8:21 ` David Hildenbrand
2018-04-22 10:10 ` David Gibson
2018-04-23 9:52 ` David Hildenbrand
2018-04-22 5:09 ` Pankaj Gupta
2018-04-22 8:26 ` David Hildenbrand
2018-04-20 12:34 ` [Qemu-devel] [PATCH v3 2/3] machine: make MemoryHotplugState accessible via the machine David Hildenbrand
2018-04-23 3:28 ` David Gibson
2018-04-23 9:36 ` David Hildenbrand
2018-04-23 10:44 ` David Gibson
2018-04-23 11:11 ` David Hildenbrand
2018-04-20 12:34 ` [Qemu-devel] [PATCH v3 3/3] pc-dimm: factor out address space logic into MemoryDevice code David Hildenbrand
2018-04-23 12:19 ` Igor Mammedov
2018-04-23 12:44 ` David Hildenbrand
2018-04-24 13:28 ` Igor Mammedov
2018-04-24 13:39 ` David Hildenbrand
2018-04-24 14:38 ` Igor Mammedov
2018-04-23 12:52 ` David Hildenbrand
2018-04-24 13:31 ` Igor Mammedov
2018-04-24 13:41 ` David Hildenbrand
2018-04-24 14:44 ` Igor Mammedov
2018-04-24 15:23 ` David Hildenbrand
2018-04-25 5:45 ` Pankaj Gupta
2018-04-25 13:23 ` Igor Mammedov
2018-04-25 13:56 ` Pankaj Gupta
2018-04-25 15:26 ` Igor Mammedov
2018-04-26 7:37 ` Pankaj Gupta
2018-05-04 9:13 ` [Qemu-devel] [PATCH v3 3/3] virtio-pmem: should we make it migratable??? Igor Mammedov
2018-05-04 9:30 ` David Hildenbrand
2018-05-04 11:59 ` Pankaj Gupta
2018-05-04 12:26 ` Dr. David Alan Gilbert
2018-05-07 8:12 ` Igor Mammedov
2018-05-07 11:19 ` Pankaj Gupta
2018-05-08 9:44 ` Dr. David Alan Gilbert
2018-04-23 14:44 ` [Qemu-devel] [PATCH v3 3/3] pc-dimm: factor out address space logic into MemoryDevice code David Hildenbrand
2018-04-22 4:58 ` [Qemu-devel] [PATCH v3 0/3] pc-dimm: factor out MemoryDevice Pankaj Gupta
2018-04-22 8:20 ` David Hildenbrand
2018-04-23 4:58 ` Pankaj Gupta
2018-04-23 12:31 ` Igor Mammedov [this message]
2018-04-23 12:50 ` David Hildenbrand
2018-04-23 15:32 ` Pankaj Gupta
2018-04-23 16:35 ` David Hildenbrand
2018-04-24 14:00 ` Igor Mammedov
2018-04-24 15:42 ` David Hildenbrand
2018-04-25 12:15 ` Igor Mammedov
2018-04-25 12:46 ` David Hildenbrand
2018-04-25 13:15 ` 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=20180423143147.6b4df2ac@redhat.com \
--to=imammedo@redhat.com \
--cc=armbru@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=david@redhat.com \
--cc=ehabkost@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=pagupta@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 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.