All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Avi Kivity <avi@redhat.com>, kvm <kvm@vger.kernel.org>,
	Gleb Natapov <gleb@redhat.com>
Subject: Re: [PATCH] KVM: x86: Drop obsolete warning about INIT on runnable VCPU
Date: Thu, 3 Feb 2011 14:21:51 -0200	[thread overview]
Message-ID: <20110203162151.GA8942@amt.cnet> (raw)
In-Reply-To: <4D47FC23.40300@siemens.com>

On Tue, Feb 01, 2011 at 01:27:15PM +0100, Jan Kiszka wrote:
> This warning was once used for debugging QEMU user space. Though
> uncommon, it is actually possible to send an INIT request to a running
> VCPU. So better drop this warning before someone misuses it to flood
> kernel logs this way.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>  arch/x86/kvm/lapic.c |    4 ----
>  1 files changed, 0 insertions(+), 4 deletions(-)

Applied, thanks.


      reply	other threads:[~2011-02-03 17:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01 12:27 [PATCH] KVM: x86: Drop obsolete warning about INIT on runnable VCPU Jan Kiszka
2011-02-03 16:21 ` Marcelo Tosatti [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=20110203162151.GA8942@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@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.