From: Adam Borowski <kilobyte@angband.pl>
To: "René Rebe" <rene@exactcode.com>
Cc: Nick Terrell <terrelln@fb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, x86@kernel.org, kernel-team@fb.com,
Chris Mason <clm@fb.com>,
Julian Andres Klode <julian.klode@canonical.com>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [RESEND PATCH v2 0/2] Add support for ZSTD-compressed kernel
Date: Thu, 22 Mar 2018 13:35:57 +0100 [thread overview]
Message-ID: <20180322123557.4eu4huhldqn6bid6@angband.pl> (raw)
In-Reply-To: <C0384AAE-FF89-4BAA-8EFC-FB3B0A8F02AB@exactcode.com>
On Thu, Mar 22, 2018 at 12:09:45PM +0100, René Rebe wrote:
> Should this currently just work without any arch change on e.g.
> ppc64, sparc64 et al.? I could do a test build and boot if that is
> of any value, ...
Initrd: no reason it wouldn't work, although for anything related to the
boot process testing is a very good idea. If you test, you'd really want to
apply that printk patch I posted, it's too easy to accidentally get a silent
fallback to gzip or uncompressed. I wonder, perhaps such a printk could be
permanently added, at a low message priority?
Kernel itself: needs per-arch porting, but it's not advertised in kconfig
outside x86 so that's not a problem.
If you are knowledgeful about bootloaders on ppc64, sparc64, etc, such
information would be great.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can.
⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener.
⠈⠳⣄⠀⠀⠀⠀ A master species delegates.
next prev parent reply other threads:[~2018-03-22 12:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180322012943.4145794-1-terrelln@fb.com>
2018-03-22 2:58 ` [RESEND PATCH v2 0/2] Add support for ZSTD-compressed kernel Adam Borowski
[not found] ` <C0384AAE-FF89-4BAA-8EFC-FB3B0A8F02AB@exactcode.com>
2018-03-22 12:35 ` Adam Borowski [this message]
2018-04-23 21:17 ` René Rebe
2018-07-09 18:04 ` Nick Terrell
2018-07-09 22:13 ` René Rebe
2018-08-17 16:15 ` René Rebe
2018-08-17 16:54 ` Andi Kleen
2018-08-17 17:15 ` René Rebe
2018-08-17 17:57 ` Adam Borowski
2018-08-17 19:22 ` Andi Kleen
2018-08-17 20:07 ` Adam Borowski
2018-08-28 2:36 ` Nick Terrell
[not found] ` <0ABE55AB-D29B-4E12-8E12-A9AFD6E39382@exactcode.com>
2019-06-07 19:20 ` Nick Terrell
2019-06-07 23:06 ` Adam Borowski
2019-06-10 18:40 ` Nick Terrell
2018-07-13 17:42 ` [PATCH] .gitignore: add ZSTD-compressed files Adam Borowski
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=20180322123557.4eu4huhldqn6bid6@angband.pl \
--to=kilobyte@angband.pl \
--cc=ak@linux.intel.com \
--cc=clm@fb.com \
--cc=hpa@zytor.com \
--cc=julian.klode@canonical.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rene@exactcode.com \
--cc=terrelln@fb.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).