From: "Li, Yong" <yong.li@intel.com>
To: Alistair Francis <alistair23@gmail.com>
Cc: <qemu-devel@nongnu.org>,
Zhiwei Liu <zhiwei_liu@linux.alibaba.com>,
<sunilvl@ventanamicro.com>
Subject: Re: [PATCH] hw/riscv/virt: Fix the boot logic if pflash0 is specified
Date: Wed, 17 May 2023 15:54:05 +0800 [thread overview]
Message-ID: <19340505-1996-f2e5-bce4-cdf20c96830a@intel.com> (raw)
In-Reply-To: <CAKmqyKM09A-dCjrF+UJh_jQyTVjG7X3RPiXLXn-qy+Of-+Zg3Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1864 bytes --]
On 2023/5/17 10:27, Alistair Francis wrote:
> On Sun, Apr 23, 2023 at 11:39 PM Yong Li<yong.li@intel.com> wrote:
>> The firmware may be specified with -bios
>> and the plfash0 device with option -drive if=pflash.
>> If both options are applied, it is intented that the pflash0 will
>> store the secure variable and the firmware be the one specified
>> by -bios. Explicitly specify "-bios none" if choose to boot from
>> pflash0
> This seems like the right approach.
>
> Can you update the docs/system/riscv/virt.rst docs to include this information?
>
> Alistair
Hi Alistair
Thanks for your review, after syncing with Sunil from ventena team.
Sunil is also working with for thishttps://www.mail-archive.com/qemu-devel@nongnu.org/msg959882.html,
and he will handle this change in his patch. Thanks
>> Signed-off-by: Yong Li<yong.li@intel.com>
>> Cc: "Zhiwei Liu"<zhiwei_liu@linux.alibaba.com>
>> ---
>> hw/riscv/virt.c | 8 +++++---
>> 1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/hw/riscv/virt.c b/hw/riscv/virt.c
>> index 4e3efbee16..b38b41e685 100644
>> --- a/hw/riscv/virt.c
>> +++ b/hw/riscv/virt.c
>> @@ -1296,10 +1296,12 @@ static void virt_machine_done(Notifier *notifier, void *data)
>> kernel_entry = 0;
>> }
>>
>> - if (drive_get(IF_PFLASH, 0, 0)) {
>> + if (drive_get(IF_PFLASH, 0, 0) &&
>> + !strcmp(machine->firmware, "none")) {
>> /*
>> - * Pflash was supplied, let's overwrite the address we jump to after
>> - * reset to the base of the flash.
>> + * If pflash (unit 0) was supplied and at the same time the -bois
>> + * is not specified, then let's overwrite the address we jump to
>> + * after reset to the base of the flash.
>> */
>> start_addr = virt_memmap[VIRT_FLASH].base;
>> }
>> --
>> 2.25.1
>>
>>
[-- Attachment #2: Type: text/html, Size: 2955 bytes --]
prev parent reply other threads:[~2023-05-17 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-23 9:59 [PATCH] hw/riscv/virt: Fix the boot logic if pflash0 is specified Yong Li
2023-05-17 2:27 ` Alistair Francis
2023-05-17 7:54 ` Li, Yong [this message]
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=19340505-1996-f2e5-bce4-cdf20c96830a@intel.com \
--to=yong.li@intel.com \
--cc=alistair23@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=sunilvl@ventanamicro.com \
--cc=zhiwei_liu@linux.alibaba.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).