public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Thomas Renninger <trenn@suse.de>,
	eric.piel@tremplin-utc.net, vojcek@tlen.pl, dsdt@gaugusch.at,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	x86@kernel.org, Lin Ming <ming.m.lin@intel.com>,
	lenb@kernel.org, robert.moore@intel.com,
	Al Viro <viro@zeniv.linux.org.uk>,
	Harald Hoyer <harald@redhat.com>, Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH] ACPI: Implement overriding of arbitrary ACPI tables via initrd
Date: Sat, 24 Mar 2012 21:17:21 -0700	[thread overview]
Message-ID: <4F6E9C51.9000406@zytor.com> (raw)
In-Reply-To: <4F6E48CD.9050002@zytor.com>

On 03/24/2012 03:21 PM, H. Peter Anvin wrote:
> The attached cpio-parsing code compiles to 458 bytes on x86-64 and 476
> bytes on i386, and that is without any library dependencies at all.
> Again, it will completely stop at the first compressed data item, so any
> such kernel objects absolutely will have to be first.  In good Linux
> tradition, it is also completely untested.
> 
> However, given that very reasonable size I would think that this is a
> reasonable approach.  Anyone who has a better suggestion for the
> namespace than "kernel/"?
> 

The more I think about it the more I really think this is the right
approach.  For microcode, this means we don't have to worry about
creating a super-container for the various microcode formats; we can
simply have:

	kernel/x86/microcode/GenuineIntel
	kernel/x86/microcode/AuthenticAMD

... which solves the problem neatly.

It does beg the question if you want to be able to have multiple:

	kernel/acpi/...

... files, to make managing different tables easier, or is that overkill?

	-hpa


  parent reply	other threads:[~2012-03-25  4:18 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23 14:29 [PATCH] ACPI: Implement overriding of arbitrary ACPI tables via initrd Thomas Renninger
2012-03-23 15:51 ` Thomas Renninger
2012-03-23 20:05 ` H. Peter Anvin
2012-03-24  1:42   ` Thomas Renninger
2012-03-24  2:01     ` H. Peter Anvin
2012-03-24  3:02       ` Thomas Renninger
2012-03-24  4:40         ` H. Peter Anvin
2012-03-24  4:43         ` H. Peter Anvin
2012-03-24  4:50           ` Yinghai Lu
2012-03-24  4:58             ` H. Peter Anvin
2012-03-24  9:24           ` Borislav Petkov
2012-03-24 18:49             ` H. Peter Anvin
2012-03-25  8:54               ` Borislav Petkov
2012-03-26  1:36                 ` H. Peter Anvin
2012-03-26 14:21                   ` Konrad Rzeszutek Wilk
2012-03-26  0:45           ` Thomas Renninger
2012-03-26  1:25             ` H. Peter Anvin
2012-03-26 14:19               ` Thomas Renninger
2012-03-26 14:46                 ` H. Peter Anvin
2012-03-26 14:51                   ` Thomas Renninger
2012-03-27  4:15                     ` H. Peter Anvin
2012-03-27  4:46               ` Peter Stuge
2012-03-27  6:18                 ` H. Peter Anvin
2012-03-24 18:42       ` Konrad Rzeszutek Wilk
2012-03-24 19:15         ` H. Peter Anvin
2012-03-24 19:17           ` Konrad Rzeszutek Wilk
2012-03-24 19:44             ` H. Peter Anvin
2012-03-24 22:21             ` H. Peter Anvin
2012-03-24 22:44               ` H. Peter Anvin
2012-03-25  9:25                 ` Borislav Petkov
2012-03-25 23:29                   ` H. Peter Anvin
2012-03-25  4:17               ` H. Peter Anvin [this message]
2012-03-25  9:07                 ` Borislav Petkov
2012-03-23 20:54 ` Yinghai Lu
2012-03-24  0:15   ` Yinghai Lu
2012-03-24  1:05   ` Yinghai Lu
2012-03-24  1:22     ` Thomas Renninger
2012-03-24  1:26   ` Thomas Renninger
2012-03-24  4:41     ` Yinghai Lu
2012-03-26  0:45       ` 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=4F6E9C51.9000406@zytor.com \
    --to=hpa@zytor.com \
    --cc=bp@alien8.de \
    --cc=dsdt@gaugusch.at \
    --cc=eric.piel@tremplin-utc.net \
    --cc=harald@redhat.com \
    --cc=konrad.wilk@oracle.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.m.lin@intel.com \
    --cc=robert.moore@intel.com \
    --cc=trenn@suse.de \
    --cc=viro@zeniv.linux.org.uk \
    --cc=vojcek@tlen.pl \
    --cc=x86@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