From: Mohd Yusuf Abdul Hamid <mohdyusuf@gmail.com>
To: Gavin Shan <gshan@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: QEMU virt (arm64) does not honor reserved-memory set in device tree
Date: Thu, 15 Jun 2023 13:59:42 -0700 [thread overview]
Message-ID: <CALKsAjAKFCgihYc-c3p7Fka3gE58bFqQ00xnAW5RYd4tbVs6rQ@mail.gmail.com> (raw)
In-Reply-To: <cfc21135-0f27-8af5-c864-d969dd42e4c0@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
Hi Gavin,
Thanks for the reply. I am new to Linux dev in general and not familiar
with the ACPI table, but I will research in the area and give it a try.
Sorry for the late response.
-Yusuf
On Fri, Jun 9, 2023, 8:36 PM Gavin Shan <gshan@redhat.com> wrote:
> Hi Mohd,
>
> On 6/10/23 10:01 AM, Mohd Yusuf Abdul Hamid wrote:
> > I am trying to reserve a portion of the system memory in QEMU (arm64
> virt), v7.2.1 - but the kernel never honors the reserved memory area and
> keeps using the area.
> >
> > Say, I dumped out DTB and added:
> >
> > reserved-memory {
> > #address-cells = <0x02>;
> > #size-cells = <0x02>;
> >
> > rsvdram@50000000 {
> > no-map;
> > reg = <0x00 0x50000000 0x00 0x20000000>;
> > };
> > };
> >
> > When booted, /proc/iomem still shows the kernel is using the entire
> space - eg 2GB.
> >
> > Is this a supported feature or I would need to modify the virt.c and
> define scratch area for some device driver scratch area.
> >
>
> It relies on the guest kernel to handle the device-tree and the
> device-tree node
> for the reserved map. I doubt if you had ACPI over device-tree in the
> guest kernel's
> configuration. In this case, the reserved memory regions need to be
> specified in
> ACPI tables instead of device-tree.
>
> Thanks,
> Gavin
>
>
[-- Attachment #2: Type: text/html, Size: 1901 bytes --]
prev parent reply other threads:[~2023-06-15 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-10 0:01 QEMU virt (arm64) does not honor reserved-memory set in device tree Mohd Yusuf Abdul Hamid
2023-06-10 3:36 ` Gavin Shan
2023-06-15 20:59 ` Mohd Yusuf Abdul Hamid [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=CALKsAjAKFCgihYc-c3p7Fka3gE58bFqQ00xnAW5RYd4tbVs6rQ@mail.gmail.com \
--to=mohdyusuf@gmail.com \
--cc=gshan@redhat.com \
--cc=qemu-devel@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 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).