qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Duyck <alexander.duyck@gmail.com>
To: pbonzini@redhat.com, david@redhat.com, mst@redhat.com
Cc: virtio-dev@lists.oasis-open.org, qemu-devel@nongnu.org
Subject: [PATCH v19 QEMU 2/4] linux-headers: update to contain virito-balloon free page reporting
Date: Thu, 09 Apr 2020 20:41:36 -0700	[thread overview]
Message-ID: <20200410034136.24738.52188.stgit@localhost.localdomain> (raw)
In-Reply-To: <20200410033729.24738.22879.stgit@localhost.localdomain>

From: Alexander Duyck <alexander.h.duyck@linux.intel.com>

Sync the latest upstream changes for free page reporting. To be
replaced by a full linux header sync.

Signed-off-by: Alexander Duyck <alexander.h.duyck@linux.intel.com>
---
 include/standard-headers/linux/virtio_balloon.h |    1 +
 1 file changed, 1 insertion(+)

diff --git a/include/standard-headers/linux/virtio_balloon.h b/include/standard-headers/linux/virtio_balloon.h
index 9375ca2a70de..1c5f6d6f2de6 100644
--- a/include/standard-headers/linux/virtio_balloon.h
+++ b/include/standard-headers/linux/virtio_balloon.h
@@ -36,6 +36,7 @@
 #define VIRTIO_BALLOON_F_DEFLATE_ON_OOM	2 /* Deflate balloon on OOM */
 #define VIRTIO_BALLOON_F_FREE_PAGE_HINT	3 /* VQ to report free pages */
 #define VIRTIO_BALLOON_F_PAGE_POISON	4 /* Guest is using page poisoning */
+#define VIRTIO_BALLOON_F_REPORTING	5 /* Page reporting virtqueue */
 
 /* Size of a PFN in the balloon interface. */
 #define VIRTIO_BALLOON_PFN_SHIFT 12



  parent reply	other threads:[~2020-04-10  3:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10  3:41 [PATCH v19 QEMU 0/4] virtio-balloon: add support for free page reporting Alexander Duyck
2020-04-10  3:41 ` [PATCH v19 QEMU 1/4] virtio-balloon: Implement support for page poison tracking feature Alexander Duyck
2020-04-15  8:08   ` David Hildenbrand
2020-04-15 17:17     ` Alexander Duyck
2020-04-15 18:16       ` David Hildenbrand
2020-04-15 19:28         ` Alexander Duyck
2020-04-15 19:46           ` David Hildenbrand
2020-04-15 21:16             ` Alexander Duyck
2020-04-16  8:18               ` David Hildenbrand
2020-04-16  8:36                 ` David Hildenbrand
2020-04-16 14:33                 ` Michael S. Tsirkin
2020-04-16 14:55                   ` David Hildenbrand
2020-04-16 18:21                     ` Alexander Duyck
2020-04-16 18:33                       ` David Hildenbrand
2020-04-10  3:41 ` Alexander Duyck [this message]
2020-04-10  3:41 ` [PATCH v19 QEMU 3/4] virtio-balloon: Provide an interface for free page reporting Alexander Duyck
2020-04-15  8:17   ` David Hildenbrand
2020-04-15  9:03     ` David Hildenbrand
2020-04-15 15:31     ` Alexander Duyck
2020-04-10  3:41 ` [PATCH v19 QEMU 4/4] memory: Do not allow direct write access to rom_device regions Alexander Duyck
2020-04-10 10:50   ` Paolo Bonzini
2020-04-13 22:48     ` Alexander Duyck
2020-04-14  7:36       ` 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=20200410034136.24738.52188.stgit@localhost.localdomain \
    --to=alexander.duyck@gmail.com \
    --cc=david@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=virtio-dev@lists.oasis-open.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 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).