qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Murilo Opsfelder Araujo <muriloo@linux.ibm.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>,
	Cornelia Huck <cohuck@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Alexander Graf <agraf@suse.de>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	qemu-s390x@nongnu.org, qemu-ppc@nongnu.org,
	Paolo Bonzini <pbonzini@redhat.com>,
	Marcel Apfelbaum <marcel@redhat.com>,
	Igor Mammedov <imammedo@redhat.com>,
	Luiz Capitulino <lcapitulino@redhat.com>,
	David Gibson <david@gibson.dropbear.id.au>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v2 16/17] s390x: initialize memory region for memory devices
Date: Fri, 11 May 2018 15:34:05 -0300	[thread overview]
Message-ID: <20180511183405.GA19020@kermit-br-ibm-com> (raw)
In-Reply-To: <20180511131953.12905-17-david@redhat.com>

On Fri, May 11, 2018 at 03:19:52PM +0200, David Hildenbrand wrote:
> While s390x has no real interface for communicating devices mapped into
> the physical address space of the guest, paravirtualized devices can
> easily expose the applicable address range themselves.
> 
> So let's use the difference between maxram_size and ram_size as the size
> for our hotplug memory area (just as on other architectures).
> 
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
>  hw/s390x/s390-virtio-ccw.c | 28 ++++++++++++++++++++++++++--
>  1 file changed, 26 insertions(+), 2 deletions(-)
> 
> diff --git a/hw/s390x/s390-virtio-ccw.c b/hw/s390x/s390-virtio-ccw.c
> index ee0a2b124f..09b755282b 100644
> --- a/hw/s390x/s390-virtio-ccw.c
> +++ b/hw/s390x/s390-virtio-ccw.c
> @@ -157,9 +157,11 @@ static void virtio_ccw_register_hcalls(void)
>  #define KVM_MEM_MAX_NR_PAGES ((1ULL << 31) - 1)
>  #define SEG_MSK (~0xfffffULL)
>  #define KVM_SLOT_MAX_BYTES ((KVM_MEM_MAX_NR_PAGES * TARGET_PAGE_SIZE) & SEG_MSK)
> -static void s390_memory_init(ram_addr_t mem_size)
> +static void s390_memory_init(MachineState *machine)
>  {
> +    S390CcwMachineState *ms = S390_CCW_MACHINE(machine);
>      MemoryRegion *sysmem = get_system_memory();
> +    ram_addr_t mem_size = machine->ram_size;
>      ram_addr_t chunk, offset = 0;
>      unsigned int number = 0;
>      gchar *name;
> @@ -181,6 +183,28 @@ static void s390_memory_init(ram_addr_t mem_size)
>      }
>      g_free(name);
>  
> +    /* always allocate the device memory information */
> +    machine->device_memory = g_malloc0(sizeof(*machine->device_memory));

Is there any QEMU guideline/preference/recommendation in using g_new0
vs. g_malloc0?

I recall Paolo suggesting g_new0 instead of g_malloc0 in another patch:

  http://lists.nongnu.org/archive/html/qemu-devel/2018-05/msg02372.html

> +
> +    /* initialize device memory address space */
> +    if (machine->ram_size < machine->maxram_size) {
> +        ram_addr_t device_mem_size = machine->maxram_size - machine->ram_size;
> +
> +        if (QEMU_ALIGN_UP(machine->maxram_size, TARGET_PAGE_SIZE) !=
> +            machine->maxram_size) {
> +            error_report("maximum memory size must be aligned to multiple of "
> +                         "%d bytes", TARGET_PAGE_SIZE);
> +            exit(EXIT_FAILURE);
> +        }
> +
> +        machine->device_memory->base = machine->ram_size;
> +        memory_region_init(&machine->device_memory->mr, OBJECT(ms),
> +                           "device-memory", device_mem_size);
> +        memory_region_add_subregion(sysmem, machine->device_memory->base,
> +                                    &machine->device_memory->mr);
> +
> +    }
> +
>      /* Initialize storage key device */
>      s390_skeys_init();
>      /* Initialize storage attributes device */
> @@ -304,7 +328,7 @@ static void ccw_init(MachineState *machine)
>      DeviceState *dev;
>  
>      s390_sclp_init();
> -    s390_memory_init(machine->ram_size);
> +    s390_memory_init(machine);
>  
>      /* init CPUs (incl. CPU model) early so s390_has_feature() works */
>      s390_init_cpus(machine);
> -- 
> 2.14.3
> 
> 

