Re: [External] : Re: [PATCH] Documentation/arm64: update memory layout table.

From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Andre Mueller <am@emlix.com>, Will Deacon <will@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [External] : Re: [PATCH] Documentation/arm64: update memory layout table.
Date: Tue, 21 Jun 2022 19:06:21 +0100	[thread overview]
Message-ID: <YrIIna6lqruS/Wcc@shell.armlinux.org.uk> (raw)
In-Reply-To: <YrH+/YyvPL5c/+zS@arm.com>

On Tue, Jun 21, 2022 at 06:25:17PM +0100, Catalin Marinas wrote:
> On Tue, Jun 21, 2022 at 02:47:30PM +0000, Russell King wrote:
> > From: Catalin Marinas <catalin.marinas@arm.com>
> > I've found the table particularly useful when wanting to know the
> > virtual address space layout, so it does seem to have some value.
> 
> Yes but that's only one of the configurations and it keeps getting out
> of sync. We used to print the information at boot until commit
> 071929dbdd86 ("arm64: Stop printing the virtual memory layout"). I think
> we could bring some of that back, maybe even behind a debug command line
> option or config (or expose it via sysfs). We shouldn't print the info
> that has security implications like where stext is mapped or anything
> randomised, only the rough layout like in the doc.

Sounds like a good idea - if there's a way to come up with it
programatically, then it's going to have a better chance of remaining
accurate.

> > (Replying from my work email as that's where it's been sent. Can't do
> > anything but top-post, which is why I use my armlinux.org.uk email for
> > kernel stuff - thanks Outlook web.)
> 
> As a side-note, Arm uses outlook as well but mutt can connect via IMAP
> (if enabled; a bit of a pain with oauth2). For SMTP I use the kernel.org
> one since outlook tends to corrupt patches.

I've tried neomutt + oauth2 over a few weeks... and with the gpg
splatting over the top of neomutt's output and the problems if you
don't notice the splatting and respond in time... yea, I gave up with
it, it was _way_ more hassle than using Outlook's web interface. It's
probably fine if all you're doing is monitoring email and nothing else.

I never thought I'd say that Outlook is better than neomutt, but in
this instance, Outlook web takes several orders of magnitude less user
maintenance than neomutt does. Neomutt + oauth2 is just way too
painful, even with the Outlook web quirks such as only supporting
top-post replying.

I guess that neomutt + oauth2 might be fine if you check email just
once a day, but not if you want to monitor email throughout the day.

-- 
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