From: "Denis V. Lunev" <den@openvz.org>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org
Cc: Xiao Guangrong <guangrong.xiao@linux.intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 0/3] don't use NVDIMM for balooning
Date: Tue, 2 Feb 2016 12:49:30 +0300 [thread overview]
Message-ID: <56B07BAA.6010707@openvz.org> (raw)
In-Reply-To: <1453963872-13549-1-git-send-email-vsementsov@virtuozzo.com>
On 01/28/2016 09:51 AM, Vladimir Sementsov-Ogievskiy wrote:
> v4:
> 0001: Reviewed-by: Eric Blake <eblake@redhat.com>
> second patch is splitted to 0002 and 0003
> 0002: Add 'type' field instead of 'balloonable' to PCDIMMDeviceInfo
> 0003: chec 'type' instead of 'balloonable'
>
> v3:
> - do not use additional class variable
>
> NVDIMM for now is planned to use as a backing store for DAX filesystem
> in the guest and thus this memory is excluded from guest memory
> management and LRUs.
>
> In this case libvirt running QEMU along with configured balloon almost
> immediately inflates balloon and effectively kill the guest as
> qemu counts nvdimm as part of the ram.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> CC: Stefan Hajnoczi <stefanha@redhat.com>
> CC: Xiao Guangrong <guangrong.xiao@linux.intel.com>
> CC: "Michael S. Tsirkin" <mst@redhat.com>
> CC: Igor Mammedov <imammedo@redhat.com>
> CC: Eric Blake <eblake@redhat.com>
> CC: Markus Armbruster <armbru@redhat.com>
>
> Vladimir Sementsov-Ogievskiy (3):
> move get_current_ram_size to virtio-balloon.c
> pcdimm: add 'type' field to PCDIMMDeviceInfo
> balloon: don't use NVDIMM for ballooning
>
> hw/mem/pc-dimm.c | 27 +--------------------------
> hw/virtio/virtio-balloon.c | 29 +++++++++++++++++++++++++++++
> include/exec/cpu-common.h | 1 -
> qapi-schema.json | 5 ++++-
> stubs/qmp_pc_dimm_device_list.c | 5 -----
> 5 files changed, 34 insertions(+), 33 deletions(-)
>
ping
prev parent reply other threads:[~2016-02-02 9:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 6:51 [Qemu-devel] [PATCH v4 0/3] don't use NVDIMM for balooning Vladimir Sementsov-Ogievskiy
2016-01-28 6:51 ` [Qemu-devel] [PATCH 1/3] move get_current_ram_size to virtio-balloon.c Vladimir Sementsov-Ogievskiy
2016-01-28 6:51 ` [Qemu-devel] [PATCH 2/3] pcdimm: add 'type' field to PCDIMMDeviceInfo Vladimir Sementsov-Ogievskiy
2016-02-02 15:26 ` Markus Armbruster
2016-02-02 22:12 ` Eric Blake
2016-02-03 12:00 ` Vladimir Sementsov-Ogievskiy
2016-02-03 15:14 ` Eric Blake
2016-02-03 15:42 ` Markus Armbruster
2016-01-28 6:51 ` [Qemu-devel] [PATCH 3/3] balloon: don't use NVDIMM for ballooning Vladimir Sementsov-Ogievskiy
2016-02-02 15:30 ` Markus Armbruster
2016-02-03 12:01 ` Vladimir Sementsov-Ogievskiy
2016-02-02 22:13 ` Eric Blake
2016-02-03 15:42 ` Markus Armbruster
2016-02-03 16:23 ` Igor Mammedov
2016-02-03 17:21 ` Vladimir Sementsov-Ogievskiy
2016-02-04 6:20 ` Markus Armbruster
2016-02-04 10:21 ` Vladimir Sementsov-Ogievskiy
2016-02-05 9:53 ` Markus Armbruster
2016-02-05 12:00 ` Vladimir Sementsov-Ogievskiy
2016-02-02 9:49 ` Denis V. Lunev [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=56B07BAA.6010707@openvz.org \
--to=den@openvz.org \
--cc=armbru@redhat.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).