hw/virtio/vhost: re-factor vhost-section and allow DIRTY_MEMORY_CODE
commit083b9bd7a1c526d57ec17b23dd6eca414e808886
authorAlex Bennée <alex.bennee@linaro.org>
Fri, 5 Jun 2020 15:49:25 +0000 (5 16:49 +0100)
committerAlex Bennée <alex.bennee@linaro.org>
Mon, 8 Jun 2020 16:04:19 +0000 (8 17:04 +0100)
tree42f2a6bce5b47f9ca47b392015202716f491b853
parenta97098844b9e4d2d1c3a24f66b8e2c7f97b3a795
hw/virtio/vhost: re-factor vhost-section and allow DIRTY_MEMORY_CODE

The purpose of vhost_section is to identify RAM regions that need to
be made available to a vhost client. However when running under TCG
all RAM sections have DIRTY_MEMORY_CODE set which leads to problems
down the line.

Re-factor the code so:

  - steps are clearer to follow
  - reason for rejection is recorded in the trace point
  - we allow DIRTY_MEMORY_CODE

We expand the comment to explain that kernel based vhost has specific
support for migration tracking.

Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Tested-by: Fabiano Rosas <farosas@linux.ibm.com>
Cc: Michael S. Tsirkin <mst@redhat.com>
Cc: Dr. David Alan Gilbert <dgilbert@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>
Message-Id: <20200605154929.26910-11-alex.bennee@linaro.org>
hw/virtio/trace-events
hw/virtio/vhost.c