All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] KVM: arm/arm64: reduce verbosity of KVM init log
Date: Fri, 2 Mar 2018 09:36:28 +0000	[thread overview]
Message-ID: <20180302093628.GA18501@arm.com> (raw)
In-Reply-To: <20180302081630.6385-1-ard.biesheuvel@linaro.org>

On Fri, Mar 02, 2018 at 08:16:30AM +0000, Ard Biesheuvel wrote:
> On my GICv3 system, the following is printed to the kernel log at boot:
> 
>    kvm [1]: 8-bit VMID
>    kvm [1]: IDMAP page: d20e35000
>    kvm [1]: HYP VA range: 800000000000:ffffffffffff
>    kvm [1]: vgic-v2 at 2c020000
>    kvm [1]: GIC system register CPU interface enabled
>    kvm [1]: vgic interrupt IRQ1
>    kvm [1]: virtual timer IRQ4
>    kvm [1]: Hyp mode initialized successfully
> 
> The KVM IDMAP is a mapping of a statically allocated kernel structure,
> and so printing its physical address leaks the physical placement of
> the kernel when physical KASLR in effect. So change the kvm_info() to
> kvm_debug() to remove it from the log output.
> 
> While at it, trim the output a bit more: IRQ numbers can be found in
> /proc/interrupts, and the HYP VA and vgic-v2 lines are not highly
> informational either.
> 
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
>  virt/kvm/arm/arch_timer.c     | 2 +-
>  virt/kvm/arm/mmu.c            | 6 +++---
>  virt/kvm/arm/vgic/vgic-init.c | 2 +-
>  virt/kvm/arm/vgic/vgic-v2.c   | 2 +-
>  4 files changed, 6 insertions(+), 6 deletions(-)

Acked-by: Will Deacon <will.deacon@arm.com>

Will

  reply	other threads:[~2018-03-02  9:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-02  8:16 [PATCH] KVM: arm/arm64: reduce verbosity of KVM init log Ard Biesheuvel
2018-03-02  9:36 ` Will Deacon [this message]
2018-03-02  9:37 ` Christoffer Dall

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=20180302093628.GA18501@arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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.