All of lore.kernel.org
 help / color / mirror / Atom feed
From: lixianglai <lixianglai@loongson.cn>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Song Gao" <gaosong@loongson.cn>,
	qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, Andrea Bolognani <abologna@redhat.com>,
	maobibo@loongson.cn, zhaotianrui@loongson.cn
Subject: Re: [PULL v2 1/1] loongarch: Change the UEFI loading mode to loongarch
Date: Sat, 2 Mar 2024 10:31:50 +0800	[thread overview]
Message-ID: <5e2419ec-6c1f-e21c-2105-fadb5971239c@loongson.cn> (raw)
In-Reply-To: <168d29d9-b82e-4dd5-abdd-93759037033c@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1871 bytes --]

Hi Philippe:
> On 29/2/24 12:38, Song Gao wrote:
>> From: Xianglai Li <lixianglai@loongson.cn>
>>
>> The UEFI loading mode in loongarch is very different
>> from that in other architectures:loongarch's UEFI code
>> is in rom, while other architectures' UEFI code is in flash.
>>
>> loongarch UEFI can be loaded as follows:
>> -machine virt,pflash=pflash0-format
>> -bios ./QEMU_EFI.fd
>>
>> Other architectures load UEFI using the following methods:
>> -machine virt,pflash0=pflash0-format,pflash1=pflash1-format
>>
>> loongarch's UEFI loading method makes qemu and libvirt incompatible
>> when using NVRAM, and the cost of loongarch's current loading method
>> far outweighs the benefits, so we decided to use the same UEFI loading
>> scheme as other architectures.
>
> FYI I'm still trying to find a way to avoid that, planning to discuss
> more with libvirt folks. Well, maybe it is a waste of my time and I
> should just stop worrying / caring about this long standing issue.
>
Thank you so much for your attention to this issue

and your long-standing contributions to the community!!:-)

Best regards,

Xianglai.


>> Cc: Andrea Bolognani <abologna@redhat.com>
>> Cc: maobibo@loongson.cn
>> Cc: Philippe Mathieu-Daudé <philmd@linaro.org>
>> Cc: Song Gao <gaosong@loongson.cn>
>> Cc: zhaotianrui@loongson.cn
>> Signed-off-by: Xianglai Li <lixianglai@loongson.cn>
>> Tested-by: Andrea Bolognani <abologna@redhat.com>
>> Reviewed-by: Song Gao <gaosong@loongson.cn>
>> Message-Id: 
>> <0bd892aa9b88e0f4cc904cb70efd0251fc1cde29.1708336919.git.lixianglai@loongson.cn>
>> Signed-off-by: Song Gao <gaosong@loongson.cn>
>> ---
>>   hw/loongarch/acpi-build.c   |  29 +++++++++--
>>   hw/loongarch/virt.c         | 101 ++++++++++++++++++++++++++----------
>>   include/hw/loongarch/virt.h |  10 ++--
>>   3 files changed, 107 insertions(+), 33 deletions(-)
>

[-- Attachment #2: Type: text/html, Size: 5722 bytes --]

  reply	other threads:[~2024-03-02  4:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 11:38 [PULL v2 0/1] loongarch-to-apply queue Song Gao
2024-02-29 11:38 ` [PULL v2 1/1] loongarch: Change the UEFI loading mode to loongarch Song Gao
2024-03-01 13:28   ` Philippe Mathieu-Daudé
2024-03-02  2:31     ` lixianglai [this message]
2024-03-06 14:56       ` chen huacai
2024-03-07  1:36         ` lixianglai
2024-03-01 14:38 ` [PULL v2 0/1] loongarch-to-apply queue Peter Maydell

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=5e2419ec-6c1f-e21c-2105-fadb5971239c@loongson.cn \
    --to=lixianglai@loongson.cn \
    --cc=abologna@redhat.com \
    --cc=gaosong@loongson.cn \
    --cc=maobibo@loongson.cn \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=zhaotianrui@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.