From: Nadav Amit <nadav.amit@gmail.com>
To: Bandan Das <bsd@redhat.com>, Nadav Amit <namit@cs.technion.ac.il>
Cc: pbonzini@redhat.com, gleb@kernel.org, tglx@linutronix.de,
mingo@redhat.com, x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: Fix lapic.c debug prints
Date: Mon, 30 Jun 2014 04:03:47 +0300 [thread overview]
Message-ID: <53B0B773.3030107@gmail.com> (raw)
In-Reply-To: <jpgr427kys6.fsf@redhat.com>
On 6/30/14, 3:48 AM, Bandan Das wrote:
> Nadav Amit <namit@cs.technion.ac.il> writes:
>
>> In two cases lapic.c does not use the apic_debug macro correctly. This patch
>> fixes them.
>>
>> Signed-off-by: Nadav Amit <namit@cs.technion.ac.il>
>> ---
>> arch/x86/kvm/lapic.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
>> index 0069118..3855103 100644
>> --- a/arch/x86/kvm/lapic.c
>> +++ b/arch/x86/kvm/lapic.c
>> @@ -1451,7 +1451,7 @@ void kvm_lapic_reset(struct kvm_vcpu *vcpu)
>> vcpu->arch.apic_arb_prio = 0;
>> vcpu->arch.apic_attention = 0;
>>
>> - apic_debug(KERN_INFO "%s: vcpu=%p, id=%d, base_msr="
>> + apic_debug("%s: vcpu=%p, id=%d, base_msr="
>> "0x%016" PRIx64 ", base_address=0x%0lx.\n", __func__,
>> vcpu, kvm_apic_id(apic),
>> vcpu->arch.apic_base, apic->base_address);
>> @@ -1895,7 +1895,7 @@ void kvm_apic_accept_events(struct kvm_vcpu *vcpu)
>> /* evaluate pending_events before reading the vector */
>> smp_rmb();
>> sipi_vector = apic->sipi_vector;
>> - pr_debug("vcpu %d received sipi with vector # %x\n",
>> + apic_debug("vcpu %d received sipi with vector # %x\n",
>
> Why don't we just use pr_debug all throughout ?
>
I don't know. I just tried to make it consistent, since it really bugged
me while I was debugging the local-apic.
If you prefer the other way around (which does seem to be better), I can
do the search-and-replace.
Nadav
next prev parent reply other threads:[~2014-06-30 1:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 9:28 [PATCH] KVM: x86: Fix lapic.c debug prints Nadav Amit
2014-06-30 0:48 ` Bandan Das
2014-06-30 1:03 ` Nadav Amit [this message]
2014-06-30 12:12 ` Paolo Bonzini
2014-06-30 17:39 ` Bandan Das
2014-06-30 18:02 ` Paolo Bonzini
2014-06-30 18:07 ` Bandan Das
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=53B0B773.3030107@gmail.com \
--to=nadav.amit@gmail.com \
--cc=bsd@redhat.com \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namit@cs.technion.ac.il \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.