On 08.04.2020 22:26, Roman Kagan wrote:
> On Tue, Apr 07, 2020 at 09:03:05PM +0200, Maciej S. Szmigiero wrote:
>> On 07.04.2020 20:56, Roman Kagan wrote:
>>> On Mon, Apr 06, 2020 at 11:20:39AM +0300, Jon Doron wrote:
>>>> Well I want it to be merged in :-)
>&
On 07.04.2020 20:56, Roman Kagan wrote:
> On Mon, Apr 06, 2020 at 11:20:39AM +0300, Jon Doron wrote:
>> Well I want it to be merged in :-)
>
> Hmm I'm curious why, it has little to offer over virtio.
>
> Anyway the series you've posted seems to be based on a fairly old
> version.
>
> The one in
Do you think you have a more recent version I dont mind diffing and
>> resubmitting a new version of the patchset?
>>
>> Thanks,
>> -- Jon.
>>
>> On Fri, Apr 3, 2020 at 5:56 PM Maciej S. Szmigiero
>> wrote:
>>>
>>> Hi Jon,
>>>
>&
Hi Jon,
On 03.04.2020 16:23, Jon Doron wrote:
> Guest OS uses ACPI to discover vmbus presence. Add a corresponding
> entry to DSDT in case vmbus has been enabled.
>
> Experimentally Windows guests were found to require this entry to
> include two IRQ resources, so this patch adds two
then please also add:
"Signed-off-by: Maciej S. Szmigiero ".
Thanks for the effort,
Maciej
On 03.04.2020 17:30, Jon Doron wrote:
> Thank you Maciej it seems like your version is really ahead I'll do
> the required work and merge it so i can submit a v2 with the latest
> patchset from
It seems to me that Roman might not be getting our e-mails since his
new e-mail address seems to be "rvka...@yandex-team.ru".
@Roman, are you with us?
Thanks,
Maciej
On 03.04.2020 19:18, Maciej S. Szmigiero wrote:
> Hi Jon,
>
> The patches are available here:
&
On 05.05.2020 17:38, Jon Doron wrote:
> On 05/05/2020, Igor Mammedov wrote:
>
> I dont know what were the original intentions of the original patch authors
> (at this point I simply rebased it, and to be honest I did not need this
> patch to get where I was going to, but it was part of the
Hi Eduardo,
On 09.10.2020 21:39, Eduardo Habkost wrote:
> Hi,
>
> I've just stumbled upon hw/hyperv/vmbus.c and I'm a bit confused:
> I haven't found any subclasses of the abstract type
> TYPE_VMBUS_DEVICE in the QEMU tree.
>
> I see a few patches in qemu-devel implementing a few vmbus
>
On 09.10.2020 22:07, Eduardo Habkost wrote:
> Having properties registered conditionally makes QOM type
> introspection difficult. Instead of skipping registration of the
> "instanceid" property, always register the property but validate
> its value against the instance id required by the class.
On 20.09.2020 15:25, Maciej S. Szmigiero wrote:
> From: "Maciej S. Szmigiero"
>
> The get_vmstate_memory_region() method from PCDIMMDeviceClass is only
> ever called from this class and is never overridden, so it can be converted
> into an ordinary function.
>
On 09.10.2020 23:33, Eduardo Habkost wrote:
> On Fri, Oct 09, 2020 at 11:05:47PM +0200, Maciej S. Szmigiero wrote:
>> On 09.10.2020 22:07, Eduardo Habkost wrote:
>>> Having properties registered conditionally makes QOM type
>>> introspection difficult. Inste
has to support rather big guests, up to 1 TB of RAM, so
performance-related things are important.
Further answers are bellow.
On 21.09.2020 11:10, David Hildenbrand wrote:
> On 20.09.20 15:25, Maciej S. Szmigiero wrote:
>> From: "Maciej S. Szmigiero"
>>
>> Thi
On 23.09.2020 14:48, David Hildenbrand wrote:
(...)
>>
>> I know that this a source of significant hot removal slowdown, especially
>> when a "ripple effect" happens on removal:
>> 1) There are 3 extra DIMMs plugged into the guest: A, B, C.
>>A and B are nearly empty, but C is nearly full.
>>
On 22.09.2020 09:26, David Hildenbrand wrote:
> On 22.09.20 00:22, Maciej S. Szmigiero wrote:
>> Hi David,
>>
>> Thank you for your comments.
>>
(...)
>>
>> The idea is to use virtual DIMM sticks for hot-adding extra memory at
>> runtime, while using b
From: "Maciej S. Szmigiero"
This device works like a virtual DIMM stick: it allows inserting extra RAM
into the guest at run time.
The main differences from the ACPI-based PC DIMM hotplug are:
* Notifying the guest about the new memory range is not done via ACPI but
via a protoc
From: "Maciej S. Szmigiero"
This driver is like virtio-balloon on steroids: it allows both changing the
guest memory allocation via ballooning and inserting extra RAM into it by
adding haprot virtual DIMM sticks.
One of advantages of these over ACPI-based PC DIMM hotplug is that such
From: "Maciej S. Szmigiero"
This commit adds Hyper-V Dynamic Memory Protocol definitions, taken
from hv_balloon Linux kernel driver, adapted to the QEMU coding style and
definitions.
Signed-off-by: Maciej S. Szmigiero
---
include/hw/hyperv/dynmem-pro
From: "Maciej S. Szmigiero"
The get_vmstate_memory_region() method from PCDIMMDeviceClass is only
ever called from this class and is never overridden, so it can be converted
into an ordinary function.
Signed-off-by: Maciej S. Szmigiero
---
hw/mem/pc-dimm.c
From: "Maciej S. Szmigiero"
This series adds a Hyper-V Dynamic Memory Protocol driver (hv-balloon)
and its protocol definitions.
Also included is a driver providing backing devices for memory hot-add
protocols ("haprots").
A haprot device works like a virtual DIMM stick:
On 15.06.2020 04:40, Jon Doron wrote:
> On 14/06/2020, Maciej S. Szmigiero wrote:
>> Hi Jon,
>>
>> On 14.06.2020 16:11, Jon Doron wrote:
>>> On 28/05/2020, Jon Doron wrote:
>>>> On 28/05/2020, Igor Mammedov wrote:
>>>>> On Thu, 28 May 2020
Hi Jon,
On 14.06.2020 16:11, Jon Doron wrote:
> On 28/05/2020, Jon Doron wrote:
>> On 28/05/2020, Igor Mammedov wrote:
>>> On Thu, 28 May 2020 08:26:42 +0300
>>> Jon Doron wrote:
>>>
On 22/05/2020, Igor Mammedow wrote:
> On Thu, 21 May 2020 18:02:07 +0200
> Paolo Bonzini wrote:
Hi Thomas,
On 03.06.2021 12:41, Thomas Huth wrote:
I accidentally came accross vmstate_vmbus_dev and noticed that
it is currently not used at all ... wire it up and make it
static, since it is only used in one file.
Thomas Huth (2):
hw/hyperv/vmbus: Wire up vmstate_vmbus_dev
From: "Maciej S. Szmigiero"
The get_vmstate_memory_region() method from PCDIMMDeviceClass is only
ever called from this class and is never overridden, so it can be converted
into an ordinary function.
This saves us from having to do an indirect call in order to reach it.
Signed-off-by
On 11.10.2020 01:30, Maciej S. Szmigiero wrote:
On 09.10.2020 23:33, Eduardo Habkost wrote:
On Fri, Oct 09, 2020 at 11:05:47PM +0200, Maciej S. Szmigiero wrote:
On 09.10.2020 22:07, Eduardo Habkost wrote:
Having properties registered conditionally makes QOM type
introspection difficult
From: "Maciej S. Szmigiero"
This way there is at least some contact point for incoming patches.
We'll see whether the code still gets just a random patch a few times
a year or whether it requires a permanent maintainer to take care of it.
Signed-off-by: Maciej S. Szmigiero
---
M
On 08.11.2021 08:30, Philippe Mathieu-Daudé wrote:
On 11/6/21 20:28, Maciej S. Szmigiero wrote:
On 06.11.2021 14:41, Philippe Mathieu-Daudé wrote:
This is the 4th time I send this patch. Is the VMBus infrastructure
used / maintained? Should we deprecate & remove?
$ ./scr
On 12.11.2021 21:39, Roman Kagan wrote:
On Fri, Nov 12, 2021 at 09:32:31PM +0300, Vladimir Sementsov-Ogievskiy wrote:
Add Den and Roman (his new address)
Thanks, I missed it on the list indeed.
06.11.2021 16:41, Philippe Mathieu-Daudé wrote:
This is the 4th time I send this patch. Is the
o me, so for it:
Reviewed-by: Maciej S. Szmigiero
Thanks,
Maciej
[1]: https://lore.kernel.org/qemu-devel/20201009193919.gf7...@habkost.net/T/#u
On 17.02.2022 14:45, Chao Peng wrote:
On Tue, Jan 25, 2022 at 09:20:39PM +0100, Maciej S. Szmigiero wrote:
On 18.01.2022 14:21, Chao Peng wrote:
KVM_MEM_PRIVATE is not exposed by default but architecture code can turn
on it by implementing kvm_arch_private_memory_supported().
Also private
On 23.02.2022 13:00, Chao Peng wrote:
On Tue, Feb 22, 2022 at 02:16:46AM +0100, Maciej S. Szmigiero wrote:
On 17.02.2022 14:45, Chao Peng wrote:
On Tue, Jan 25, 2022 at 09:20:39PM +0100, Maciej S. Szmigiero wrote:
On 18.01.2022 14:21, Chao Peng wrote:
KVM_MEM_PRIVATE is not exposed
On 18.01.2022 14:21, Chao Peng wrote:
KVM_MEM_PRIVATE is not exposed by default but architecture code can turn
on it by implementing kvm_arch_private_memory_supported().
Also private memslot cannot be movable and the same file+offset can not
be mapped into different GFNs.
Signed-off-by: Yu
),
remove the check in memory_region_get_ram_discard_manager() and clarify
the doc.
Signed-off-by: David Hildenbrand
Reviewed-by: Maciej S. Szmigiero
Thanks,
Maciej
On 8.09.2023 16:21, David Hildenbrand wrote:
Let's add vhost_get_max_memslots().
Signed-off-by: David Hildenbrand
Reviewed-by: Maciej S. Szmigiero
Thanks,
Maciej
.
Signed-off-by: David Hildenbrand
Reviewed-by: Maciej S. Szmigiero
Thanks,
Maciej
On 8.09.2023 16:21, David Hildenbrand wrote:
We'll need the stub soon from memory device context.
While at it, use "unsigned int" as return value and place the
declaration next to kvm_get_free_memslots().
Signed-off-by: David Hildenbrand
Reviewed-by: Maciej S. Szmigiero
Thanks,
Maciej
ce for
our device memory and register a memory listener (add/remove) for that
address space.
Signed-off-by: David Hildenbrand
Reviewed-by: Maciej S. Szmigiero
Thanks,
Maciej
Hildenbrand
Reviewed-by: Maciej S. Szmigiero
Thanks,
Maciej
.
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: David Hildenbrand
Reviewed-by: Maciej S. Szmigiero
Thanks,
Maciej
On 8.09.2023 16:21, David Hildenbrand wrote:
We want to place non-qmp stubs in there, so let's rename it. While at
it, put it into the MAINTAINERS file under "Memory devices".
Signed-off-by: David Hildenbrand
Reviewed-by: Maciej S. Szmigiero
Thanks,
Maciej
Reviewed-by: Maciej S. Szmigiero
Thanks,
Maciej
t to make it any worse.So let's keep it simple
and simply reject plugging such vhost devices in such a configuration.
Eventually, all vhost devices that want to be fully compatible with such
memory devices should support a decent number of memslots (>= 509).
Signed-off-by: David Hildenbrand
---
Re
memslot metadata is no longer an
issue, we could simply stop optimizing for that. Migration source and
destination can differ on the setting of "multiple-memslots".
Signed-off-by: David Hildenbrand
---
Reviewed-by: Maciej S. Szmigiero
Hope this patch was well-tested, especially on corn
From: "Maciej S. Szmigiero"
Used by the hv-balloon driver for (optional) guest memory status reports.
Signed-off-by: Maciej S. Szmigiero
---
hw/hyperv/hv-balloon.c | 31 +++-
monitor/monitor.c | 1 +
qapi/machine.json
From: "Maciej S. Szmigiero"
Used by the driver to report its provided memory state information.
Co-developed-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
hw/core/machine-hmp-cmds.c | 15 +++
hw/hyperv/hv-balloon.c | 27 ++
From: David Hildenbrand
Let's support empty memory devices -- memory devices that don't have a
memory device region in the current configuration. hv-balloon with an
optional memdev is the primary use case.
Signed-off-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
hw/mem/memory
From: "Maciej S. Szmigiero"
Add the necessary plumbing for the hv-balloon driver to the PC machine.
Co-developed-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
hw/i386/Kconfig | 1 +
hw/i386/pc.c| 22 ++
2 files changed, 23 insertions(+)
From: David Hildenbrand
There is no strong requirement that the size has to be multiples of the
requested alignment, let's drop it. This is a preparation for hv-baloon.
Signed-off-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
hw/mem/memory-device.c | 6 --
1 file changed
From: "Maciej S. Szmigiero"
This driver is like virtio-balloon on steroids: it allows both changing the
guest memory allocation via ballooning and inserting pieces of extra RAM
into it on demand from a provided memory backend.
One of advantages of these over ACPI-based PC DI
From: "Maciej S. Szmigiero"
This is a continuation of the v6 of the patch series located here:
https://lore.kernel.org/qemu-devel/cover.1689786474.git.maciej.szmigi...@oracle.com/
Changes from v6:
* Split the hv-balloon driver implementation into multiple files holding
parti
From: "Maciej S. Szmigiero"
This commit adds Hyper-V Dynamic Memory Protocol definitions, taken
from hv_balloon Linux kernel driver, adapted to the QEMU coding style and
definitions.
Signed-off-by: Maciej S. Szmigiero
---
include/hw/hyperv/dynmem-pro
On 2.11.2023 14:50, David Hildenbrand wrote:
On 23.10.23 19:24, Maciej S. Szmigiero wrote:
From: "Maciej S. Szmigiero"
This is a continuation of the v7 of the patch series located here:
https://lore.kernel.org/qemu-devel/cover.1693240836.git.maciej.szmigi...@oracle.com/
I skimmed
From: "Maciej S. Szmigiero"
The following changes since commit d762bf97931b58839316b68a570eecc6143c9e3e:
Merge tag 'pull-target-arm-20231102' of
https://git.linaro.org/people/pmaydell/qemu-arm into staging (2023-11-03
10:04:12 +0800)
are available in the Git repository at
From: "Maciej S. Szmigiero"
This driver is like virtio-balloon on steroids: it allows both changing the
guest memory allocation via ballooning and (in the next patch) inserting
pieces of extra RAM into it on demand from a provided memory backend.
The actual resizing is done via
From: "Maciej S. Szmigiero"
One of advantages of using this protocol over ACPI-based PC DIMM hotplug is
that it allows hot-adding memory in much smaller granularity because the
ACPI DIMM slot limit does not apply.
In order to enable this functionality a new memory backend needs to
From: David Hildenbrand
Let's support empty memory devices -- memory devices that don't have a
memory device region in the current configuration. hv-balloon with an
optional memdev is the primary use case.
Signed-off-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
hw/mem/memory
From: David Hildenbrand
There is no strong requirement that the size has to be multiples of the
requested alignment, let's drop it. This is a preparation for hv-baloon.
Signed-off-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
hw/mem/memory-device.c | 6 --
1 file changed
From: "Maciej S. Szmigiero"
This commit adds Hyper-V Dynamic Memory Protocol definitions, taken
from hv_balloon Linux kernel driver, adapted to the QEMU coding style and
definitions.
Acked-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
include/hw/hyperv/dynmem-pro
From: "Maciej S. Szmigiero"
Used by the hv-balloon driver for (optional) guest memory status reports.
Acked-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
hw/hyperv/hv-balloon.c | 30 +++-
monitor/monitor.c | 1 +
qapi/machine.json
From: "Maciej S. Szmigiero"
Used by the driver to report its provided memory state information.
Co-developed-by: David Hildenbrand
Reviewed-by: David Hildenbrand
Acked-by: Markus Armbruster
Signed-off-by: Maciej S. Szmigiero
---
hw/core/machine-hmp-cmds.c | 15 +++
hw
From: "Maciej S. Szmigiero"
Acked-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 8e8a7d5be5de..d4a480ce5a62 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2656,6 +26
From: "Maciej S. Szmigiero"
Add the necessary plumbing for the hv-balloon driver to the PC machine.
Co-developed-by: David Hildenbrand
Reviewed-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
hw/i386/Kconfig | 1 +
hw/i386/pc.c| 22 ++
2 fil
On 26.10.2023 11:31, Анастасия Любимова wrote:
28/09/23 19:18, Maciej S. Szmigiero пишет:
On 28.09.2023 15:25, Anastasia Belova wrote:
cpu_physical_memory_map may return NULL in hyperv_hcall_post_message.
Add check for NULL to avoid NULL-dereference.
Found by Linux Verification Center
On 6.11.2023 02:33, Stefan Hajnoczi wrote:
On Sun, 5 Nov 2023 at 19:49, Maciej S. Szmigiero
wrote:
From: "Maciej S. Szmigiero"
The following changes since commit d762bf97931b58839316b68a570eecc6143c9e3e:
Merge tag 'pull-target-arm-20231102' of
https://git.linaro.org/peopl
From: David Hildenbrand
There is no strong requirement that the size has to be multiples of the
requested alignment, let's drop it. This is a preparation for hv-baloon.
Signed-off-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
hw/mem/memory-device.c | 6 --
1 file changed
From: "Maciej S. Szmigiero"
Hi Stefan,
Fixed the CI pipeline issues with yesterday's pull request, and:
the following changes since commit d762bf97931b58839316b68a570eecc6143c9e3e:
Merge tag 'pull-target-arm-20231102' of
https://git.linaro.org/people/pmaydell/qemu-arm into stagin
From: "Maciej S. Szmigiero"
Used by the driver to report its provided memory state information.
Co-developed-by: David Hildenbrand
Reviewed-by: David Hildenbrand
Acked-by: Markus Armbruster
Signed-off-by: Maciej S. Szmigiero
---
hw/core/machine-hmp-cmds.c | 15 +++
hw
From: "Maciej S. Szmigiero"
Used by the hv-balloon driver for (optional) guest memory status reports.
Acked-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
hw/hyperv/hv-balloon-stub.c | 19
hw/hyperv/hv-balloon.c | 30 +-
hw/hyperv/m
From: "Maciej S. Szmigiero"
Add the necessary plumbing for the hv-balloon driver to the PC machine.
Co-developed-by: David Hildenbrand
Reviewed-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
hw/i386/Kconfig | 1 +
hw/i386/pc.c| 22 ++
2 fil
From: David Hildenbrand
Let's support empty memory devices -- memory devices that don't have a
memory device region in the current configuration. hv-balloon with an
optional memdev is the primary use case.
Signed-off-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
hw/mem/memory
From: "Maciej S. Szmigiero"
This commit adds Hyper-V Dynamic Memory Protocol definitions, taken
from hv_balloon Linux kernel driver, adapted to the QEMU coding style and
definitions.
Acked-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
include/hw/hyperv/dynmem-pro
From: "Maciej S. Szmigiero"
One of advantages of using this protocol over ACPI-based PC DIMM hotplug is
that it allows hot-adding memory in much smaller granularity because the
ACPI DIMM slot limit does not apply.
In order to enable this functionality a new memory backend needs to
From: "Maciej S. Szmigiero"
This reverts commit 5960f254dbb46f0c7a9f5f44bf4d27c19c34cb97 since the
previous commit made this situation possible again.
Signed-off-by: Maciej S. Szmigiero
---
hw/virtio/virtio-pmem.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff
From: "Maciej S. Szmigiero"
This driver is like virtio-balloon on steroids: it allows both changing the
guest memory allocation via ballooning and (in the next patch) inserting
pieces of extra RAM into it on demand from a provided memory backend.
The actual resizing is done via
From: "Maciej S. Szmigiero"
Acked-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 8e8a7d5be5de..d4a480ce5a62 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2656,6 +26
On 25.09.2023 13:49, Markus Armbruster wrote:
"Maciej S. Szmigiero" writes:
From: "Maciej S. Szmigiero"
Used by the hv-balloon driver for (optional) guest memory status reports.
Signed-off-by: Maciej S. Szmigiero
[...]
static void hv_balloon_handle_unballoo
On 28.09.2023 18:56, Alex Bennée wrote:
Anastasia Belova writes:
cpu_physical_memory_map may return NULL in hyperv_hcall_post_message.
Add check for NULL to avoid NULL-dereference.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
Fixes: 76036a5fc7 ("hyperv: process
ic int virtio_mem_prealloc_range_cb(VirtIOMEM *vmem, void *arg,
uint64_t offset, uint64_t size)
{
void *area = memory_region_get_ram_ptr(>memdev->mr) + offset;
Reviewed-by: Maciej S. Szmigiero
Thanks,
Maciej
On 28.09.2023 15:25, Anastasia Belova wrote:
cpu_physical_memory_map may return NULL in hyperv_hcall_post_message.
Add check for NULL to avoid NULL-dereference.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
Fixes: 76036a5fc7 ("hyperv: process POST_MESSAGE hypercall")
d Hildenbrand
---
The changes seem reasonable, so:
Reviewed-by: Maciej S. Szmigiero
Thanks,
Maciej
ion_id)
return -EBUSY;
}
}
-return 0;
+
+post_load_bitmap:
+/* Finally, update any other state to be consistent with the new bitmap. */
+return virtio_mem_post_load_bitmap(vmem);
}
typedef struct VirtIOMEMMigSanityChecks {
Reviewed-by: Maciej S. Szm
On 18.10.2023 10:00, David Hildenbrand wrote:
On 28.08.23 18:48, Maciej S. Szmigiero wrote:
From: "Maciej S. Szmigiero"
This is a continuation of the v6 of the patch series located here:
https://lore.kernel.org/qemu-devel/cover.1689786474.git.maciej.szmigi...@oracle.com/
Chang
From: David Hildenbrand
Let's support empty memory devices -- memory devices that don't have a
memory device region in the current configuration. hv-balloon with an
optional memdev is the primary use case.
Signed-off-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
hw/mem/memory
From: "Maciej S. Szmigiero"
Used by the hv-balloon driver for (optional) guest memory status reports.
Signed-off-by: Maciej S. Szmigiero
---
hw/hyperv/hv-balloon.c | 30 +++-
monitor/monitor.c | 1 +
qapi/machine.json
From: "Maciej S. Szmigiero"
Add the necessary plumbing for the hv-balloon driver to the PC machine.
Co-developed-by: David Hildenbrand
Reviewed-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
hw/i386/Kconfig | 1 +
hw/i386/pc.c| 22 ++
2 fil
From: "Maciej S. Szmigiero"
This driver is like virtio-balloon on steroids: it allows both changing the
guest memory allocation via ballooning and (in the next patch) inserting
pieces of extra RAM into it on demand from a provided memory backend.
The actual resizing is done via
From: "Maciej S. Szmigiero"
This is a continuation of the v7 of the patch series located here:
https://lore.kernel.org/qemu-devel/cover.1693240836.git.maciej.szmigi...@oracle.com/
Changes from v7:
* Rebase onto the current QEMU git master now that the David's memslots
patch series
From: David Hildenbrand
There is no strong requirement that the size has to be multiples of the
requested alignment, let's drop it. This is a preparation for hv-baloon.
Signed-off-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
hw/mem/memory-device.c | 6 --
1 file changed
From: "Maciej S. Szmigiero"
Signed-off-by: Maciej S. Szmigiero
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 9bd4fe378d46..6cab87700f82 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2602,6 +2602,14 @@ F: hw/usb/canokey.c
From: "Maciej S. Szmigiero"
This commit adds Hyper-V Dynamic Memory Protocol definitions, taken
from hv_balloon Linux kernel driver, adapted to the QEMU coding style and
definitions.
Acked-by: David Hildenbrand
Signed-off-by: Maciej S. Szmigiero
---
include/hw/hyperv/dynmem-pro
From: "Maciej S. Szmigiero"
One of advantages of using this protocol over ACPI-based PC DIMM hotplug is
that it allows hot-adding memory in much smaller granularity because the
ACPI DIMM slot limit does not apply.
In order to enable this functionality a new memory backend needs to
From: "Maciej S. Szmigiero"
Used by the driver to report its provided memory state information.
Co-developed-by: David Hildenbrand
Reviewed-by: David Hildenbrand
Acked-by: Markus Armbruster
Signed-off-by: Maciej S. Szmigiero
---
hw/core/machine-hmp-cmds.c | 15 +++
hw
9b1ee464 ("virtio-mem: Expose device memory dynamically via multiple
memslots if enabled")
Cc: Michael S. Tsirkin
Cc: Maciej S. Szmigiero
Signed-off-by: David Hildenbrand
---
Reviewed-by: Maciej S. Szmigiero
Thanks,
Maciej
On 9.11.2023 15:51, Peter Maydell wrote:
On Mon, 6 Nov 2023 at 14:23, Maciej S. Szmigiero
wrote:
From: "Maciej S. Szmigiero"
One of advantages of using this protocol over ACPI-based PC DIMM hotplug is
that it allows hot-adding memory in much smaller granularity because the
ACPI
From: "Maciej S. Szmigiero"
Since KVM commit 5f76f6f5ff96 ("KVM: nVMX: Do not expose MPX VMX controls when
guest MPX disabled")
it is not possible to disable MPX on a "-cpu host" just by adding "-mpx"
there if the host CPU does indeed support MPX.
QEMU
Message-Id: <20211106134155.582312-2-phi...@redhat.com>
[MSS: Remove also corresponding variables, which are now unused]
Signed-off-by: Maciej S. Szmigiero
---
hw/hyperv/vmbus.c | 99 ---
include/hw/hyperv/vmbus.h | 3 --
2 files changed, 102 de
for being picked up since
November last year.
Maciej S. Szmigiero (1):
MAINTAINERS: Add myself as the maintainer for Hyper-V VMBus
Philippe Mathieu-Daudé (1):
hw/hyperv/vmbus: Remove unused vmbus_load/save_req
From: "Maciej S. Szmigiero"
This way there is some contact point for incoming patches,
and somebody to review and pick up them.
Signed-off-by: Maciej S. Szmigiero
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index dff0200f70..
From: "Maciej S. Szmigiero"
Since KVM commit 5f76f6f5ff96 ("KVM: nVMX: Do not expose MPX VMX controls when
guest MPX disabled")
it is not possible to disable MPX on a "-cpu host" just by adding "-mpx"
there if the host CPU does indeed support MPX.
QEMU
On 21.05.2022 10:54, Paolo Bonzini wrote:
On Fri, May 20, 2022 at 8:33 PM Maciej S. Szmigiero
wrote:
From: "Maciej S. Szmigiero"
Since KVM commit 5f76f6f5ff96 ("KVM: nVMX: Do not expose MPX VMX controls when guest
MPX disabled")
it is not possible to disable MPX o
From: "Maciej S. Szmigiero"
Resetting a guest that has Hyper-V VMBus support enabled triggers a QEMU
assertion failure:
hw/hyperv/hyperv.c:131: synic_reset: Assertion
`QLIST_EMPTY(>sint_routes)' failed.
This happens both on normal guest reboot or when using "system_
1 - 100 of 206 matches
Mail list logo
