From: Selvakumar Velandi <selvakumar.velandi@olakrutrim.com>
To: u-boot@lists.denx.de
Subject: [PATCH] Added FDT PAD memory size while reserving memory for FDT to avoid some memory corruption issue
Date: Fri, 9 Feb 2024 13:22:08 +0530 [thread overview]
Message-ID: <CAJ-dvqwMWvWw0=34ZLkG37MwTRG1m_tabSi0zLkoHNY8CjR_PQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
Hi,
Issue:
Linux kernel getting crash after loading kernel in VM system using RISCV
QEMU.
RootCause:
Memory corruption in uboot FDT memory while launching a VM system in RISCV
QEMU.
Fix:
In the board_f.c file the FDT memory region is reserved without FDT padding
bytes. uboot will add some params like bootargs while launching linux.
While relocate the FDT, if its decided as run in the Fixed memory location
i.e fdy_high is set as -1, then the padding bytes not added while
relocating the FDT,
but the size is blindly added with padding bytes without reserving the
physical memory in the FDT header in the image_fdt.c file.
Please find the attached patch file to fix the issue. Please review and
revert your comments.
Regards,
SelvakumarVelandi
Krutrim SI designs
--
***
This communication is confidential, may be privileged and is meant only
for the intended recipient and purpose. No part of this email or any files
transmitted with it can be shared, copied, forwarded or published online or
offline, without prior written consent of the sender. If you are not the
intended recipient, please preserve the confidentiality, delete the e-mail
and attachments, if any from your system and inform the sender immediately.
***
[-- Attachment #2: 0001-PATCH-RISCV-QEMU-Add-PAD-size-during-the-FDT-memory-.patch --]
[-- Type: application/x-patch, Size: 3051 bytes --]
next reply other threads:[~2024-02-09 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 7:52 Selvakumar Velandi [this message]
2024-02-09 13:40 ` [PATCH] Added FDT PAD memory size while reserving memory for FDT to avoid some memory corruption issue Tom Rini
2024-02-09 14:15 ` Selvakumar Velandi
2024-02-09 20:25 ` Tom Rini
2024-02-14 9:27 ` Selvakumar Velandi
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='CAJ-dvqwMWvWw0=34ZLkG37MwTRG1m_tabSi0zLkoHNY8CjR_PQ@mail.gmail.com' \
--to=selvakumar.velandi@olakrutrim.com \
--cc=u-boot@lists.denx.de \
/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).