On 22.06.2023 20:45, Maciej S. Szmigiero wrote:
On 22.06.2023 14:52, David Hildenbrand wrote:
On 22.06.23 14:14, Maciej S. Szmigiero wrote:
On 22.06.2023 14:06, David Hildenbrand wrote:
On 22.06.23 13:17, Maciej S. Szmigiero wrote:
On 22.06.2023 13:15, David Hildenbrand wrote:
On 22.06.23
On 22.06.23 20:45, Maciej S. Szmigiero wrote:
On 22.06.2023 14:52, David Hildenbrand wrote:
On 22.06.23 14:14, Maciej S. Szmigiero wrote:
On 22.06.2023 14:06, David Hildenbrand wrote:
On 22.06.23 13:17, Maciej S. Szmigiero wrote:
On 22.06.2023 13:15, David Hildenbrand wrote:
On 22.06.23
On 22.06.2023 14:52, David Hildenbrand wrote:
On 22.06.23 14:14, Maciej S. Szmigiero wrote:
On 22.06.2023 14:06, David Hildenbrand wrote:
On 22.06.23 13:17, Maciej S. Szmigiero wrote:
On 22.06.2023 13:15, David Hildenbrand wrote:
On 22.06.23 13:12, Maciej S. Szmigiero wrote:
On 22.06.2023
On 22.06.23 14:14, Maciej S. Szmigiero wrote:
On 22.06.2023 14:06, David Hildenbrand wrote:
On 22.06.23 13:17, Maciej S. Szmigiero wrote:
On 22.06.2023 13:15, David Hildenbrand wrote:
On 22.06.23 13:12, Maciej S. Szmigiero wrote:
On 22.06.2023 13:01, David Hildenbrand wrote:
[...]
We'd
On 22.06.2023 14:14, Maciej S. Szmigiero wrote:
On 22.06.2023 14:06, David Hildenbrand wrote:
On 22.06.23 13:17, Maciej S. Szmigiero wrote:
On 22.06.2023 13:15, David Hildenbrand wrote:
On 22.06.23 13:12, Maciej S. Szmigiero wrote:
On 22.06.2023 13:01, David Hildenbrand wrote:
[...]
We'd
On 22.06.2023 14:06, David Hildenbrand wrote:
On 22.06.23 13:17, Maciej S. Szmigiero wrote:
On 22.06.2023 13:15, David Hildenbrand wrote:
On 22.06.23 13:12, Maciej S. Szmigiero wrote:
On 22.06.2023 13:01, David Hildenbrand wrote:
[...]
We'd use a memory region container as device memory
On 22.06.23 13:17, Maciej S. Szmigiero wrote:
On 22.06.2023 13:15, David Hildenbrand wrote:
On 22.06.23 13:12, Maciej S. Szmigiero wrote:
On 22.06.2023 13:01, David Hildenbrand wrote:
[...]
We'd use a memory region container as device memory region (like [1]) and would
have to handle the
On 22.06.2023 13:15, David Hildenbrand wrote:
On 22.06.23 13:12, Maciej S. Szmigiero wrote:
On 22.06.2023 13:01, David Hildenbrand wrote:
[...]
We'd use a memory region container as device memory region (like [1]) and would
have to handle the !memdev case (I can help with that). > Into
On 22.06.23 13:12, Maciej S. Szmigiero wrote:
On 22.06.2023 13:01, David Hildenbrand wrote:
[...]
We'd use a memory region container as device memory region (like [1]) and would
have to handle the !memdev case (I can help with that). > Into that, you can
map the RAM memory region on demand
On 22.06.2023 13:01, David Hildenbrand wrote:
[...]
We'd use a memory region container as device memory region (like [1]) and would
have to handle the !memdev case (I can help with that). > Into that, you can
map the RAM memory region on demand (and eventually even using multiple slots like
[...]
We'd use a memory region container as device memory region (like [1]) and would
have to handle the !memdev case (I can help with that). > Into that, you can
map the RAM memory region on demand (and eventually even using multiple slots like
[1]).
(2) Use a single virtual DIMM and
On 21.06.2023 12:32, David Hildenbrand wrote:
On 20.06.23 22:13, Maciej S. Szmigiero wrote:
On 19.06.2023 17:58, David Hildenbrand wrote:
[...]
Sorry for the late reply!
Still trying to make up my mind what the right way forward with this is.
This usage is still problematic I suspect
On 20.06.23 22:13, Maciej S. Szmigiero wrote:
On 19.06.2023 17:58, David Hildenbrand wrote:
[...]
Sorry for the late reply!
Still trying to make up my mind what the right way forward with this is.
This usage is still problematic I suspect (well, and a layer violation
regarding the
On 19.06.2023 17:58, David Hildenbrand wrote:
[...]
Sorry for the late reply!
Still trying to make up my mind what the right way forward with this is.
This usage is still problematic I suspect (well, and a layer violation
regarding the machine). The machine hotplug handler is supposed to
[...]
Sorry for the late reply!
Still trying to make up my mind what the right way forward with this is.
This usage is still problematic I suspect (well, and a layer violation
regarding the machine). The machine hotplug handler is supposed to call the
pre_plug/plug/unplug hooks as response
On 12.06.2023 19:42, David Hildenbrand wrote:
On 12.06.23 16:00, Maciej S. Szmigiero wrote:
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
On 12.06.23 16:00, Maciej S. Szmigiero wrote:
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
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 DIMM hotplug is that
18 matches
Mail list logo
