From: Paolo Bonzini <pbonzini@redhat.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: remove pointless cpu hotplug messages
Date: Thu, 07 May 2015 11:31:29 +0200 [thread overview]
Message-ID: <554B30F1.506@redhat.com> (raw)
In-Reply-To: <1430811548-34140-1-git-send-email-heiko.carstens@de.ibm.com>
On 05/05/2015 09:39, Heiko Carstens wrote:
> On cpu hotplug only KVM emits an unconditional message that its notifier
> has been called. It certainly can be assumed that calling cpu hotplug
> notifiers work, therefore there is no added value if KVM prints a message.
>
> If an error happens on cpu online KVM will still emit a warning.
>
> So let's remove this superfluous message.
>
> Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
> ---
> virt/kvm/kvm_main.c | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> index 90977418aeb6..5fb52af5b975 100644
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -2882,18 +2882,12 @@ static int hardware_enable_all(void)
> static int kvm_cpu_hotplug(struct notifier_block *notifier, unsigned long val,
> void *v)
> {
> - int cpu = (long)v;
> -
> val &= ~CPU_TASKS_FROZEN;
> switch (val) {
> case CPU_DYING:
> - pr_info("kvm: disabling virtualization on CPU%d\n",
> - cpu);
> hardware_disable();
> break;
> case CPU_STARTING:
> - pr_info("kvm: enabling virtualization on CPU%d\n",
> - cpu);
> hardware_enable();
> break;
> }
>
Applied, thanks.
Paolo
prev parent reply other threads:[~2015-05-07 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 7:39 [PATCH] KVM: remove pointless cpu hotplug messages Heiko Carstens
2015-05-05 11:20 ` Christian Borntraeger
2015-05-07 9:31 ` Paolo Bonzini [this message]
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=554B30F1.506@redhat.com \
--to=pbonzini@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.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.