From: Jacob Moody <moody@posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] qemu kernel for arm64, detected memory
Date: Sun, 7 Jan 2024 08:23:40 -0600 [thread overview]
Message-ID: <6479cfe7-95ee-4f75-ba98-a3ff48879b61@posixcafe.org> (raw)
In-Reply-To: <515bcf9c-352e-4f2b-b0d9-86c26171fa8f@cosarara.me>
On 1/7/24 06:07, cosarara wrote:
> Running 9front on qemu-system-aarch64 (trying to follow the directions in commit dd79854239a8c):
>
> qemu-system-aarch64 -M virt-2.12,gic-version=3 \
> -cpu cortex-a57 -m 4G -smp 4 \
> -bios u-boot/u-boot.bin \
> -drive file=9front-10277.arm64.qcow2,if=none,id=disk \
> -device virtio-blk-pci-non-transitional,drive=disk \
> -nographic
>
> u-boot correctly reports:
>
>> DRAM: 4 GiB
>
> But then plan9:
>
>> ## Transferring control to Plan 9 (at address 40100000) ...
>> 127 holes free
>> 0x404c4000 0x429bd000 38768640
>> 38768640 bytes free
>>
>> Plan 9
>> timer frequency 62500000 Hz
>> cpu0: 1000MHz QEMU
>> 127M memory: 41M kernel data, 86M user, 455M swap
>> [...]
>> cirno# cat /dev/swap
>> 129220608 memory
>> 4096 pagesize
>> 9465 kernel
>> 2993/22083 user
>> 0/94644 swap
>> 1556/22083 reclaim
>> 1816176/1966560/36545820 kernel malloc
>> 0/0/36545820 kernel draw
>> 768/65568/16777216 kernel secret
>
> So it seems it does not detect the full amount. I don't know if this is a know bug in the kernel.
>
>
>
This is a known issue. You can set *maxmem in plan9.ini to get it to use more memory.
Thanks,
moody
next prev parent reply other threads:[~2024-01-07 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 12:07 cosarara
2024-01-07 14:23 ` Jacob Moody [this message]
2024-01-07 15:47 ` cosarara
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=6479cfe7-95ee-4f75-ba98-a3ff48879b61@posixcafe.org \
--to=moody@posixcafe.org \
--cc=9front@9front.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 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).