From: "Du, Changbin" <changbin.du@intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: changbin.du@intel.com, hpa@zytor.com, tglx@linutronix.de,
mingo@redhat.com, x86@kernel.org, linux-kernel@vger.kernel.org,
yamada.masahiro@socionext.com
Subject: Re: [PATCH v2 1/4] x86, build: Factor out fdimage/isoimage generation commands to standalone script
Date: Tue, 7 Nov 2017 18:35:24 +0800 [thread overview]
Message-ID: <20171107103524.GA16764@intel.com> (raw)
In-Reply-To: <20171107102029.4zvhovgdguthyg6u@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2497 bytes --]
On Tue, Nov 07, 2017 at 11:20:29AM +0100, Ingo Molnar wrote:
>
> * changbin.du@intel.com <changbin.du@intel.com> wrote:
>
> > From: Changbin Du <changbin.du@intel.com>
> >
> > The build message for fdimage/isoimage are pretty unstructured. The raw
> > shell command blocks are printed. We can improve them as regular build
> > system messages. Besides, writing commands in a shell script is much more
> > easy than in a Makefile.
> >
> > See Ingo's suggestion here https://lkml.org/lkml/2017/10/31/124.
> >
> > This patch factors out the commands used for fdimage/isoimage generation
> > from arch/x86/boot/Makefile to a new script arch/x86/boot/genimage.sh.
> > Then it adds the new kbuild command 'genimage' which invokes the new script.
> > All fdimages/isoimage files are now generated by a call to 'genimage' with
> > different parameters.
> >
> > Now 'make isoimage' becomes:
> > ...
> > Kernel: arch/x86/boot/bzImage is ready (#30)
> > GENIMAGE arch/x86/boot/image.iso
> > Size of boot image is 4 sectors -> No emulation
> > 15.37% done, estimate finish Sun Nov 5 23:36:57 2017
> > 30.68% done, estimate finish Sun Nov 5 23:36:57 2017
> > 46.04% done, estimate finish Sun Nov 5 23:36:57 2017
> > 61.35% done, estimate finish Sun Nov 5 23:36:57 2017
> > 76.69% done, estimate finish Sun Nov 5 23:36:57 2017
> > 92.00% done, estimate finish Sun Nov 5 23:36:57 2017
> > Total translation table size: 2048
> > Total rockridge attributes bytes: 659
> > Total directory bytes: 0
> > Path table size(bytes): 10
> > Max brk space used 0
> > 32608 extents written (63 MB)
> > Kernel: arch/x86/boot/image.iso is ready
>
> Could we please also do another patch, to make it emit only this by default:
>
> > GENIMAGE arch/x86/boot/image.iso
>
> None of the other messages really matter to the user.
>
> Maybe emit them when building with V=1 - but none of that info is really
> interesting IMHO.
>
Ingo, do you mean that omit below messages?
Size of boot image is 4 sectors -> No emulation
15.37% done, estimate finish Sun Nov 5 23:36:57 2017
...
32608 extents written (63 MB)
These are printed by mkisofs. How about just add '-quite' parameter to it?
Kernel: arch/x86/boot/bzImage is ready (#75)
GENIMAGE arch/x86/boot/image.iso
Using /usr/lib/ISOLINUX/isolinux.bin
Using /usr/lib/syslinux/modules/bios/ldlinux.c32
Kernel: arch/x86/boot/image.iso is ready
> Thanks,
>
> Ingo
--
Thanks,
Changbin Du
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2017-11-07 10:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 3:32 [PATCH v2 0/4] x86, kbuild: Some improvement for fdimage/isoimage generation changbin.du
2017-11-06 3:32 ` [PATCH v2 1/4] x86, build: Factor out fdimage/isoimage generation commands to standalone script changbin.du
2017-11-07 10:20 ` Ingo Molnar
2017-11-07 10:35 ` Du, Changbin [this message]
2017-11-07 11:12 ` Ingo Molnar
2017-11-07 11:13 ` [tip:x86/asm] x86/build: " tip-bot for Changbin Du
2017-11-06 3:32 ` [PATCH v2 2/4] x86, build: Add new paths for isolinux.bin and ldlinux.c32 changbin.du
2017-11-07 11:14 ` [tip:x86/asm] x86/build: " tip-bot for Changbin Du
2017-11-06 3:32 ` [PATCH v2 3/4] x86, build: Specify -input-charset=utf-8 for mkisofs changbin.du
2017-11-07 11:14 ` [tip:x86/asm] x86/build: " tip-bot for Changbin Du
2017-11-06 3:32 ` [PATCH v2 4/4] x86, boot: Add some generated files to the .gitignore file changbin.du
2017-11-07 11:14 ` [tip:x86/asm] x86/build: Add more " tip-bot for Changbin Du
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=20171107103524.GA16764@intel.com \
--to=changbin.du@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yamada.masahiro@socionext.com \
/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).