From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Jungseung Lee <js07.lee@samsung.com>
Cc: linus.walleij@linaro.org, amit.kachhap@arm.com, ardb@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, keescook@chromium.org,
js07.lee@gmail.com
Subject: Re: [PATCH 2/2] arm/mm : Report actual image regions in /proc/iomem
Date: Mon, 6 Mar 2023 12:28:36 +0000 [thread overview]
Message-ID: <ZAXcdDBiQ9JVo4pY@shell.armlinux.org.uk> (raw)
In-Reply-To: <076401d95025$305fb150$911f13f0$@samsung.com>
On Mon, Mar 06, 2023 at 09:14:23PM +0900, Jungseung Lee wrote:
> Hi, Russell
>
> > -----Original Message-----
> > From: Russell King (Oracle) <linux@armlinux.org.uk>
> > Sent: Monday, March 6, 2023 8:10 PM
> > To: Jungseung Lee <js07.lee@samsung.com>
> > Cc: linus.walleij@linaro.org; amit.kachhap@arm.com; ardb@kernel.org;
> > linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
> > keescook@chromium.org; js07.lee@gmail.com
> > Subject: Re: [PATCH 2/2] arm/mm : Report actual image regions in
> > /proc/iomem
> >
> > On Mon, Mar 06, 2023 at 02:51:55PM +0900, Jungseung Lee wrote:
> > > The resource reservations in /proc/iomem made for the kernel image
> > > did not reflect the gaps between text, rodata, and data.
> > > Add the "rodata" resource and update the start/end calculations.
> > >
> > > Before :
> > > 04000000-2f7fffff : System RAM
> > > 04100000-04cfffff : Kernel code
> > > 04e00000-05369a27 : Kernel data
> > >
> > > After :
> > > 04000000-2f7fffff : System RAM
> > > 04100000-049fffff : Kernel code
> > > 04a00000-04cb2fff : Kernel rodata
> > > 04e00000-05369a27 : Kernel data
> >
> > NAK. This is API, and programs do read and parse this file. It is
> > important that this file reports these parameters in a similar way to
> > other architectures. Other architectures do not split up the
> > individual regions.
> >
>
> Sounds like an important point, but I failed to find which programs use it
> as an API. Could you tell me which program uses it as an API?
>
> In fact, x86 architecture also split up the individual regions in this way.
> In addition, most architectures separate the "Kernel bss" area, but arm does
> not.
Take a look at kexec-tools - that certainly does parse /proc/iomem
looking for entries such as "Kernel code" and "Kernel data".
It's fine for an architecture to decide to do something else if it
started to do it early on, but not when something has been established
for decades.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-03-06 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230306061055epcas1p1f7718c46c10f84845e086f9ce9f9a41f@epcas1p1.samsung.com>
2023-03-06 5:51 ` [PATCH 1/2] arm/mm : omit [_text, _stext) from kernel code region Jungseung Lee
2023-03-06 5:51 ` [PATCH 2/2] arm/mm : Report actual image regions in /proc/iomem Jungseung Lee
2023-03-06 11:10 ` Russell King (Oracle)
2023-03-06 12:14 ` Jungseung Lee
2023-03-06 12:28 ` Russell King (Oracle) [this message]
2023-03-06 13:00 ` Ard Biesheuvel
2023-03-06 11:06 ` [PATCH 1/2] arm/mm : omit [_text, _stext) from kernel code region Russell King (Oracle)
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=ZAXcdDBiQ9JVo4pY@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=amit.kachhap@arm.com \
--cc=ardb@kernel.org \
--cc=js07.lee@gmail.com \
--cc=js07.lee@samsung.com \
--cc=keescook@chromium.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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).