Skip a few messages by default: command line args; flat binary; earlyprintk.
PATCH 1/1 Skip a few messages by default: command line args; flat binary; earlyprintk.
The partial command line args & earlyprintk=serial are still enabled in the debug mode. Warning that a flat binary kernel image is attemped to be loaded is completely dropped. These are not that informative, once one is past intial debugging, and only polute the console.
--- builtin-run.c | 10 ++++++---- kvm.c | 1 - x86/kvm.c | 8 ++++++-- 3 files changed, 12 insertions(+), 7 deletions(-)
builtin-run.c +6 -4
@@ -613,10 +613,12 @@ static struct kvm *kvm_cmd_run_init(int argc, const char **argv) kvm->cfg.real_cmdline = real_cmdline; -printf (" # %s run -k %s -m %Lu -c %d --name %s\n" ,KVM_BINARY_NAME , - kvm->cfg.kernel_filename, - (unsigned long long )kvm->cfg.ram_size /1024 /1024 , - kvm->cfg.nrcpus, kvm->cfg.guest_name); +if (do_debug_print) { +printf (" # %s run -k %s -m %Lu -c %d --name %s\n" ,KVM_BINARY_NAME , + kvm->cfg.kernel_filename, + (unsigned long long )kvm->cfg.ram_size /1024 /1024 , + kvm->cfg.nrcpus, kvm->cfg.guest_name); + }if (init_list__init (kvm) <0 )die ("Initialisation failed" );
kvm.c +0 -1
@@ -378,7 +378,6 @@ bool kvm__load_kernel(struct kvm *kvm, const char *kernel_filename,if (ret) goto found_kernel; -pr_warning ("%s is not a bzImage. Trying to load it as a flat binary..." , kernel_filename);#endif ret =load_elf_binary (kvm, fd_kernel, fd_initrd, kernel_cmdline);
x86/kvm.c +6 -2
@@ -124,8 +124,12 @@ void kvm__arch_set_cmdline(char *cmdline, bool video) "i8042.dumbkbd=1 i8042.nopnp=1");if (video)strcat (cmdline," video=vesafb console=tty0" ); -else -strcat (cmdline," console=ttyS0 earlyprintk=serial i8042.noaux=1" ); +else { +strcat (cmdline," console=ttyS0 i8042.noaux=1" ); +if (do_debug_print) { +strcat (cmdline," earlyprintk=serial" ); + } + } }/* Architecture-specific KVM init */
Signature · 1 line
2.1.4
Hi Dimitri,
thanks for sharing your patches.
Quoted 20 lines · Dimitri John Ledkov
The partial command line args & earlyprintk=serial are still enabled in the debug mode. Warning that a flat binary kernel image is attemped to be loaded is completely dropped. These are not that informative, once one is past intial debugging, and only polute the console.
Signed-off-by Dimitri John Ledkov <[email protected]>--- builtin-run.c | 10 ++++++---- kvm.c | 1 - x86/kvm.c | 8 ++++++-- 3 files changed, 12 insertions(+), 7 deletions(-)builtin-run.c +0
-0@@ -613,10 +613,12 @@ static struct kvm *kvm_cmd_run_init(int argc, const char **argv) kvm->cfg.real_cmdline = real_cmdline;
builtin-run.c static struct kvm *kvm_cmd_run_init(int argc, const char **argv) · line 621
Quoted 10 lines
builtin-run.c +6
-4-printf (" # %s run -k %s -m %Lu -c %d --name %s\n" ,KVM_BINARY_NAME , - kvm->cfg.kernel_filename, - (unsigned long long )kvm->cfg.ram_size /1024 /1024 , - kvm->cfg.nrcpus, kvm->cfg.guest_name); +if (do_debug_print) { +printf (" # %s run -k %s -m %Lu -c %d --name %s\n" ,KVM_BINARY_NAME , + kvm->cfg.kernel_filename, + (unsigned long long )kvm->cfg.ram_size /1024 /1024 , + kvm->cfg.nrcpus, kvm->cfg.guest_name); + }
I like the general idea. In fact I have this very patch (among others) in my tree too. I applied similar guarding to other messages as well (mostly those that only show up on ARM, but also the "ended normally" message). Like any good UNIX tool kvmtool should keep quiet if it has nothing worthwhile to say ;-)
But looking at it more closely, I see that there is pr_debug() defined doing that "if (do_debug_print)" already. The only issue is that is prints source line information, which is not really useful here. But then again there does not seem to be any user of it?
So what about the following:
- We avoid printing pr_info() messages in the default case. Looking at its current users in the tree this information is not really useful for normal users. We enable pr_info() output only if do_debug_print is enabled or introduce another command line flag (--verbose?) for that.
- We check each user of pr_info() to see whether this information is actually "informational" or whether it should be converted to pr_warn.
- We change the above line to use pr_info instead of printf.
- We fix the EOL mayhem we have atm while at it.
If you don't mind I will give this a try later this week.
kvm.c bool kvm__load_kernel(struct kvm *kvm, const char *kernel_filename, · line 381
Quoted 12 lines
builtin-run.c +0
-0if (init_list__init (kvm) <0 )die ("Initialisation failed" );kvm.c +0
-1@@ -378,7 +378,6 @@ bool kvm__load_kernel(struct kvm *kvm, const char *kernel_filename,if (ret) goto found_kernel; -pr_warning ("%s is not a bzImage. Trying to load it as a flat binary..." , kernel_filename);
I think on x86 this message is useful to have: to point people to the fact that they are trying to load a kernel which most probably isn't one. Do you actually load a "flat binary", so not a Linux bzImage? If yes, what is it? Does this work for you? I didn't have the impression that this code was actually used at all.
If you do use it, could you please give my kernel loading series [1] a try? I touch flat binary loading there, but had no chance to test it.
Quoted 9 lines
kvm.c +0
-0#endif ret =load_elf_binary (kvm, fd_kernel, fd_initrd, kernel_cmdline);x86/kvm.c +0
-0@@ -124,8 +124,12 @@ void kvm__arch_set_cmdline(char *cmdline, bool video) "i8042.dumbkbd=1 i8042.nopnp=1");
x86/kvm.c void kvm__arch_set_cmdline(char *cmdline, bool video) · line 132
Quoted 10 lines
x86/kvm.c +6
-2if (video)strcat (cmdline," video=vesafb console=tty0" ); -else -strcat (cmdline," console=ttyS0 earlyprintk=serial i8042.noaux=1" ); +else { +strcat (cmdline," console=ttyS0 i8042.noaux=1" ); +if (do_debug_print) { +strcat (cmdline," earlyprintk=serial" ); + } + }
I am not completely convinced of this one. The do_debug_print is meant to affect kvmtool's own debug output only and should really have no effect on the guest's kernel output, shouldn't it?
Maybe we should clarify the semantics in the documentation?
Cheers,
Andre.
Quoted 4 lines
x86/kvm.c +0
-0}/* Architecture-specific KVM init */
Hello,
A bit of context. I'm from Clear Linux* Project for Intel Architecture and we use lkvm as the hypervisor in Clear Containers for Docker Engine http://blog.surgut.co.uk/2015/09/clear-containers-for-docker-engine.html
For us, we really do not want any output coming from the hypervisor, or kernel, or init. We use systemd, and the only unit that has TTY connected for output is the ultimate docker workload user has requested. Thus I am avert --vey-quiet mode for lkvm. I understand that this is outside of the usual intended use-case for kvmtool (i.e. kernel development), but it's really lean and nice to work with.
Quoted 37 lines · Andre Przywara
Hi Dimitri,
thanks for sharing your patches.
Quoted 20 lines · Dimitri John Ledkov
The partial command line args & earlyprintk=serial are still enabled in the debug mode. Warning that a flat binary kernel image is attemped to be loaded is completely dropped. These are not that informative, once one is past intial debugging, and only polute the console.
Signed-off-by Dimitri John Ledkov <[email protected]>--- builtin-run.c | 10 ++++++---- kvm.c | 1 - x86/kvm.c | 8 ++++++-- 3 files changed, 12 insertions(+), 7 deletions(-)builtin-run.c +0
-0@@ -613,10 +613,12 @@ static struct kvm *kvm_cmd_run_init(int argc, const char **argv) kvm->cfg.real_cmdline = real_cmdline;builtin-run.c static struct kvm *kvm_cmd_run_init(int argc, const char **argv) · line 621
Quoted 10 lines
builtin-run.c +6
-4-printf (" # %s run -k %s -m %Lu -c %d --name %s\n" ,KVM_BINARY_NAME , - kvm->cfg.kernel_filename, - (unsigned long long )kvm->cfg.ram_size /1024 /1024 , - kvm->cfg.nrcpus, kvm->cfg.guest_name); +if (do_debug_print) { +printf (" # %s run -k %s -m %Lu -c %d --name %s\n" ,KVM_BINARY_NAME , + kvm->cfg.kernel_filename, + (unsigned long long )kvm->cfg.ram_size /1024 /1024 , + kvm->cfg.nrcpus, kvm->cfg.guest_name); + }I like the general idea. In fact I have this very patch (among others)
Quoted 9 lines
in my tree too. I applied similar guarding to other messages as well (mostly those that only show up on ARM, but also the "ended normally" message). Like any good UNIX tool kvmtool should keep quiet if it has nothing worthwhile to say ;-)
But looking at it more closely, I see that there ispr_debug()defined doing that "if (do_debug_print)" already. The only issue is that is prints source line information, which is not really useful here. But then again there does not seem to be any user of it?
I'd be happy to change these to pr_debug() messages.
Quoted 8 lines
So what about the following:
- We avoid printingpr_info()messages in the default case. Looking at its current users in the tree this information is not really useful for normal users. We enablepr_info()output only ifdo_debug_printis enabled or introduce another command line flag (--verbose?) for that.
- We check each user ofpr_info()to see whether this information is actually "informational" or whether it should be converted topr_warn.
- We change the above line to usepr_infoinstead of printf.
Sounds good to me. That should work as well.
Quoted 2 lines
- We fix the EOL mayhem we have atm while at it.
Not quite sure what you mean by `EOL mayhem' could you please elaborate?
Quoted 2 lines
If you don't mind I will give this a try later this week.
Thumbs up!
Quoted 11 lines
Quoted 11 lines
builtin-run.c +0
-0if (init_list__init (kvm) <0 )die ("Initialisation failed" );kvm.c +0
-0@@ -378,7 +378,6 @@ bool kvm__load_kernel(struct kvm *kvm, const char *kernel_filename,if (ret) goto found_kernel;
Quoted 7 lines
kvm.c bool kvm__load_kernel(struct kvm *kvm, const char *kernel_filename, · line 381
Quoted 1 line
kvm.c +0
-1-pr_warning ("%s is not a bzImage. Trying to load it as a flat binary..." , kernel_filename);I think on x86 this message is useful to have: to point people to the fact that they are trying to load a kernel which most probably isn't one. Do you actually load a "flat binary", so not a Linux bzImage? If yes, what is it? Does this work for you? I didn't have the impression that this code was actually used at all.
We do use flat kernel loading, and we have extra patches for that. But I haven't reconciled that with current upstream tree yet.
Quoted 3 lines
If you do use it, could you please give my kernel loading series [1] a try? I touch flat binary loading there, but had no chance to test it.
These look very interesting. I will definitely look into them.
Quoted 15 lines
Quoted 15 lines
kvm.c +0
-0#endif ret =load_elf_binary (kvm, fd_kernel, fd_initrd, kernel_cmdline);x86/kvm.c +2
-2@@ -124,8 +124,12 @@ void kvm__arch_set_cmdline(char *cmdline, bool video) "i8042.dumbkbd=1 i8042.nopnp=1");if (video)strcat (cmdline," video=vesafb console=tty0" ); -else -strcat (cmdline," console=ttyS0 earlyprintk=serial i8042.noaux=1" ); +else { +strcat (cmdline," console=ttyS0 i8042.noaux=1" );
Quoted 8 lines
x86/kvm.c void kvm__arch_set_cmdline(char *cmdline, bool video) · line 132
Quoted 4 lines
x86/kvm.c +4
-0+if (do_debug_print) { +strcat (cmdline," earlyprintk=serial" ); + } + }I am not completely convinced of this one. The
do_debug_printis meant to affect kvmtool's own debug output only and should really have no effect on the guest's kernel output, shouldn't it?
I have no idea about this one. Imho, earlyprintk=serial is too much. On the other hand it's inline with the original lkvm usecase. Not at all needed for my usecase. Maybe, I should add --very-quiet option which doesn't enable earlyprintk by default?
Quoted 11 lines
Maybe we should clarify the semantics in the documentation?
Cheers,
Andre.[1] http://marc.info/?l=kvm&m=143825354808135
Quoted 4 lines
x86/kvm.c +0
-0}/* Architecture-specific KVM init */
Signature · 8 lines
Regards, Dimitri. 90 sleeps till Christmas, or less https://clearlinux.org Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ.
Quoted 52 lines · Andre Przywara
Quoted 20 lines · Dimitri John Ledkov
The partial command line args & earlyprintk=serial are still enabled in the debug mode. Warning that a flat binary kernel image is attemped to be loaded is completely dropped. These are not that informative, once one is past intial debugging, and only polute the console.
Signed-off-by Dimitri John Ledkov <[email protected]>--- builtin-run.c | 10 ++++++---- kvm.c | 1 - x86/kvm.c | 8 ++++++-- 3 files changed, 12 insertions(+), 7 deletions(-)builtin-run.c +0
-0@@ -613,10 +613,12 @@ static struct kvm *kvm_cmd_run_init(int argc, const char **argv) kvm->cfg.real_cmdline = real_cmdline;builtin-run.c static struct kvm *kvm_cmd_run_init(int argc, const char **argv) · line 621
Quoted 10 lines
builtin-run.c +6
-4-printf (" # %s run -k %s -m %Lu -c %d --name %s\n" ,KVM_BINARY_NAME , - kvm->cfg.kernel_filename, - (unsigned long long )kvm->cfg.ram_size /1024 /1024 , - kvm->cfg.nrcpus, kvm->cfg.guest_name); +if (do_debug_print) { +printf (" # %s run -k %s -m %Lu -c %d --name %s\n" ,KVM_BINARY_NAME , + kvm->cfg.kernel_filename, + (unsigned long long )kvm->cfg.ram_size /1024 /1024 , + kvm->cfg.nrcpus, kvm->cfg.guest_name); + }I like the general idea. In fact I have this very patch (among others) in my tree too. I applied similar guarding to other messages as well (mostly those that only show up on ARM, but also the "ended normally" message). Like any good UNIX tool kvmtool should keep quiet if it has nothing worthwhile to say ;-)
But looking at it more closely, I see that there ispr_debug()defined doing that "if (do_debug_print)" already. The only issue is that is prints source line information, which is not really useful here. But then again there does not seem to be any user of it?So what about the following:
- We avoid printingpr_info()messages in the default case. Looking at its current users in the tree this information is not really useful for normal users. We enablepr_info()output only ifdo_debug_printis enabled or introduce another command line flag (--verbose?) for that.
- We check each user ofpr_info()to see whether this information is actually "informational" or whether it should be converted topr_warn.
- We change the above line to usepr_infoinstead of printf.
- We fix the EOL mayhem we have atm while at it.
Quoted 1 line
If you don't mind I will give this a try later this week.
Sounds good to me.
Will