From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:38440) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h3KXY-0000hE-HM for qemu-devel@nongnu.org; Mon, 11 Mar 2019 09:00:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h3KXW-0007yV-5m for qemu-devel@nongnu.org; Mon, 11 Mar 2019 09:00:24 -0400 Received: from mx1.redhat.com ([209.132.183.28]:34338) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1h3KXV-0007y0-Rs for qemu-devel@nongnu.org; Mon, 11 Mar 2019 09:00:22 -0400 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 11C03C05E77B for ; Mon, 11 Mar 2019 13:00:21 +0000 (UTC) Date: Mon, 11 Mar 2019 13:00:00 +0000 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Message-ID: <20190311130000.GW12393@redhat.com> Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= References: <20190309004826.9027-1-lersek@redhat.com> <20190311102801.GM12393@redhat.com> <20190311085449-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190311085449-mutt-send-email-mst@kernel.org> Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH 00/10] bundle edk2 platform firmware with QEMU List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Philippe =?utf-8?Q?Mathieu-Daud=C3=A9?= , Laszlo Ersek , imammedo@redhat.com, kraxel@redhat.com, qemu-devel@nongnu.org On Mon, Mar 11, 2019 at 08:57:04AM -0400, Michael S. Tsirkin wrote: > On Mon, Mar 11, 2019 at 10:28:01AM +0000, Daniel P. Berrang=C3=A9 wrote= : > > On Sat, Mar 09, 2019 at 02:20:06AM +0100, Philippe Mathieu-Daud=C3=A9= wrote: > > > On 3/9/19 1:48 AM, Laszlo Ersek wrote: > > > > Repo: https://github.com/lersek/qemu.git > > > > Branch: edk2_build > > > >=20 > > > > This series advances the roms/edk2 submodule to the "edk2-stable2= 01903" > > > > release, and builds and captures platform firmware binaries from = that > > > > release. At this point they are meant to be used by both end-user= s and > > > > by Igor's ACPI unit tests in qtest ("make check"). > > > >=20 > > > > Previous discussion: > > > >=20 > > > > [Qemu-devel] bundling edk2 platform firmware images with QEMU > > > > http://mid.mail-archive.com/80f0bae3-e79a-bb68-04c4-1c9c684d95b= 8@redhat.com > > > > https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg02601.= html > > > >=20 > > > > Note that the series was formatted with "--no-binary" (affecting = patch > > > > #8), therefore it cannot be applied with "git-am". See the remote > > > > repo/branch reference near the top instead. > > > >=20 > > > > Thanks, > > > > Laszlo > > > >=20 > > > > Laszlo Ersek (10): > > > > roms: lift "edk2-funcs.sh" from "tests/uefi-test-tools/build.sh= " > > > > roms/edk2-funcs.sh: require gcc-4.8+ for building i386 and x86_= 64 > > > > tests/uefi-test-tools/build.sh: work around TianoCore#1607 > > > > roms/edk2: advance to tag edk2-stable201903 > > > > roms/edk2-funcs.sh: add the qemu_edk2_get_thread_count() functi= on > > > > roms/Makefile: replace the $(EFIROM) target with "edk2-basetool= s" > > > > roms: build edk2 firmware binaries and variable store templates > > > > pc-bios: add edk2 firmware binaries and variable store template= s > > > > pc-bios: document the edk2 firmware images; add firmware descri= ptors > > > > Makefile: install the edk2 firmware images and their descriptor= s > > > >=20 > > > > Makefile | 17 +- > > > > pc-bios/README | 11 + > > > > pc-bios/descriptors/50-edk2-i386-secure.json | 34 +++ > > > > pc-bios/descriptors/50-edk2-x86_64-secure.json | 35 +++ > > > > pc-bios/descriptors/60-edk2-aarch64.json | 31 +++ > > > > pc-bios/descriptors/60-edk2-arm.json | 31 +++ > > > > pc-bios/descriptors/60-edk2-i386.json | 33 +++ > > > > pc-bios/descriptors/60-edk2-x86_64.json | 34 +++ > > > > pc-bios/edk2-aarch64-code.fd | Bin 0 -> 671088= 64 bytes > > > > pc-bios/edk2-arm-code.fd | Bin 0 -> 671088= 64 bytes > > > > pc-bios/edk2-arm-vars.fd | Bin 0 -> 671088= 64 bytes > > >=20 > > > GitHub moans here: > > >=20 > > > remote: warning: GH001: Large files detected. You may want to try G= it > > > Large File Storage - https://git-lfs.github.com. > > > remote: warning: See http://git.io/iEPt8g for more information. > > > remote: warning: File pc-bios/edk2-arm-vars.fd is 64.00 MB; this is > > > larger than GitHub's recommended maximum file size of 50.00 MB > > > remote: warning: File pc-bios/edk2-arm-code.fd is 64.00 MB; this is > > > larger than GitHub's recommended maximum file size of 50.00 MB > > > remote: warning: File pc-bios/edk2-aarch64-code.fd is 64.00 MB; thi= s is > > > larger than GitHub's recommended maximum file size of 50.00 MB > >=20 > > I wonder if this is a such that github isn't handling sparse files > > well, or if they just blindly do this check before they look at the > > actual required storage for the files. > >=20 > > Regards, > > Daniel >=20 >=20 > Right. But really: can we keep these around compressed? I think it is viable for us to xz compress the images that we store in git & just let make "build" the uncompressed images when needed. Regards, Daniel --=20 |: https://berrange.com -o- https://www.flickr.com/photos/dberran= ge :| |: https://libvirt.org -o- https://fstop138.berrange.c= om :| |: https://entangle-photo.org -o- https://www.instagram.com/dberran= ge :|