diff options
| author | David Hildenbrand <david@redhat.com> | 2021-04-29 13:26:59 +0200 |
|---|---|---|
| committer | Dr. David Alan Gilbert <dgilbert@redhat.com> | 2021-05-13 18:21:13 +0100 |
| commit | 082851a3af1450fa714e9a0a3ca7cb4b9dbd8855 (patch) | |
| tree | 5cd7eff8cac6a7d26860aca1cc5a04acb739f73b /crypto/pbkdf-gcrypt.c | |
| parent | 372043f389126bf6bb4ba88b970f3dfcaf86b722 (diff) | |
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>
Diffstat (limited to 'crypto/pbkdf-gcrypt.c')
0 files changed, 0 insertions, 0 deletions