From: "H. Peter Anvin" <hpa@zytor.com>
To: Thomas Renninger <trenn@suse.de>
Cc: linux-kernel@vger.kernel.org, lenb@kernel.org,
robert.moore@intel.com, Fenghua Yu <fenghua.yu@intel.com>,
initramfs@vger.kernel.org, bigeasy@linutronix.de, vojcek@tlen.pl,
eric.piel@tremplin-utc.net, linux-acpi@vger.kernel.org,
yinghai@kernel.org, "H. Peter Anvin" <hpa@linux.intel.com>
Subject: Re: [PATCH 1/2] lib: Add early cpio decoder
Date: Tue, 04 Sep 2012 10:00:09 -0700 [thread overview]
Message-ID: <50463399.70506@zytor.com> (raw)
In-Reply-To: <1346318957-5831-2-git-send-email-trenn@suse.de>
On 08/30/2012 02:29 AM, Thomas Renninger wrote:
> From: "H. Peter Anvin" <hpa@linux.intel.com>
>
> Add a simple cpio decoder without library dependencies for the purpose
> of extracting components from the initramfs blob for early kernel
> uses. Intended consumers so far are microcode and ACPI override.
>
> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
> CC: Thomas Renninger <trenn@suse.de>
> Link: http://lkml.kernel.org/r/201203261651.29640.trenn@suse.de
> Signed-off-by: Thomas Renninger <trenn@suse.de>
I was trying to figure out if there is a way to do what you want
(support for multiple files) without the problems of the callback
interface. I think it is actually fairly straightforward; we need a
prefix iterator (so you can give it a string like "kernel/acpi/" rather
than a full filename) and it needs to be able to accept a "last" pointer
so it can resume scanning at the point it last left off. That should be
a pretty trivial change.
The other thing we presumably want to do -- and this is generic -- is to
be able to handle multiple sources for the initramfs; at the very least
there is built in vs provided from the boot loader. I had originally
intended to just handle that by calling the earlycpio function once per
block, but the "last left off" bit makes that a little harder. Need to
think about that a little bit.
I am guessing that this may not need to be something we need from the
very beginning, or am I wrong?
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-09-04 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 9:29 Early cpio decoder and ACPI table override via initrd making use of it Thomas Renninger
2012-08-30 9:29 ` [PATCH 1/2] lib: Add early cpio decoder Thomas Renninger
2012-09-04 17:00 ` H. Peter Anvin [this message]
2012-09-21 12:51 ` Thomas Renninger
2012-09-25 3:47 ` H. Peter Anvin
2012-08-30 9:29 ` [PATCH 2/2] ACPI: Override arbitrary ACPI tables via initrd for debugging Thomas Renninger
2012-08-30 9:34 ` Thomas Renninger
2012-09-21 13:28 Early cpio decoder and ACPI table override via initrd making use of it Thomas Renninger
2012-09-21 13:28 ` [PATCH 1/2] lib: Add early cpio decoder Thomas Renninger
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=50463399.70506@zytor.com \
--to=hpa@zytor.com \
--cc=bigeasy@linutronix.de \
--cc=eric.piel@tremplin-utc.net \
--cc=fenghua.yu@intel.com \
--cc=hpa@linux.intel.com \
--cc=initramfs@vger.kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.moore@intel.com \
--cc=trenn@suse.de \
--cc=vojcek@tlen.pl \
--cc=yinghai@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).