From: Igor Mammedov <imammedo@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: Pankaj Gupta <pagupta@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
qemu-s390x@nongnu.org, qemu-ppc@nongnu.org,
Marcel Apfelbaum <marcel@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH v3 3/3] pc-dimm: factor out address space logic into MemoryDevice code
Date: Tue, 24 Apr 2018 16:38:56 +0200 [thread overview]
Message-ID: <20180424163856.6584a73c@redhat.com> (raw)
In-Reply-To: <44c86da6-7851-d0c6-1121-6d1395a705c6@redhat.com>
On Tue, 24 Apr 2018 15:39:30 +0200
David Hildenbrand <david@redhat.com> wrote:
> On 24.04.2018 15:28, Igor Mammedov wrote:
> > On Mon, 23 Apr 2018 14:44:34 +0200
> > David Hildenbrand <david@redhat.com> wrote:
> >
> >> On 23.04.2018 14:19, Igor Mammedov wrote:
> >>> On Fri, 20 Apr 2018 14:34:56 +0200
> >>> David Hildenbrand <david@redhat.com> wrote:
> > considering v4 queued, I'm dropping mostly nor relevant points at this point.
> > wrt, virtio I'll elaborate more in reply to Pankaj
> >
> > [...]
> >
> >>>> diff --git a/hw/mem/memory-device.c b/hw/mem/memory-device.c
> >>>> index b860c9c582..b96efa3bf4 100644
> >>>> --- a/hw/mem/memory-device.c
> >>>> +++ b/hw/mem/memory-device.c
> >>>> @@ -15,6 +15,8 @@
> >>>> #include "qapi/error.h"
> >>>> #include "hw/boards.h"
> >>>> #include "qemu/range.h"
> >>>> +#include "hw/virtio/vhost.h"
> >>>> +#include "sysemu/kvm.h"
> >>>>
> >>>> static gint memory_device_addr_sort(gconstpointer a, gconstpointer b)
> >>>> {
> >>>> @@ -106,6 +108,166 @@ uint64_t get_plugged_memory_size(void)
> >>>> return size;
> >>>> }
> >>>>
> >>>> +static int memory_device_used_region_size_internal(Object *obj, void *opaque)
> >>>> +{
> >>>> + uint64_t *size = opaque;
> >>>> +
> >>>> + if (object_dynamic_cast(obj, TYPE_MEMORY_DEVICE)) {
> >>>> + DeviceState *dev = DEVICE(obj);
> >>>> + MemoryDeviceState *md = MEMORY_DEVICE(obj);
> >>>> + MemoryDeviceClass *mdc = MEMORY_DEVICE_GET_CLASS(obj);
> >>>> +
> >>>> + if (dev->realized) {
> >>>> + *size += mdc->get_region_size(md, &error_abort);
> >>>> + }
> >>>> + }
> >>>> +
> >>>> + object_child_foreach(obj, memory_device_used_region_size_internal, opaque);
> >>>> + return 0;
> >>>> +}
> >>>> +
> >>>> +static uint64_t memory_device_used_region_size(void)
> >>>> +{
> >>>> + uint64_t size = 0;
> >>>> +
> >>>> + memory_device_used_region_size_internal(qdev_get_machine(), &size);
> >>>> +
> >>>> + return size;
> >>>> +}
> >>>> +
> >>>> +uint64_t memory_device_get_free_addr(uint64_t *hint, uint64_t align,
> >>>> + uint64_t size, Error **errp)
> >>> I'd suggest to pc_dimm_memory_plug/pc_dimm_get_free_addr first,
> >>> namely most of the stuff it does like checks and assigning default
> >>> values should go to pre_plug (pre realize) handler and then only
> >>> actual mapping is left for plug (after realize) handler to deal with:
> >>>
> >>
> >> Can you elaborate what you mean by pre-plug? If this is about pre plug
> >> handler of the (machine) hotplug handler, it might be problematic for
> >> virtio devices.
> > yes, something along these lines: c871bc70b
> >
> >
>
> Yes, we can factor that out (at least) for pc-dimm later on easily.
> Seems to be just about moving a couple of calls.
yep, but there is nice side effect,
there is no need to call devicefoo::unrealize() on failure since
devicefoo:realize() hasn't been called yet.
next prev parent reply other threads:[~2018-04-24 14:39 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 [this message]
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
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=20180424163856.6584a73c@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 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).