Searched hist:"082851 a3af1450fa714e9a0a3ca7cb4b9dbd8855" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/qemu/util/ |
| H A D | vfio-helpers.c | diff 082851a3af1450fa714e9a0a3ca7cb4b9dbd8855 Thu Apr 29 06:26:59 CDT 2021 David Hildenbrand <david@redhat.com> util: vfio-helpers: Factor out and fix processing of existing ram blocks
Factor it out into common code when a new notifier is registered, just
as done with the memory region notifier. This keeps logic about how to
process existing ram blocks at a central place.
Just like when adding a new ram block, we have to register the max_length.
Ram blocks are only "fake resized". All memory (max_length) is mapped.
Print the warning from inside qemu_vfio_ram_block_added().
Reviewed-by: Peter Xu <peterx@redhat.com>
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20210429112708.12291-2-david@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
|
| /openbmc/qemu/hw/core/ |
| H A D | numa.c | diff 082851a3af1450fa714e9a0a3ca7cb4b9dbd8855 Thu Apr 29 06:26:59 CDT 2021 David Hildenbrand <david@redhat.com> util: vfio-helpers: Factor out and fix processing of existing ram blocks
Factor it out into common code when a new notifier is registered, just
as done with the memory region notifier. This keeps logic about how to
process existing ram blocks at a central place.
Just like when adding a new ram block, we have to register the max_length.
Ram blocks are only "fake resized". All memory (max_length) is mapped.
Print the warning from inside qemu_vfio_ram_block_added().
Reviewed-by: Peter Xu <peterx@redhat.com>
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20210429112708.12291-2-david@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
|
| /openbmc/qemu/include/exec/ |
| H A D | cpu-common.h | diff 082851a3af1450fa714e9a0a3ca7cb4b9dbd8855 Thu Apr 29 06:26:59 CDT 2021 David Hildenbrand <david@redhat.com> util: vfio-helpers: Factor out and fix processing of existing ram blocks
Factor it out into common code when a new notifier is registered, just
as done with the memory region notifier. This keeps logic about how to
process existing ram blocks at a central place.
Just like when adding a new ram block, we have to register the max_length.
Ram blocks are only "fake resized". All memory (max_length) is mapped.
Print the warning from inside qemu_vfio_ram_block_added().
Reviewed-by: Peter Xu <peterx@redhat.com>
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20210429112708.12291-2-david@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
|