qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: zhaotianrui <zhaotianrui@loongson.cn>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: richard.henderson@linaro.org, peter.maydell@linaro.org,
	imammedo@redhat.com, anisinha@redhat.com, mst@redhat.com,
	alex.bennee@linaro.org, maobibo@loongson.cn,
	yangxiaojuan@loongson.cn, gaosong@loongson.cn
Subject: Re: [PATCH] hw/loongarch: Supplement cpu topology arguments
Date: Wed, 14 Jun 2023 09:35:11 +0800	[thread overview]
Message-ID: <ae679a39-aec8-a38c-9409-fc2d77802017@loongson.cn> (raw)
In-Reply-To: <7565da8d-a7ad-ba02-9a59-9a441da2d988@linaro.org>


在 2023/6/13 下午8:55, Philippe Mathieu-Daudé 写道:
> On 13/6/23 14:32, Tianrui Zhao wrote:
>> Supplement LoongArch cpu topology arguments, including support socket
>> and threads per core.
>>
>> Base-on:
>> https://patchew.org/QEMU/20230613122613.2471743-1-zhaotianrui@loongson.cn/ 
>>
>
> ^ FYI this tag ...
>
>> Signed-off-by: Song Gao <gaosong@loongson.cn>
>> Signed-off-by: Tianrui Zhao <zhaotianrui@loongson.cn>
>> ---
>
> ... goes here after the '---' separator, because it is only helpful when
> testing/merging the patch. Once it is committed, this become irrelevant.
> (Everything after the '---' separator is normally stripped when applying
> patches).
>
Thanks, I will move the 'Base-on' flag after the '---'.

Tianrui Zhao

>>   hw/loongarch/acpi-build.c | 4 ++++
>>   hw/loongarch/virt.c       | 9 ++++++++-
>>   2 files changed, 12 insertions(+), 1 deletion(-)
>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>



  reply	other threads:[~2023-06-14  1:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13 12:32 [PATCH] hw/loongarch: Supplement cpu topology arguments Tianrui Zhao
2023-06-13 12:55 ` Philippe Mathieu-Daudé
2023-06-14  1:35   ` zhaotianrui [this message]
2023-06-16  7:10 ` Song Gao
  -- strict thread matches above, loose matches on Subject: below --
2023-05-30 12:59 Tianrui Zhao

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=ae679a39-aec8-a38c-9409-fc2d77802017@loongson.cn \
    --to=zhaotianrui@loongson.cn \
    --cc=alex.bennee@linaro.org \
    --cc=anisinha@redhat.com \
    --cc=gaosong@loongson.cn \
    --cc=imammedo@redhat.com \
    --cc=maobibo@loongson.cn \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=yangxiaojuan@loongson.cn \
    /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).