From: Laszlo Ersek <lersek@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"haibinzhang(张海斌)" <haibinzhang@tencent.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>
Cc: Leif Lindholm <leif@nuviainc.com>,
Ard Biesheuvel <Ard.Biesheuvel@arm.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH] hw/arm/virt: use pflash image real size when mapping
Date: Tue, 22 Sep 2020 08:57:17 +0200 [thread overview]
Message-ID: <db1e1feb-aef0-e8c4-429b-61586106edec@redhat.com> (raw)
In-Reply-To: <52eb89e8-3602-2a2a-df9e-66130bce4070@redhat.com>
On 09/18/20 15:41, Philippe Mathieu-Daudé wrote:
> Cc'ing firmware experts.
>
> On 9/18/20 2:26 PM, haibinzhang(寮犳捣鏂�) wrote:
>> Default size of arm-virt pflash image is 64MB which
>> will cost extra 128MB(64MBx2) memory per qemu process
>> and 12.5GB for 100 qemu processes. Host memory is
>> precious and it is valuable to reduce pflash image size.
>> For compatibility arm-virt uses real size when mapping.
>
> Flash#0 is a device because eventually its model will handle
> sector/block protection, so firmware can do CapsuleUpdate
> (updating itself). Meanwhile you could treat flash#0 as a pure
> ROM device... But this wouldn't be the 'arm-virt' machine anymore.
>
>>
>> Signed-off-by: Haibin Zhang <haibinzhang@tencent.com>
>> ---
>> hw/arm/virt.c | 22 ++++++++++++++++++++--
>> 1 file changed, 20 insertions(+), 2 deletions(-)
>>
>> diff --git a/hw/arm/virt.c b/hw/arm/virt.c
>> index acf9bfbece..3545e12865 100644
>> --- a/hw/arm/virt.c
>> +++ b/hw/arm/virt.c
>> @@ -50,6 +50,7 @@
>> #include "sysemu/sysemu.h"
>> #include "sysemu/tpm.h"
>> #include "sysemu/kvm.h"
>> +#include "sysemu/block-backend.h"
>> #include "hw/loader.h"
>> #include "exec/address-spaces.h"
>> #include "qemu/bitops.h"
>> @@ -1001,10 +1002,27 @@ static void virt_flash_map(VirtMachineState *vms,
>> */
>> hwaddr flashsize = vms->memmap[VIRT_FLASH].size / 2;
>> hwaddr flashbase = vms->memmap[VIRT_FLASH].base;
>> + int64_t realsize;
>> + BlockBackend *blk;
>>
>> - virt_flash_map1(vms->flash[0], flashbase, flashsize,
>> + realsize = flashsize;
>> + blk = pflash_cfi01_get_blk(vms->flash[0]);
>> + if (blk) {
>> + realsize = blk_getlength(blk);
>> + realsize = realsize < flashsize ? realsize : flashsize;
>> + }
>
> Stefan recently posted "nvdimm: read-only file support" which
> might be a better way to achieve what you want:
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg741137.html
>
>> +
>> + virt_flash_map1(vms->flash[0], flashbase, realsize,
>> secure_sysmem);
>> - virt_flash_map1(vms->flash[1], flashbase + flashsize, flashsize,
>> +
>> + realsize = flashsize;
>> + blk = pflash_cfi01_get_blk(vms->flash[1]);
>> + if (blk) {
>> + realsize = blk_getlength(blk);
>> + realsize = realsize < flashsize ? realsize : flashsize;
>> + }
>> +
>> + virt_flash_map1(vms->flash[1], flashbase + flashsize, realsize,
>> sysmem);
>> }
>>
>> --
>> 2.23.0
>>
>
We've been here before.
[Qemu-devel] [RFC PATCH] hw/arm/virt: use variable size of flash device to save memory
https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg06773.html
http://mid.mail-archive.com/20190325125142.11628-1-zhengxiang9@huawei.com
I don't have anything to add.
Laszlo
next prev parent reply other threads:[~2020-09-22 7:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 12:26 [PATCH] hw/arm/virt: use pflash image real size when mapping haibinzhang(张海斌)
2020-09-18 13:41 ` Philippe Mathieu-Daudé
2020-09-19 10:03 ` haibinzhang(张海斌)
2020-09-21 5:34 ` haibinzhang(张海斌)
2020-09-22 6:57 ` Laszlo Ersek [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-18 12:21 haibinzhang(张海斌)
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=db1e1feb-aef0-e8c4-429b-61586106edec@redhat.com \
--to=lersek@redhat.com \
--cc=Ard.Biesheuvel@arm.com \
--cc=haibinzhang@tencent.com \
--cc=leif@nuviainc.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).