From: Markus Armbruster <armbru@redhat.com>
To: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Eduardo Habkost" <eduardo@habkost.net>,
"David Hildenbrand" <david@redhat.com>,
"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>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v6 4/6] qapi: Add HvBalloonDeviceInfo sub-type to MemoryDeviceInfo
Date: Tue, 25 Jul 2023 10:26:11 +0200 [thread overview]
Message-ID: <87y1j4gzx8.fsf@pond.sub.org> (raw)
In-Reply-To: <cbe30f06-c787-7baf-01c9-573da902fa35@maciej.szmigiero.name> (Maciej S. Szmigiero's message of "Mon, 24 Jul 2023 13:43:14 +0200")
"Maciej S. Szmigiero" <mail@maciej.szmigiero.name> writes:
> On 24.07.2023 13:37, Markus Armbruster wrote:
>> "Maciej S. Szmigiero" <mail@maciej.szmigiero.name> writes:
>>
>>> From: "Maciej S. Szmigiero" <maciej.szmigiero@oracle.com>
>>>
>>> Used by the hv-balloon driver to report its provided memory state
>>> information.
>>>
>>> Co-developed-by: David Hildenbrand <david@redhat.com>
>>> Signed-off-by: Maciej S. Szmigiero <maciej.szmigiero@oracle.com>
>>> ---
>>> hw/core/machine-hmp-cmds.c | 15 +++++++++++++++
>>> qapi/machine.json | 39 ++++++++++++++++++++++++++++++++++++--
>>> 2 files changed, 52 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/hw/core/machine-hmp-cmds.c b/hw/core/machine-hmp-cmds.c
>>> index c3e55ef9e9cd..7b06ed35decb 100644
>>> --- a/hw/core/machine-hmp-cmds.c
>>> +++ b/hw/core/machine-hmp-cmds.c
>>> @@ -247,6 +247,7 @@ void hmp_info_memory_devices(Monitor *mon, const QDict *qdict)
>>> MemoryDeviceInfo *value;
>>> PCDIMMDeviceInfo *di;
>>> SgxEPCDeviceInfo *se;
>>> + HvBalloonDeviceInfo *hi;
>>> for (info = info_list; info; info = info->next) {
>>> value = info->value;
>>> @@ -304,6 +305,20 @@ void hmp_info_memory_devices(Monitor *mon, const QDict *qdict)
>>> monitor_printf(mon, " node: %" PRId64 "\n", se->node);
>>> monitor_printf(mon, " memdev: %s\n", se->memdev);
>>> break;
>>> + case MEMORY_DEVICE_INFO_KIND_HV_BALLOON:
>>
>> This is the only occurence of MEMORY_DEVICE_INFO_KIND_HV_BALLOON at the
>> end of the series. Where are MemoryDeviceInfo with this union tag
>> created?
>
> From patch 6:
[...]
I messed around with git, and managed to confuse myself. Thanks for
your help!
next prev parent reply other threads:[~2023-07-25 8:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 10:12 [PATCH v6 0/6] Hyper-V Dynamic Memory Protocol driver (hv-balloon 🎈️) Maciej S. Szmigiero
2023-07-20 10:12 ` [PATCH v6 1/6] memory-device: Support empty memory devices Maciej S. Szmigiero
2023-07-20 10:12 ` [PATCH v6 2/6] memory-device: Drop size alignment check Maciej S. Szmigiero
2023-07-20 10:13 ` [PATCH v6 3/6] Add Hyper-V Dynamic Memory Protocol definitions Maciej S. Szmigiero
2023-07-20 10:13 ` [PATCH v6 4/6] qapi: Add HvBalloonDeviceInfo sub-type to MemoryDeviceInfo Maciej S. Szmigiero
2023-07-24 11:37 ` Markus Armbruster
2023-07-24 11:43 ` Maciej S. Szmigiero
2023-07-25 8:26 ` Markus Armbruster [this message]
2023-07-25 8:25 ` Markus Armbruster
2023-07-25 18:13 ` Maciej S. Szmigiero
2023-07-20 10:13 ` [PATCH v6 5/6] qapi: Add HV_BALLOON_STATUS_REPORT event Maciej S. Szmigiero
2023-07-25 8:04 ` Markus Armbruster
2023-07-25 18:13 ` Maciej S. Szmigiero
2023-07-20 10:13 ` [PATCH v6 6/6] Add a Hyper-V Dynamic Memory Protocol driver (hv-balloon) Maciej S. Szmigiero
2023-07-24 10:56 ` [PATCH v6 0/6] Hyper-V Dynamic Memory Protocol driver (hv-balloon 🎈️) Markus Armbruster
2023-07-24 11:04 ` Maciej S. Szmigiero
2023-07-24 11:39 ` Markus Armbruster
2023-07-24 11:44 ` Maciej S. Szmigiero
2023-07-24 14:42 ` David Hildenbrand
2023-07-25 8:25 ` Markus Armbruster
2023-07-25 18:09 ` Maciej S. Szmigiero
2023-07-25 18:12 ` 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=87y1j4gzx8.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=david@redhat.com \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=mail@maciej.szmigiero.name \
--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 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.