From: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>
To: Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <eduardo@habkost.net>
Cc: "Michael S . Tsirkin" <mst@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Eric Blake" <eblake@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
qemu-devel@nongnu.org
Subject: [PATCH][RESEND v3 0/3] Hyper-V Dynamic Memory Protocol driver (hv-balloon)
Date: Fri, 24 Feb 2023 22:41:13 +0100 [thread overview]
Message-ID: <cover.1677274611.git.maciej.szmigiero@oracle.com> (raw)
From: "Maciej S. Szmigiero" <maciej.szmigiero@oracle.com>
This is a rebase/resend of v2 patch series located here:
https://lore.kernel.org/qemu-devel/cover.1672878904.git.maciej.szmigiero@oracle.com/
The only changes from v2 are fixing some conflicts around build files (and
re-testing).
Kconfig.host | 3 +
configure | 36 +
hw/hyperv/Kconfig | 5 +
hw/hyperv/hv-balloon.c | 2185 ++++++++++++++++++++++++++++++
hw/hyperv/meson.build | 1 +
hw/hyperv/trace-events | 16 +
hw/i386/Kconfig | 2 +
hw/i386/pc.c | 4 +-
hw/mem/Kconfig | 4 +
hw/mem/hapvdimm.c | 221 +++
hw/mem/meson.build | 1 +
include/hw/hyperv/dynmem-proto.h | 423 ++++++
include/hw/mem/hapvdimm.h | 27 +
meson.build | 4 +-
qapi/machine.json | 68 +
15 files changed, 2998 insertions(+), 2 deletions(-)
create mode 100644 hw/hyperv/hv-balloon.c
create mode 100644 hw/mem/hapvdimm.c
create mode 100644 include/hw/hyperv/dynmem-proto.h
create mode 100644 include/hw/mem/hapvdimm.h
next reply other threads:[~2023-02-24 21:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 21:41 Maciej S. Szmigiero [this message]
2023-02-24 21:41 ` [PATCH][RESEND v3 1/3] hapvdimm: add a virtual DIMM device for memory hot-add protocols Maciej S. Szmigiero
2023-02-27 15:25 ` David Hildenbrand
2023-02-28 14:14 ` Maciej S. Szmigiero
2023-02-28 15:02 ` David Hildenbrand
2023-02-28 21:27 ` Maciej S. Szmigiero
2023-02-28 22:12 ` David Hildenbrand
2023-03-01 16:26 ` Maciej S. Szmigiero
2023-03-01 17:24 ` David Hildenbrand
2023-03-01 22:08 ` Maciej S. Szmigiero
2023-03-02 9:28 ` David Hildenbrand
2023-02-24 21:41 ` [PATCH][RESEND v3 2/3] Add Hyper-V Dynamic Memory Protocol definitions Maciej S. Szmigiero
2023-02-24 21:41 ` [PATCH][RESEND v3 3/3] Add a Hyper-V Dynamic Memory Protocol driver (hv-balloon) Maciej S. Szmigiero
2023-02-28 16:18 ` Igor Mammedov
2023-02-28 17:12 ` David Hildenbrand
2023-02-28 17:34 ` Daniel P. Berrangé
2023-02-28 21:24 ` Maciej S. Szmigiero
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=cover.1677274611.git.maciej.szmigiero@oracle.com \
--to=mail@maciej.szmigiero.name \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=david@redhat.com \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=marcandre.lureau@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.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).