mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Graf <graf@amazon.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Jan H.Schönherr" <jschoenh@amazon.de>,
	"James Gowans" <jgowans@amazon.com>
Subject: Re: [PATCH] initramfs: Expose retained initrd as sysfs file
Date: Wed, 6 Dec 2023 22:29:30 +0100	[thread overview]
Message-ID: <1ab3656e-bfed-441a-aa8c-c3bd816303e1@amazon.com> (raw)
In-Reply-To: <20231206120020.215a51251cba5a2c4fa51df2@linux-foundation.org>


On 06.12.23 21:00, Andrew Morton wrote:
> On Wed, 6 Dec 2023 14:16:27 +0000 Alexander Graf <graf@amazon.com> wrote:
>
>> When the kernel command line option "retain_initrd" is set, we do not
>> free the initrd memory. However, we also don't expose it to anyone for
>> consumption. That leaves us in a weird situation where the only user of
>> this feature is ppc64 and arm64 specific kexec tooling.
>>
>> To make it more generally useful, this patch adds a kobject to the
>> firmware object that contains the initrd context when "retain_initrd"
>> is set. That way, we can access the initrd any time after boot from
>> user space and for example hand it into kexec as --initrd parameter
>> if we want to reboot the same initrd. Or inspect it directly locally.
> I think it would be helpful if the changelog were mention and describe
> the new /sys/firmware/initrd.  And I assume we should add a
> Documentation/ABI/testing/sysfs-firmware-initrd.


Thanks a bunch for the suggestions - let me send v2 with both addressed :)

Alex




Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879



      parent reply	other threads:[~2023-12-06 21:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 14:16 Alexander Graf
     [not found] ` <20231206120020.215a51251cba5a2c4fa51df2@linux-foundation.org>
2023-12-06 21:29   ` Alexander Graf [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=1ab3656e-bfed-441a-aa8c-c3bd816303e1@amazon.com \
    --to=graf@amazon.com \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jgowans@amazon.com \
    --cc=jschoenh@amazon.de \
    --cc=linux-doc@vger.kernel.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

all inboxes | Powered by JetHome®