From: David Hildenbrand <david@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
"Alexander Duyck" <alexander.duyck@gmail.com>,
"Alexander Bulekov" <alxndr@bu.edu>,
"Wei Wang" <wei.w.wang@intel.com>,
"Alexander Duyck" <alexander.h.duyck@linux.intel.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [PATCH v2 0/3] virtio-balloon: free page hinting fixes
Date: Wed, 20 May 2020 12:04:36 +0200 [thread overview]
Message-ID: <20200520100439.19872-1-david@redhat.com> (raw)
Some fixes for VIRTIO_BALLOON_F_FREE_PAGE_HINT. First issue was reported by
Alexander Bulekov [1], the other ones were discovered by me when digging
into the details.
We keep finding more issues, let's see how we'll proceed with this feature
long-term. These patches can be backported to stable QEMU.
[1] https://lkml.kernel.org/r/20200511044121.eihns2tdimdzgi4i@mozz.bu.edu
v1 -> v2:
- "virtio-balloon: fix free page hinting without an iothread"
-- Drop initialization to 0/false
-- Reformat one condition
- cc stable
David Hildenbrand (3):
virtio-balloon: fix free page hinting without an iothread
virtio-balloon: fix free page hinting check on unrealize
virtio-balloon: unref the iothread when unrealizing
hw/virtio/virtio-balloon.c | 36 ++++++++++++++++++------------------
1 file changed, 18 insertions(+), 18 deletions(-)
--
2.25.4
next reply other threads:[~2020-05-20 10:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 10:04 David Hildenbrand [this message]
2020-05-20 10:04 ` [PATCH v2 1/3] virtio-balloon: fix free page hinting without an iothread David Hildenbrand
2020-05-20 10:04 ` [PATCH v2 2/3] virtio-balloon: fix free page hinting check on unrealize David Hildenbrand
2020-05-20 10:04 ` [PATCH v2 3/3] virtio-balloon: unref the iothread when unrealizing David Hildenbrand
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=20200520100439.19872-1-david@redhat.com \
--to=david@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=alexander.h.duyck@linux.intel.com \
--cc=alxndr@bu.edu \
--cc=mst@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wei.w.wang@intel.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.