From: Thomas Huth <thuth@redhat.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Matthew Rosato <mjrosato@linux.vnet.ibm.com>,
agraf@suse.de, qemu-devel@nongnu.org,
Markus Armbruster <armbru@redhat.com>,
borntraeger@de.ibm.com, jfrei@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH for-2.6 04/10] s390x/cpu: Tolerate max_cpus
Date: Thu, 10 Mar 2016 11:37:59 +0100 [thread overview]
Message-ID: <56E14E87.8070105@redhat.com> (raw)
In-Reply-To: <20160310105255.7780b6f1.cornelia.huck@de.ibm.com>
On 10.03.2016 10:52, Cornelia Huck wrote:
> On Wed, 9 Mar 2016 22:55:30 +0100
> Thomas Huth <thuth@redhat.com> wrote:
>
>> While you're at it, it might be better to use g_new0 here instead
>> (see e.g. https://patchwork.ozlabs.org/patch/517377/ for a description
>> why this is better).
>
> Using g_new0 sounds sensible; but rather than respinning again, I'll
> just put the following on top:
>
> From 0a11840959f61861672858ce961fc34b71efa3be Mon Sep 17 00:00:00 2001
> From: Cornelia Huck <cornelia.huck@de.ibm.com>
> Date: Thu, 10 Mar 2016 10:19:46 +0100
> Subject: [PATCH] s390x/cpu: use g_new0
>
> Let's use g_new0 to allocate cpu_states.
>
> Suggested-by: Thomas Huth <thuth@redhat.com>
> Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
> ---
> hw/s390x/s390-virtio.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/s390x/s390-virtio.c b/hw/s390x/s390-virtio.c
> index 4ea9040..7c6e281 100644
> --- a/hw/s390x/s390-virtio.c
> +++ b/hw/s390x/s390-virtio.c
> @@ -103,7 +103,7 @@ void s390_init_cpus(MachineState *machine)
> machine->cpu_model = "host";
> }
>
> - cpu_states = g_malloc0(sizeof(S390CPU *) * max_cpus);
> + cpu_states = g_new0(S390CPU *, max_cpus);
>
> for (i = 0; i < max_cpus; i++) {
> name = g_strdup_printf("cpu[%i]", i);
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2016-03-10 10:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 17:27 [Qemu-devel] [PATCH for-2.6 00/10] s390x patches for 2.6 Cornelia Huck
2016-03-09 17:27 ` [Qemu-devel] [PATCH for-2.6 01/10] s390x/cpu: Cleanup init in preparation for hotplug Cornelia Huck
2016-03-09 17:28 ` [Qemu-devel] [PATCH for-2.6 02/10] s390x/cpu: Set initial CPU state in common routine Cornelia Huck
2016-03-09 17:28 ` [Qemu-devel] [PATCH for-2.6 03/10] s390x/cpu: Get rid of side effects when creating a vcpu Cornelia Huck
2016-03-09 17:28 ` [Qemu-devel] [PATCH for-2.6 04/10] s390x/cpu: Tolerate max_cpus Cornelia Huck
2016-03-09 21:55 ` Thomas Huth
2016-03-10 9:52 ` Cornelia Huck
2016-03-10 10:37 ` Thomas Huth [this message]
2016-03-09 17:28 ` [Qemu-devel] [PATCH for-2.6 05/10] s390x/cpu: Add CPU property links Cornelia Huck
2016-03-09 17:28 ` [Qemu-devel] [PATCH for-2.6 06/10] s390x/cpu: Add error handling to cpu creation Cornelia Huck
2016-03-09 17:28 ` [Qemu-devel] [PATCH for-2.6 07/10] s390x/cpu: Allow hotplug of CPUs Cornelia Huck
2016-03-09 17:28 ` [Qemu-devel] [PATCH for-2.6 08/10] pc-bios/s390-ccw: fix old bug in ptr increment Cornelia Huck
2016-03-09 17:28 ` [Qemu-devel] [PATCH for-2.6 09/10] s390x: Introduce machine definition macros Cornelia Huck
2016-03-09 17:28 ` [Qemu-devel] [PATCH for-2.6 10/10] s390x: Introduce S390MachineClass Cornelia Huck
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=56E14E87.8070105@redhat.com \
--to=thuth@redhat.com \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=mjrosato@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
/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).