diff options
author | David Hildenbrand <david@redhat.com> | 2020-11-12 16:37:57 +0300 |
---|---|---|
committer | Michael S. Tsirkin <mst@redhat.com> | 2020-12-19 00:14:26 +0300 |
commit | 989ff82527074b79bc89ba1c390be1eda01784a5 (patch) | |
tree | 2f1af38c9dba0fa7aa3a87170c42c19d6cef45fa /drivers/virtio/virtio_balloon.c | |
parent | f2d799d591359685a3a74d28c2989c56f4bb9898 (diff) | |
download | linux-989ff82527074b79bc89ba1c390be1eda01784a5.tar.xz |
virtio-mem: generalize check for added memory
Let's check by traversing busy system RAM resources instead, to avoid
relying on memory block states.
Don't use walk_system_ram_range(), as that works on pages and we want to
use the bare addresses we have easily at hand.
This is a preparation for Big Block Mode (BBM), which won't have memory
block states.
Reviewed-by: Wei Yang <richard.weiyang@linux.alibaba.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
Signed-off-by: David Hildenbrand <david@redhat.com>
Link: https://lore.kernel.org/r/20201112133815.13332-12-david@redhat.com
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'drivers/virtio/virtio_balloon.c')
0 files changed, 0 insertions, 0 deletions