[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <65935935-bdd9-c6a6-1a33-2bbaf6ffbbc5@redhat.com>
Date: Wed, 14 Dec 2016 17:35:53 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Christoffer Dall <christoffer.dall@...aro.org>,
Maninder Singh <maninder1.s@...sung.com>
Cc: catalin.marinas@....com, will.deacon@....com, marc.zyngier@....com,
rkrcmar@...hat.com, cmetcalf@...lanox.com, panand@...hat.com,
mark.rutland@....com, james.morse@....com,
akpm@...ux-foundation.org, sandeepa.s.prabhu@...il.com,
labbott@...hat.com, shijie.huang@....com,
ard.biesheuvel@...aro.org, wangkefeng.wang@...wei.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
kvmarm@...ts.cs.columbia.edu, kvm@...r.kernel.org,
pankaj.m@...sung.com, ajeet.y@...sung.com, cpgs@...sung.com,
Vaneet Narang <v.narang@...sung.com>
Subject: Re: [PATCH 1/1] arm64: Correcting format specifier for printing 64
bit addresses
On 06/12/2016 17:11, Christoffer Dall wrote:
> + kvm_err("Unsupported guest CP%d access at: %08lx\n",
> + cp, *vcpu_pc(vcpu));
> + else
> + kvm_err("Unsupported guest CP%d access at: %016lx\n",
> + cp, *vcpu_pc(vcpu));
>
> It feels a bit much to me to have an if-statement to differentiate the
> number of leading zeros, so if it's important to always have fixed
> widths then I would just use %016lx in both cases.
Really, this is just a debugging message. Just use "0x%lx" and let's
stop bikeshedding. :)
Paolo
Powered by blists - more mailing lists