qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Bibo Mao" <maobibo@loongson.cn>,
	"Song Gao" <gaosong@loongson.cn>, "Peter Xu" <peterx@redhat.com>,
	"Fabiano Rosas" <farosas@suse.de>,
	"Laurent Vivier" <lvivier@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	qemu-devel@nongnu.org,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v4 1/5] hw/loongarch: Rename LOONGARCH_MACHINE with LOONGARCH_VIRT_MACHINE
Date: Fri, 13 Sep 2024 10:02:25 +0200	[thread overview]
Message-ID: <87jzfg2d7y.fsf@pond.sub.org> (raw)
In-Reply-To: <2f7acdd5-9d9d-442c-a19f-c8a5828ae02b@redhat.com> (Thomas Huth's message of "Fri, 13 Sep 2024 09:36:42 +0200")

Thomas Huth <thuth@redhat.com> writes:

> On 08/05/2024 05.11, Bibo Mao wrote:
>> On LoongArch system, there is only virt machine type now, name
>> LOONGARCH_MACHINE is confused, rename it with LOONGARCH_VIRT_MACHINE.
>> Machine name about Other real hw boards can be added in future.
>> Signed-off-by: Bibo Mao <maobibo@loongson.cn>
>> ---
> ...
>> diff --git a/hw/loongarch/virt.c b/hw/loongarch/virt.c
>> index c0999878df..6619cb52a9 100644
>> --- a/hw/loongarch/virt.c
>> +++ b/hw/loongarch/virt.c
> ...
>> @@ -1208,7 +1208,6 @@ static void loongarch_class_init(ObjectClass *oc, void *data)
>>       MachineClass *mc = MACHINE_CLASS(oc);
>>       HotplugHandlerClass *hc = HOTPLUG_HANDLER_CLASS(oc);
>>   -    mc->desc = "Loongson-3A5000 LS7A1000 machine";
>>       mc->init = loongarch_init;
>>       mc->default_ram_size = 1 * GiB;
>>       mc->default_cpu_type = LOONGARCH_CPU_TYPE_NAME("la464");
>
>  Hi!
>
> I noticed that the machine now does not have any description anymore, which is kind of ugly when you list the available machines:
>
> $ ./qemu-system-loongarch64 -M help
> Supported machines are:
> none                 empty machine
> virt                 (null) (default)
>
> Could you please come up with a new mc->desc for the virt machine?

Formatting a null pointer with %s is actually a crash bug on some
systems.



  reply	other threads:[~2024-09-13  8:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08  3:11 [PATCH v4 0/5] Add migration test for loongarch64 Bibo Mao
2024-05-08  3:11 ` [PATCH v4 1/5] hw/loongarch: Rename LOONGARCH_MACHINE with LOONGARCH_VIRT_MACHINE Bibo Mao
2024-05-08 15:08   ` Philippe Mathieu-Daudé
2024-09-13  7:36   ` Thomas Huth
2024-09-13  8:02     ` Markus Armbruster [this message]
2024-09-13  9:25       ` maobibo
2024-05-08  3:11 ` [PATCH v4 2/5] hw/loongarch: Rename LoongArchMachineState with LoongArchVirtMachineState Bibo Mao
2024-05-08 15:08   ` Philippe Mathieu-Daudé
2024-05-08  3:11 ` [PATCH v4 3/5] hw/loongarch: Add compat machine for 9.0 Bibo Mao
2024-05-08  3:11 ` [PATCH v4 4/5] hw/loongarch: Set minimium memory size as 256M Bibo Mao
2024-05-08  3:11 ` [PATCH v4 5/5] tests: Add migration test for loongarch64 Bibo Mao
2024-05-08 21:58 ` [PATCH v4 0/5] " Philippe Mathieu-Daudé

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=87jzfg2d7y.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=farosas@suse.de \
    --cc=gaosong@loongson.cn \
    --cc=lvivier@redhat.com \
    --cc=maobibo@loongson.cn \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /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).