[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191022210120.GQ2343@linux.intel.com>
Date: Tue, 22 Oct 2019 14:01:20 -0700
From: Sean Christopherson <sean.j.christopherson@...el.com>
To: Zhenzhong Duan <zhenzhong.duan@...cle.com>
Cc: linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com,
bp@...en8.de, x86@...nel.org, pbonzini@...hat.com,
rkrcmar@...hat.com, vkuznets@...hat.com, wanpengli@...cent.com,
jmattson@...gle.com, joro@...tes.org, boris.ostrovsky@...cle.com,
jgross@...e.com, peterz@...radead.org, will@...nel.org,
linux-hyperv@...r.kernel.org, kvm@...r.kernel.org,
mikelley@...rosoft.com, kys@...rosoft.com, haiyangz@...rosoft.com,
sthemmin@...rosoft.com, sashal@...nel.org,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH v7 2/5] x86/kvm: Change print code to use pr_*() format
On Mon, Oct 21, 2019 at 05:11:13PM +0800, Zhenzhong Duan wrote:
> pr_*() is preferred than printk(KERN_* ...), after change all the print
> in arch/x86/kernel/kvm.c will have "kvm_guest: xxx" style.
>
> No functional change.
>
> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@...cle.com>
> Reviewed-by: Vitaly Kuznetsov <vkuznets@...hat.com>
> Cc: Paolo Bonzini <pbonzini@...hat.com>
> Cc: Radim Krcmar <rkrcmar@...hat.com>
> Cc: Sean Christopherson <sean.j.christopherson@...el.com>
> Cc: Vitaly Kuznetsov <vkuznets@...hat.com>
> Cc: Wanpeng Li <wanpengli@...cent.com>
> Cc: Jim Mattson <jmattson@...gle.com>
> Cc: Joerg Roedel <joro@...tes.org>
> Cc: Thomas Gleixner <tglx@...utronix.de>
> Cc: Ingo Molnar <mingo@...hat.com>
> Cc: Borislav Petkov <bp@...en8.de>
> Cc: "H. Peter Anvin" <hpa@...or.com>
> ---
> arch/x86/kernel/kvm.c | 30 ++++++++++++++++--------------
> 1 file changed, 16 insertions(+), 14 deletions(-)
>
> diff --git a/arch/x86/kernel/kvm.c b/arch/x86/kernel/kvm.c
> index 3bc6a266..249f14a 100644
> --- a/arch/x86/kernel/kvm.c
> +++ b/arch/x86/kernel/kvm.c
> @@ -7,6 +7,8 @@
> * Authors: Anthony Liguori <aliguori@...ibm.com>
> */
>
> +#define pr_fmt(fmt) "kvm_guest: " fmt
Sort of a silly nit, especially since I suggested kvm_guest...
What about using kvm-guest instead of kvm_guest to be consistent with
kvm-clock, the other prolific logger in a KVM guest.
E.g.
kvm-clock: cpu 1, msr 551e041, secondary cpu clock
kvm-guest: setup async PF for cpu 1
kvm-guest: stealtime: cpu 1, msr 277695f40
kvm-clock: cpu 2, msr 551e081, secondary cpu clock
kvm-guest: setup async PF for cpu 2
kvm-guest: stealtime: cpu 2, msr 277715f40
kvm-clock: cpu 3, msr 551e0c1, secondary cpu clock
kvm-guest: setup async PF for cpu 3
kvm-guest: stealtime: cpu 3, msr 277795f40
kvm-clock: cpu 4, msr 551e101, secondary cpu clock
instead of
kvm-clock: cpu 1, msr 551e041, secondary cpu clock
kvm_guest: setup async PF for cpu 1
kvm_guest: stealtime: cpu 1, msr 277695f40
kvm-clock: cpu 2, msr 551e081, secondary cpu clock
kvm_guest: setup async PF for cpu 2
kvm_guest: stealtime: cpu 2, msr 277715f40
kvm-clock: cpu 3, msr 551e0c1, secondary cpu clock
kvm_guest: setup async PF for cpu 3
kvm_guest: stealtime: cpu 3, msr 277795f40
kvm-clock: cpu 4, msr 551e101, secondary cpu clock
Powered by blists - more mailing lists