All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Fritsch <sf@sfritsch.de>
Cc: zhanghailiang <zhang.zhanghailiang@huawei.com>,
	hangaohuai@huawei.com, kvm@vger.kernel.org, gleb@kernel.org,
	peter.huangpeng@huawei.com
Subject: Re: [PATCH] KVM: add KVM_CAP_VMX_APICV to advertise hardware apic-v support
Date: Thu, 18 Dec 2014 10:23:44 +0100	[thread overview]
Message-ID: <54929D20.60505@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1412180954080.25777@eru.sfritsch.de>



On 18/12/2014 09:57, Stefan Fritsch wrote:
> I think setting the "recommended" bits to be best for the host where the 
> VM is first started should always be ok. When it migrates to a different 
> host, performance may not be optimal but otherwise it will work just fine. 
> After all, non-optimal performance is not different from the current 
> situation.

What if, due to a bug, a guest mysteriously starts failing on some hosts
of a cluster but not others?  This is really not a path you want to walk
down.

Paolo

  reply	other threads:[~2014-12-18  9:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11  8:07 [PATCH] KVM: add KVM_CAP_VMX_APICV to advertise hardware apic-v support zhanghailiang
2014-12-11 11:48 ` Paolo Bonzini
2014-12-11 12:53   ` zhanghailiang
2014-12-11 13:28     ` Radim Krčmář
2014-12-11 17:15     ` Paolo Bonzini
2014-12-17 22:17       ` Stefan Fritsch
2014-12-18  3:37         ` zhanghailiang
2014-12-18  8:30           ` Paolo Bonzini
2014-12-18  8:57             ` Stefan Fritsch
2014-12-18  9:23               ` Paolo Bonzini [this message]
2014-12-11 13:08 ` Radim Krčmář

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=54929D20.60505@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=gleb@kernel.org \
    --cc=hangaohuai@huawei.com \
    --cc=kvm@vger.kernel.org \
    --cc=peter.huangpeng@huawei.com \
    --cc=sf@sfritsch.de \
    --cc=zhang.zhanghailiang@huawei.com \
    /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.