All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hang Xu <xuhang@eswincomputing.com>
To: qemu-riscv@nongnu.org
Cc: qemu-devel@nongnu.org, palmer@rivosinc.com,
	dbarboza@ventanamicro.com, alistair.francis@wdc.com,
	Hang Xu <xuhang@eswincomputing.com>
Subject: [PATCH v3 0/1] Fix max initrd size limit when put initrd to RAM
Date: Mon, 13 Mar 2023 02:18:25 +0000	[thread overview]
Message-ID: <20230313021826.6898-1-xuhang@eswincomputing.com> (raw)

Because the starting address of ram is not necessarily 0,
the remaining free space in ram is
ram_size - (start - ram_base) instead of ram_size-start.

v3:
* Declare 'max_initrd' at the start of the function
* Fix title typo

v2:
* Rebase
* Considering that the ram block may be discontinuous

Hang Xu (1):
  hw/riscv: Fix max size limit when put initrd to RAM

 hw/riscv/boot.c            | 19 +++++++++++++------
 hw/riscv/microchip_pfsoc.c |  5 ++++-
 hw/riscv/opentitan.c       |  2 +-
 hw/riscv/sifive_e.c        |  2 +-
 hw/riscv/sifive_u.c        |  5 ++++-
 hw/riscv/spike.c           |  5 ++++-
 hw/riscv/virt.c            |  5 ++++-
 include/hw/riscv/boot.h    |  2 ++
 8 files changed, 33 insertions(+), 12 deletions(-)

-- 
2.17.1



             reply	other threads:[~2023-03-13  2:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13  2:18 Hang Xu [this message]
2023-03-13  2:18 ` [PATCH v3 1/1] hw/riscv: Fix max size limit when put initrd to RAM Hang Xu
2023-03-13 12:29   ` Daniel Henrique Barboza
2023-03-13 15:49   ` Anup Patel
2023-03-13 21:32     ` Daniel Henrique Barboza
2023-04-05  5:53   ` Alistair Francis
2023-04-05  9:38     ` Daniel Henrique Barboza
2023-04-07  4:26     ` Hang Xu

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=20230313021826.6898-1-xuhang@eswincomputing.com \
    --to=xuhang@eswincomputing.com \
    --cc=alistair.francis@wdc.com \
    --cc=dbarboza@ventanamicro.com \
    --cc=palmer@rivosinc.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    /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.