-- 
Murilo

  reply	other threads:[~2018-05-11 18:34 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 13:19 [Qemu-devel] [PATCH v2 00/17] MemoryDevice: use multi stage hotplug handlers David Hildenbrand
2018-05-11 13:19 ` [Qemu-devel] [PATCH v2 01/17] memory-device: drop assert related to align and start of address space David Hildenbrand
2018-05-14  1:24   ` Michael S. Tsirkin
2018-05-11 13:19 ` [Qemu-devel] [PATCH v2 02/17] qdev: let machine hotplug handler to override bus hotplug handler David Hildenbrand
2018-05-11 13:19 ` [Qemu-devel] [PATCH v2 03/17] pc: prepare for multi stage hotplug handlers David Hildenbrand
2018-05-11 13:19 ` [Qemu-devel] [PATCH v2 04/17] pc: route all memory devices through the machine hotplug handler David Hildenbrand
2018-05-12 14:47   ` Paolo Bonzini
2018-05-12 16:45     ` David Hildenbrand
2018-05-14  9:12     ` David Hildenbrand
2018-05-11 13:19 ` [Qemu-devel] [PATCH v2 05/17] spapr: prepare for multi stage hotplug handlers David Hildenbrand
2018-05-11 13:19 ` [Qemu-devel] [PATCH v2 06/17] spapr: route all memory devices through the machine hotplug handler David Hildenbrand
2018-05-11 13:19 ` [Qemu-devel] [PATCH v2 07/17] spapr: handle pc-dimm unplug via hotplug handler chain David Hildenbrand
2018-05-11 13:19 ` [Qemu-devel] [PATCH v2 08/17] spapr: handle cpu core " David Hildenbrand
2018-05-11 13:19 ` [Qemu-devel] [PATCH v2 09/17] memory-device: new functions to handle plug/unplug David Hildenbrand
2018-05-11 13:19 ` [Qemu-devel] [PATCH v2 10/17] pc-dimm: implement new memory device functions David Hildenbrand
2018-05-11 13:19 ` [Qemu-devel] [PATCH v2 11/17] memory-device: factor out pre-plug into hotplug handler David Hildenbrand
2018-05-11 13:19 ` [Qemu-devel] [PATCH v2 12/17] memory-device: factor out unplug " David Hildenbrand
2018-05-11 13:19 ` [Qemu-devel] [PATCH v2 13/17] memory-device: factor out plug " David Hildenbrand
2018-05-11 13:19 ` [Qemu-devel] [PATCH v2 14/17] s390x/sclp: make sure ram_size and maxram_size stay in sync David Hildenbrand
2018-05-11 13:19 ` [Qemu-devel] [PATCH v2 15/17] s390x: prepare for multi stage hotplug handlers David Hildenbrand
2018-05-11 13:19 ` [Qemu-devel] [PATCH v2 16/17] s390x: initialize memory region for memory devices David Hildenbrand
2018-05-11 18:34   ` Murilo Opsfelder Araujo [this message]
2018-05-11 18:43     ` Eduardo Habkost
2018-05-12  7:53       ` David Hildenbrand
2018-05-14 23:04         ` [Qemu-devel] [Qemu-ppc] " Murilo Opsfelder Araujo
2018-05-15  5:58           ` Markus Armbruster
2018-05-15  7:57             ` David Hildenbrand
2018-05-15 14:01               ` Murilo Opsfelder Araujo
2018-05-11 13:19 ` [Qemu-devel] [PATCH v2 17/17] s390x: support " 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=20180511183405.GA19020@kermit-br-ibm-com \
    --to=muriloo@linux.ibm.com \
    --cc=agraf@suse.de \
    --cc=armbru@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=david@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=lcapitulino@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).