All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, imammedo@redhat.com,
	peter.huangpeng@huawei.com,
	zhanghailiang <zhang.zhanghailiang@huawei.com>,
	Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/3] pc-dimm: add a function to calculate VM's current RAM size
Date: Thu, 20 Nov 2014 11:10:20 +0200	[thread overview]
Message-ID: <20141120091020.GA4050@redhat.com> (raw)
In-Reply-To: <546CC5E7.3010908@redhat.com>

On Wed, Nov 19, 2014 at 09:31:35AM -0700, Eric Blake wrote:
> On 11/19/2014 09:06 AM, Michael S. Tsirkin wrote:
> 
> >>>> This affects QMP right?
> >>>
> >>> I think later patches will tell how. CC'ing Eric.
> >>
> >> As far as I can tell, this is just correcting a reporting issue; the
> >> existing QMP commands/events for tracking balloon size will now properly
> >> account for hotplugged memory.
> >>
> >> What I don't know is if this change in semantics will affect any users.
> >>  Libvirt is not yet supporting memory hotplug, so ideally, fixing this
> >> bug before libvirt uses memory hotplug means libvirt will never have to
> >> worry about qemu versions that do incorrect reporting.
> >>
> >> The alternative is to declare that the existing QMP commands cannot
> >> change in semantics for the existing members that it reports, and must
> >> instead report additional dictionary members describing the amount of
> >> hot-plugged memory, and then require that the client add the numbers
> >> together itself.  That sounds mean to the client, so I'm hoping we don't
> >> have to go there.
> > 
> > 
> > IOW you ack this patch for 2.2?
> > 
> 
> Is memory hotplug one of the new features in 2.2?  If so, then yes, we
> should get its semantics right from the start (this is a bug fix to
> avoid a release with broken semantics).  On the other hand, if hotplug
> existed in 2.1, then we already have a release with odd semantics, so
> delaying this fix until 2.3 and leaving 2.2 with the same odd semantics
> would not hurt, and it then becomes a judgment call of whether we are
> rushing in a possibly incomplete solution by trying to get this into
> 2.2. (Sorry I haven't been following the history of memory hotplug closer)

AFAIK it's there since 2.0.


> 
> -- 
> Eric Blake   eblake redhat com    +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
> 

  parent reply	other threads:[~2014-11-20  9:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-17  5:11 [Qemu-devel] [PATCH v2 0/3] fix bug about balloon working incorrectly when hotplug memeory zhanghailiang
2014-11-17  5:11 ` [Qemu-devel] [PATCH v2 1/3] pc-dimm: add a function to calculate VM's current RAM size zhanghailiang
2014-11-19  9:59   ` Igor Mammedov
2014-11-19 10:32   ` Michael S. Tsirkin
2014-11-19 15:13     ` Luiz Capitulino
2014-11-19 15:52       ` Eric Blake
2014-11-19 16:06         ` Michael S. Tsirkin
2014-11-19 16:31           ` Eric Blake
2014-11-20  2:31             ` zhanghailiang
2014-11-20  9:10             ` Michael S. Tsirkin [this message]
2014-11-20  2:33     ` zhanghailiang
2014-11-17  5:11 ` [Qemu-devel] [PATCH v2 2/3] virtio-balloon: Fix balloon not working correctly when hotplug memory zhanghailiang
2014-11-17  5:11 ` [Qemu-devel] [PATCH v2 3/3] virtio-balloon: Add some trace events zhanghailiang
2014-11-17  6:07 ` [Qemu-devel] [PATCH v2 0/3] fix bug about balloon working incorrectly when hotplug memeory Michael S. Tsirkin
2014-11-17 10:39 ` Michael S. Tsirkin
2014-11-17 10:53   ` zhanghailiang
2014-11-17 12:25     ` zhanghailiang
2014-11-17 12:40       ` Michael S. Tsirkin
2014-11-18  2:50         ` zhanghailiang
2014-11-19  8:28 ` zhanghailiang
2014-11-19 10:06   ` Igor Mammedov
2015-03-03 14:04 ` Luiz Capitulino
2015-03-04 12:55   ` zhanghailiang

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=20141120091020.GA4050@redhat.com \
    --to=mst@redhat.com \
    --cc=eblake@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --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.