Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp324285ybb; Wed, 1 Apr 2020 00:19:39 -0700 (PDT) X-Google-Smtp-Source: APiQypJ6vR5ZBvDmmOKD0swN/fhAZvMFBfBnwtKJHdjjRIRyPnBpy3T4SmG9PqqVq/e9q0s1s1ou X-Received: by 2002:aca:4d49:: with SMTP id a70mr1936893oib.152.1585725578962; Wed, 01 Apr 2020 00:19:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585725578; cv=none; d=google.com; s=arc-20160816; b=j/vHPyfVUPfBwAqR7k0EmdWciQqhM1Vu1uTtL/7P4VMxHUjIaeVHQKeOHb4VJJEJf6 pLTLRevmzIU0t9s3Cv4AYnje5F2VqHoZi4Hv6jTUeMFwirz2eplHCzGXNt2dkOt6Bxec zIELillNBJHJ9bRxsDpEkM6eseu/xYpJj//dQspudH0SSIo2KXhVARIzk9uAEMV1j50/ 8ye5HwFc+ylcFcjWHKSnu29OW787L0IDsYq9nejfneaAtTtG0R3r6FK5e8osbzZOyjbn AAPyG8mC3t7tvIOGzWCwRzSWYzTpyrj0As2JbATLsPamm6ds+luew+NeVNPodGYi35+x Bwww== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=iDzu2ug5dmFZy8CmBXaolDeUPm4BNekaQ1mdu3paPhw=; b=iQA9fKDzmlN9OnhRdJSj3VwsUukEJs40mXEv4nkwz73A6IcOMQAk4FQE17ziv0WfaX /6bd4u+rGYOwdI8dZA2+MNjafSgFG16Q7O0IRgRnEWDF58gbjRFkALDW0+bsdjD3Y0hW jVctPCmTyyuzgaREa35yqXtgEHCVlaDeZ+CJ4dZQ31rDm7t10zS4DizPCoYQYVG9/Xzn 3+XOGklyDzQnV6srmFflruzl1TM7AJZm1sYe2bO43ocInoaimn6CbgCZaJ2sfJwfjF7j C0lKM+Ybb/fyQLYNsJGtsulJY1at7dvrWORU0Er/WqTsszmFYQEFlTo7ETPgWoRXgugA XP6A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y139si512382ooa.14.2020.04.01.00.19.26; Wed, 01 Apr 2020 00:19:38 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731968AbgDAHSW (ORCPT + 99 others); Wed, 1 Apr 2020 03:18:22 -0400 Received: from tartarus.angband.pl ([54.37.238.230]:45160 "EHLO tartarus.angband.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731680AbgDAHSW (ORCPT ); Wed, 1 Apr 2020 03:18:22 -0400 Received: from kilobyte by tartarus.angband.pl with local (Exim 4.92) (envelope-from ) id 1jJXdf-0008SI-Nb; Wed, 01 Apr 2020 09:18:15 +0200 Date: Wed, 1 Apr 2020 09:18:15 +0200 From: Adam Borowski To: Sedat Dilek Cc: Nick Terrell , Nick Terrell , "linux-kernel@vger.kernel.org" , Chris Mason , "linux-kbuild@vger.kernel.org" , "x86@kernel.org" , "gregkh@linuxfoundation.org" , Petr Malat , Kees Cook , Kernel Team , Patrick Williams , Michael van der Westhuizen , "mingo@kernel.org" , Patrick Williams , Nick Desaulniers Subject: Re: [PATCH v3 0/8] Add support for ZSTD-compressed kernel and initramfs Message-ID: <20200401071815.GA27371@angband.pl> References: <1A630698-E385-4CDF-9755-ACDAAF60DBB9@fb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Junkbait: aaron@angband.pl, zzyx@angband.pl User-Agent: Mutt/1.10.1 (2018-07-13) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: kilobyte@angband.pl X-SA-Exim-Scanned: No (on tartarus.angband.pl); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 31, 2020 at 05:11:35PM +0200, Sedat Dilek wrote: > I have re-tested zstd-v3 patchset with Linux version 5.6 final and > Clang/LLD version 10.0.0 final (from Debian/unstable repository). So did I and a bunch of other folks. I for one run v1 since 2017 on a bunch of boxes (amd64/BIOS, amd64/EFI, arm64, armhf), without a glitch (not counting trying to boot zstd initrd _without_ the patchset :p). I've tried v2 on all of the above configurations, v3 on all but armhf, v4 on amd64/EFI -- all is fine. Back in the days, folks reported success on IIRC ppc64, sparc64 and more. (Obviously, initrd only on !x86.) > Is it possible to mention that there might distro-specific changes > needed to initramfs-handling? > For Debian you are welcome to include below Link [1]. > [1] LINK: https://lore.kernel.org/lkml/CA+icZUXCn2an9aNDrm+-eneSAOyGibz0W1xYhwkA5k3B3U-5vQ@mail.gmail.com/ +zstd) compress="zstd -19 -v" ;; I'm not sure if hard-coding -19 is always right. It's good for production machines but slows down dev cycles. But that's a matter for userland, not a problem with Nick's patchset. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good. ⢿⡄⠘⠷⠚⠋⠀ -- on #linux-sunxi ⠈⠳⣄⠀⠀⠀⠀