From: "Dr. David Alan Gilbert"
Add the meat of update_mem_cb; this is called for each region,
to add a region to our temporary list.
Our temporary list is in order we look to see if this
region can be merged with the current head of list.
Signed-off-by: Dr. David Alan
From: "Dr. David Alan Gilbert"
Hi,
This patch set reworks the way the vhost code handles changes in
physical address space layout that came from a discussion with Igor.
Its intention is to simplify a lot of the update code,
and to make it easier for the postcopy+shared
From: "Dr. David Alan Gilbert"
Iterate through an address space calling a function for each
section. The iteration is done in order.
Signed-off-by: Dr. David Alan Gilbert
---
include/exec/memory.h | 23 +++
memory.c |
From: "Dr. David Alan Gilbert"
vhost_verify_ring_mappings() were used to verify that
rings are still accessible and related memory hasn't
been moved after flatview is updated.
It was doing checks by mapping ring's GPA+len and
checking that HVA hadn't changed with new memory
From: "Dr. David Alan Gilbert"
vhost_update_mem will replace the existing update mechanism.
They make use of the Flatview we have now to make the update simpler.
This commit just adds the basic structure.
Signed-off-by: Dr. David Alan Gilbert
---
From: "Dr. David Alan Gilbert"
Move the log_dirty check into vhost_section.
Signed-off-by: Dr. David Alan Gilbert
---
hw/virtio/trace-events | 3 +++
hw/virtio/vhost.c | 20 +---
2 files changed, 16 insertions(+), 7 deletions(-)
From: "Dr. David Alan Gilbert"
Compare the temporary region data with the original, and if it's
different update the original in the device state.
Signed-off-by: Dr. David Alan Gilbert
---
hw/virtio/trace-events | 2 ++
hw/virtio/vhost.c | 19
From: "Dr. David Alan Gilbert"
Remove the old update mechanism, vhost_set_memory, and the functions
it uses and the memory_changed flags we no longer use.
Signed-off-by: Dr. David Alan Gilbert
---
hw/virtio/vhost.c | 254
From: "Dr. David Alan Gilbert"
Move the maintenance of mem_sections into the vhost_update_mem routines,
this removes the need for the vhost_region_add/del callbacks.
Suggested-by: Igor Mammedov
(and mostly written by Igor!)
Signed-off-by: Dr. David
From: "Dr. David Alan Gilbert"
Mostly just manual conversion with very minor fixes.
Signed-off-by: Dr. David Alan Gilbert
---
docs/devel/{migration.txt => migration.rst} | 326 +++-
1 file changed, 176 insertions(+), 150
From: "Dr. David Alan Gilbert"
Iterate through an address space calling a function for each
section. The iteration is done in order.
Signed-off-by: Dr. David Alan Gilbert
---
include/exec/memory.h | 23 +++
memory.c |
From: "Dr. David Alan Gilbert"
Move the log_dirty check into vhost_section.
Signed-off-by: Dr. David Alan Gilbert
---
hw/virtio/trace-events | 3 +++
hw/virtio/vhost.c | 20 +---
2 files changed, 16 insertions(+), 7 deletions(-)
From: "Dr. David Alan Gilbert"
Hi,
This is an experimental set that reworks the way the vhost
code handles changes in physical address space layout that
came from a discussion with Igor.
It's intention is to simplify a lot of the update code,
and to make it easier for the
From: "Dr. David Alan Gilbert"
Add the meat of update_mem_cb; this is called for each region,
to add a region to our temporary list.
Our temporary list is in order we look to see if this
region can be merged with the current head of list.
Signed-off-by: Dr. David Alan
From: "Dr. David Alan Gilbert"
vhost_update_mem will replace the existing update mechanism.
They make use of the Flatview we have now to make the update simpler.
This commit just adds the basic structure.
Signed-off-by: Dr. David Alan Gilbert
---
From: "Dr. David Alan Gilbert"
vhost_verify_ring_mappings() were used to verify that
rings are still accessible and related memory hasn't
been moved after flatview is updated.
It were doing checks by mapping ring's GPA+len and
checking that HVA hasn't changed with new
From: "Dr. David Alan Gilbert"
Remove the old update mechanism, vhost_set_memory, and the functions
it uses and the memory_changed flags we no longer use.
Signed-off-by: Dr. David Alan Gilbert
---
hw/virtio/vhost.c | 254
From: "Dr. David Alan Gilbert"
Compare the temporary region data with the original, and if it's
different update the original in the device state.
Signed-off-by: Dr. David Alan Gilbert
---
hw/virtio/trace-events | 2 ++
hw/virtio/vhost.c | 19
From: "Dr. David Alan Gilbert"
Mvoe the maintenance of mem_sections into the vhost_update_mem routines,
this removes the need for the vhost_region_add/del callbacks.
Suggested-by: Igor Mammedov
(and mostly written by Igor!)
Signed-off-by: Dr. David
From: ZhiPeng Lu
Use hmp_handle_error instend of error_report_err to set error.
Signed-off-by: ZhiPeng Lu
Reviewed-by: Jiyun Fan
Message-Id: <1508411793-22868-1-git-send-email-lu.zhip...@zte.com.cn>
Reviewed-by: Philippe
From: Greg Kurz
If a CPU selected with the "cpu" command is hot-unplugged then "info cpus"
causes QEMU to exit:
(qemu) device_del cpu1
(qemu) info cpus
qemu:qemu_cpu_kick_thread: No such process
This happens because "cpu" stores the pointer to the selected CPU into
the monitor
From: "Dr. David Alan Gilbert"
The following changes since commit abf6e752e55b2f5afb48303429dea2db7c3a62de:
Merge remote-tracking branch 'remotes/borntraeger/tags/s390x-20171030' into
staging (2017-10-30 13:02:45 +)
are available in the Git repository at:
From: "Dr. David Alan Gilbert"
The response to a VHOST_USER_POSTCOPY_ADVISE contains a fd but doesn't
actually contain any data. FIx vu_message_write so that it doesn't
do a 0-byte write() call, since this was ending up with rc=0
that was confusing the error handling code.
From: "Dr. David Alan Gilbert"
Blank lines and comments as suggested by Eric.
Signed-off-by: Dr. David Alan Gilbert
---
qapi/migration.json | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/qapi/migration.json
From: "Dr. David Alan Gilbert"
Update the migration docs:
Among other changes:
* Added a general list of advice for device authors
* Reordered the section on conditional state (subsections etc)
into the order we prefer.
* Add a note about firmware
Signed-off-by:
From: Igor Mammedov
Commands query-chardev, query-version, query-name, query-uuid,
query-iothreads, query-memdev are informational and do not depend on
the machine being initialized. Make them available in preconfig
runstate to make the latter a little bit more useful.
The generic qom commands
From: "Dr. David Alan Gilbert"
Allow the 'help' command in preconfig state but
make it only list the preconfig commands.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
Reviewed-by: Igor Mammedov
---
hmp-commands.hx | 1 +
monitor.c | 8 +++-
2 files changed, 8
From: "Dr. David Alan Gilbert"
Don't show the commands that aren't available.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
Reviewed-by: Igor Mammedov
---
monitor.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/monitor.c b/monitor.c
index
From: "Dr. David Alan Gilbert"
Add the exit_preconfig command to return to normality.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
Reviewed-by: Igor Mammedov
---
hmp-commands.hx | 19 +++
hmp.c | 8
hmp.h | 1 +
3 files changed,
From: "Dr. David Alan Gilbert"
Reenable HMP in preconfig mode; it's pretty
easy and anyway I want to do a similar thing for OOB eventually.
We'll want to enable more commands in preconfig mode to make it
useful at some point.
Dave
v4
Fixes from Markus' review.
Including enabling some
From: "Dr. David Alan Gilbert"
Add a flag to command definitions to allow them to be used in preconfig
and check it.
If users try to use commands that aren't available, tell them to use
the exit_preconfig comand we're adding in a few patches.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by:
From: "Dr. David Alan Gilbert"
Allow a bunch of the info commands to be used in preconfig.
version, chardev, name, uuid,memdev, iothreads
Were enabled in QMP in the previous patch from Igor
status, hotpluggable_cpus
Was enabled in the original allow-preconfig series
history
is HMP
From: "Dr. David Alan Gilbert"
Now we can cope with preconfig in HMP, reenable by reverting
commit 71dc578e116599ea73c8a2a4e693134702ec0e83.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
Reviewed-by: Igor Mammedov
---
monitor.c | 6 --
1 file changed, 6 deletions(-)
diff
From: "Dr. David Alan Gilbert"
Add the exit_preconfig command to return to normality.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
Reviewed-by: Igor Mammedov
---
hmp-commands.hx | 15 +++
hmp.c | 7 +++
hmp.h | 1 +
3 files changed, 23
From: "Dr. David Alan Gilbert"
Don't show the commands that aren't available.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
Reviewed-by: Igor Mammedov
---
monitor.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/monitor.c b/monitor.c
index
From: Igor Mammedov
subj commands, are informational and do not depend on machine being
initialized. Make them available early in preconfig runstate to make
the later a little bit more useful.
Signed-off-by: Igor Mammedov
---
qapi/char.json | 3 ++-
qapi/misc.json | 12 +++-
2 files
From: "Dr. David Alan Gilbert"
Now we can cope with preconfig in HMP, reenable by reverting
commit 71dc578e116599ea73c8a2a4e693134702ec0e83.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
Reviewed-by: Igor Mammedov
---
monitor.c | 6 --
1 file changed, 6 deletions(-)
diff
From: "Dr. David Alan Gilbert"
Allow the 'help' command in preconfig state but
make it only list the preconfig commands.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
Reviewed-by: Igor Mammedov
---
hmp-commands.hx | 1 +
monitor.c | 8 +++-
2 files changed, 8
From: "Dr. David Alan Gilbert"
Reenable HMP in preconfig mode; it's pretty
easy and anyway I want to do a similar thing for OOB eventually.
We'll want to enable more commands in preconfig mode to make it
useful at some point.
Dave
v3
Add Igor's patch to enable most of the same info commands
From: "Dr. David Alan Gilbert"
Allow a bunch of the info commands to be used in preconfig.
version, chardev, name, uuid,memdev, iothreads
Were enabled in QMP in the previous patch from Igor
status, hotpluggable_cpus
Was enabled in the original allow-preconfig series
history
is HMP
From: "Dr. David Alan Gilbert"
Add a flag to command definitions to allow them to be used in preconfig
and check it.
If users try to use commands that aren't available, tell them to use
the exit_preconfig comand we're adding in a few patches.
Signed-off-by: Dr. David Alan Gilbert
---
From: "Dr. David Alan Gilbert"
Rate limiting sleeps the migration thread for a while when it runs
out of bandwidth; but sometimes we want to wake up to get on with
something more urgent (like a postcopy request). Here we use
a semaphore with a timedwait instead of a simple sleep; Incrementing
From: "Dr. David Alan Gilbert"
Limit the background transfer bandwidth during the postcopy
phase to the value set on this new parameter. The default, 0,
corresponds to the existing behaviour which is unlimited bandwidth.
Signed-off-by: Dr. David Alan Gilbert
---
hmp.c | 7
From: "Dr. David Alan Gilbert"
Use the 'urgent request' mechanism added in the previous patch
for entries added to the postcopy request queue for RAM. Ignore
the rate limiting while we have requests.
Signed-off-by: Dr. David Alan Gilbert
---
migration/ram.c | 9 -
1 file changed, 8
From: "Dr. David Alan Gilbert"
Hi,
Postcopy currently turns off bandwidth limits during the postcopy
phase to make sure the urgent postcopy requests aren't delayed.
This causes problems for larger clusters which share networking
between the migration stream and other critical services.
From: Greg Kurz
Since commit 83ee768d6247b, we now have two places that define the
QJSON type:
$ git grep 'typedef struct QJSON QJSON'
include/migration/vmstate.h:typedef struct QJSON QJSON;
migration/qjson.h:typedef struct QJSON QJSON;
This breaks docker-test-build@centos6:
In file included
From: "Dr. David Alan Gilbert"
Use the 'urgent request' mechanism added in the previous patch
for entries added to the postcopy request queue for RAM. Ignore
the rate limiting while we have requests.
Signed-off-by: Dr. David Alan Gilbert
Message-Id:
From: "Dr. David Alan Gilbert"
Rate limiting sleeps the migration thread for a while when it runs
out of bandwidth; but sometimes we want to wake up to get on with
something more urgent (like a postcopy request). Here we use
a semaphore with a timedwait instead of a simple sleep; Incrementing
From: "Dr. David Alan Gilbert"
Limit the background transfer bandwidth during the postcopy
phase to the value set on this new parameter. The default, 0,
corresponds to the existing behaviour which is unlimited bandwidth.
Signed-off-by: Dr. David Alan Gilbert
Message-Id:
From: Xiao Guangrong
Sync up xbzrle_cache_miss_prev only after migration iteration goes
forward
Signed-off-by: Xiao Guangrong
Message-Id: <20180604095520.8563-4-xiaoguangr...@tencent.com>
Reviewed-by: Dr. David Alan Gilbert
Signed-off-by: Dr. David Alan Gilbert
---
migration/ram.c | 2 +-
1
From: Balamuruhan S
expected_downtime value is not accurate with dirty_pages_rate * page_size,
using ram_bytes_remaining() would yeild it resonable.
consider to read the remaining ram just after having updated the dirty
pages count later migration_bitmap_sync_range() in migration_bitmap_sync()
From: Vladimir Sementsov-Ogievskiy
dirty_bitmap_load_header return code is obtained but not handled. Fix
this.
Bug was introduced in b35ebdf076d697bc
"migration: add postcopy migration of dirty bitmaps" with the whole
function.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Message-Id:
From: "Dr. David Alan Gilbert"
There are still a few cases where migration code is using the macros
and functions that do all RAMBlocks rather than just the migratable
blocks; fix those up.
Signed-off-by: Dr. David Alan Gilbert
Message-Id: <20180605162545.80778-2-dgilb...@redhat.com>
From: "Dr. David Alan Gilbert"
The following changes since commit 2702c2d3eb74e3908c0c5dbf3a71c8987595a86e:
Merge remote-tracking branch
'remotes/stsquad/tags/pull-travis-updates-140618-1' into staging (2018-06-15
12:49:36 +0100)
are available in the Git repository at:
From: Xiao Guangrong
It is used to slightly clean the code up, no logic is changed
Signed-off-by: Xiao Guangrong
Message-Id: <20180604095520.8563-5-xiaoguangr...@tencent.com>
Reviewed-by: Dr. David Alan Gilbert
Signed-off-by: Dr. David Alan Gilbert
---
migration/ram.c | 35
From: "Dr. David Alan Gilbert"
The migration code should be using the
RAMBLOCK_FOREACH_MIGRATABLE and qemu_ram_foreach_block_migratable
not the all-block versions; poison them so that we can't accidentally
use them.
Signed-off-by: Dr. David Alan Gilbert
Message-Id:
From: "Dr. David Alan Gilbert"
Allow a bunch of the info commands to be used in preconfig.
Could probably add most of them.
Signed-off-by: Dr. David Alan Gilbert
---
hmp-commands-info.hx | 9 +
hmp-commands.hx | 1 +
2 files changed, 10 insertions(+)
diff --git
From: "Dr. David Alan Gilbert"
Add a flag to command definitions to allow them to be used in preconfig
and check it.
Signed-off-by: Dr. David Alan Gilbert
---
monitor.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/monitor.c b/monitor.c
index 6d0cec552e..50b95f41db
From: "Dr. David Alan Gilbert"
Add the exit_preconfig command to return to normality.
Signed-off-by: Dr. David Alan Gilbert
---
hmp-commands.hx | 15 +++
hmp.c | 7 +++
hmp.h | 1 +
3 files changed, 23 insertions(+)
diff --git a/hmp-commands.hx
From: "Dr. David Alan Gilbert"
Allow the 'help' command in preconfig state but
make it only list the preconfig commands.
Signed-off-by: Dr. David Alan Gilbert
---
hmp-commands.hx | 1 +
monitor.c | 8 +++-
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/hmp-commands.hx
From: "Dr. David Alan Gilbert"
Reenable HMP in preconfig mode; it's pretty
easy and anyway I want to do a similar thing for OOB eventually.
We'll want to enable more commands in preconfig mode to make it
useful at some point.
Dave
Dr. David Alan Gilbert (6):
hmp: Add flag for preconfig
From: "Dr. David Alan Gilbert"
Now we can cope with preconfig in HMP, reenable by reverting
commit 71dc578e116599ea73c8a2a4e693134702ec0e83.
Signed-off-by: Dr. David Alan Gilbert
---
monitor.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/monitor.c b/monitor.c
index
From: "Dr. David Alan Gilbert"
Don't show the commands that aren't available.
Signed-off-by: Dr. David Alan Gilbert
---
monitor.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/monitor.c b/monitor.c
index 7d1709c225..9b29787a52 100644
--- a/monitor.c
+++
From: "Dr. David Alan Gilbert"
There are still a few cases where migration code is using the macros
and functions that do all RAMBlocks rather than just the migratable
blocks; fix those up.
Signed-off-by: Dr. David Alan Gilbert
---
migration/ram.c | 4 ++--
migration/rdma.c | 2 +-
2 files
From: "Dr. David Alan Gilbert"
The migration code should be using the
RAMBLOCK_FOREACH_MIGRATABLE and qemu_ram_foreach_block_migratable
not the all-block versions; poison them so that we can't accidentally
use them.
Signed-off-by: Dr. David Alan Gilbert
---
include/exec/ramlist.h | 4 +++-
From: "Dr. David Alan Gilbert"
Hi,
Cédric's b895de50 got merged at about the same
time as some of Peter's changes and there's a rdma
case as well; so tidy up those cases that were looping
over all (rather than just migratable) RAMBlocks
and poison it so we don't end up doing the same thing
From: "Dr. David Alan Gilbert"
Allow a bunch of the info commands to be used in preconfig.
Could probably add most of them.
Signed-off-by: Dr. David Alan Gilbert
---
hmp-commands-info.hx | 12
hmp-commands.hx | 1 +
2 files changed, 13 insertions(+)
diff --git
From: "Dr. David Alan Gilbert"
PPC tcg seems to be failing migration tests quite regularly;
we believe this is TCG bugs in dirty bit updating; it's
not clear why PPC fails more but lets skip for the moment.
$ ./tests/migration-test
/ppc64/migration/deprecated: OK
/ppc64/migration/bad_dest: SKIP
From: "Dr. David Alan Gilbert"
Use qemu_set_nonblock rather than a simple fcntl; cleaner
and I have no reason to change other flags.
Reported-by: Peter Maydell
Signed-off-by: Dr. David Alan Gilbert
---
hw/virtio/vhost-user.c
From: "Dr. David Alan Gilbert"
During a TLS connect we see:
migration_channel_connect calls
migration_tls_channel_connect
(calls after TLS setup)
migration_channel_connect
My previous error handling fix made migration_channel_connect
call migrate_fd_connect in all
From: "Dr. David Alan Gilbert"
Update the migration docs:
Among other changes:
* Added a general list of advice for device authors
* Reordered the section on conditional state (subsections etc)
into the order we prefer.
* Add a note about firmware
Signed-off-by:
From: "Dr. David Alan Gilbert"
Wait for a semaphore before completing the migration,
if the previously added capability was enabled.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
---
migration/migration.c | 38
From: "Dr. David Alan Gilbert"
When 'pause-before-switchover' is enabled, the outgoing migration
will pause before invalidating the block devices and serializing
the device state.
At this point the management layer gets the chance to clean up any
device jobs or other device
From: "Dr. David Alan Gilbert"
Hi,
This set attempts to make a race condition between migration and
drive-mirror (and other block users) soluble by allowing the migration
to be paused after the source qemu releases the block devices but
before the serialisation of the
From: "Dr. David Alan Gilbert"
Add two statuses for use when the 'pause-before-switchover'
capability is enabled.
'pre-switchover' is the state that we wait in for management
to allow us to continue.
'device' is the state we enter while serialising the devices
after
From: "Dr. David Alan Gilbert"
If a migration_cancel is issued during the new paused state,
kick the pause_sem to get to unpause so it can cancel.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
---
From: "Dr. David Alan Gilbert"
HMP equivalent to the just added migrate-continue
Unpause a migrate paused at a given state.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
---
hmp-commands.hx | 12
hmp.c
From: "Dr. David Alan Gilbert"
A new qmp command allows the caller to continue from a given
paused state.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
---
migration/migration.c | 11 +++
qapi/migration.json
From: "Dr. David Alan Gilbert"
Add pause-before-switchover support for postcopy.
After starting postcopy it will transition
active->pre-switchover->postcopy_active
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Peter Xu
---
From: "Dr. David Alan Gilbert"
Hi,
This is mainly the alignment change that Paolo asked for
in the 2nd commit, but while I was there I added some comments
and tracing that I've split out.
Dave
Dr. David Alan Gilbert (2):
find_ram_offset: Add comments and tracing
From: "Dr. David Alan Gilbert"
The dirty bitmaps are built from 'long'sand there is fast-path code
for synchronising the case where the RAMBlock is aligned to the start
of a long boundary. Align the allocation to this boundary
to cause the fast path to be used.
Offsets
From: "Dr. David Alan Gilbert"
Add some comments so I can understand the various nested loops.
Add some tracing so I can see what they're doing.
Signed-off-by: Dr. David Alan Gilbert
---
exec.c | 17 -
trace-events | 3 +++
2
From: "Dr. David Alan Gilbert"
Remove the old update mechanism, vhost_set_memory, and the functions
and flags it used.
Signed-off-by: Dr. David Alan Gilbert
---
hw/virtio/vhost.c | 251 --
From: "Dr. David Alan Gilbert"
Igor spotted that there's a race, where a region that's unref'd
in a _del callback might be free'd before the set_mem_table call in
the _commit callback, and thus the vhost might end up using free memory.
Fix this by building a complete
From: "Dr. David Alan Gilbert"
vhost_verify_ring_mappings() were used to verify that
rings are still accessible and related memory hasn't
been moved after flatview is updated.
It was doing checks by mapping ring's GPA+len and
checking that HVA hadn't changed with new memory
From: "Dr. David Alan Gilbert"
Now that the olf vhost_set_memory code is gone, the _nop and _add
callbacks are identical and can be merged. The _del callback is
no longer needed.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Igor Mammedov
From: "Dr. David Alan Gilbert"
Move the log_dirty check into vhost_section.
Signed-off-by: Dr. David Alan Gilbert
---
hw/virtio/trace-events | 1 +
hw/virtio/vhost.c | 20 +---
2 files changed, 14 insertions(+), 7 deletions(-)
From: "Dr. David Alan Gilbert"
Hi,
This patch set reworks the way the vhost code handles changes in
physical address space layout that came from a discussion with Igor.
Its intention is to simplify a lot of the update code,
and to make it easier for the postcopy+shared
From: "Dr. David Alan Gilbert"
vhost_verify_ring_mappings() were used to verify that
rings are still accessible and related memory hasn't
been moved after flatview is updated.
It was doing checks by mapping ring's GPA+len and
checking that HVA hadn't changed with new memory
From: "Dr. David Alan Gilbert"
Hi,
This patch set reworks the way the vhost code handles changes in
physical address space layout that came from a discussion with Igor.
Its intention is to simplify a lot of the update code,
and to make it easier for the postcopy+shared
From: "Dr. David Alan Gilbert"
Now that the olf vhost_set_memory code is gone, the _nop and _add
callbacks are identical and can be merged. The _del callback is
no longer needed.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-by: Igor Mammedov
From: "Dr. David Alan Gilbert"
Move the log_dirty check into vhost_section.
Signed-off-by: Dr. David Alan Gilbert
---
hw/virtio/trace-events | 1 +
hw/virtio/vhost.c | 20 +---
2 files changed, 14 insertions(+), 7 deletions(-)
From: "Dr. David Alan Gilbert"
Igor spotted that there's a race, where a region that's unref'd
in a _del callback might be free'd before the set_mem_table call in
the _commit callback, and thus the vhost might end up using free memory.
Fix this by building a complete
From: "Dr. David Alan Gilbert"
Remove the old update mechanism, vhost_set_memory, and the functions
and flags it used.
Signed-off-by: Dr. David Alan Gilbert
---
hw/virtio/vhost.c | 251 --
From: "Dr. David Alan Gilbert"
Compare the sections list that's just been generated, and if it's
different from the old one regenerate the region list.
Signed-off-by: Dr. David Alan Gilbert
---
hw/virtio/trace-events | 1 +
hw/virtio/vhost.c |
From: "Dr. David Alan Gilbert"
As sections are reported by the listener to the _nop and _add
methods, add them to the temporary section list but now merge them
with the previous section if the new one abuts and the backend allows.
Signed-off-by: Dr. David Alan Gilbert
From: "Dr. David Alan Gilbert"
The boot block used in the migration test is currently only
shipped as a hex (with the source in the git commit message),
change this to actually include the source.
A makefile rule is added, but the expectation is that
the generated hex is
From: "Dr. David Alan Gilbert"
In e91d895 I added the new pause-before-switchover mechanism
to allow migration completion to be delayed; this changes the
last state prior to completion to MIGRATE_STATUS_DEVICE rather
than MIGRATE_STATUS_ACTIVE.
Fix the failure path in
From: Juan Quintela
We add deprecated commands on a new test, so we don't have to add it
on normal tests.
Signed-off-by: Juan Quintela
Reviewed-by: Peter Xu
Signed-off-by: Dr. David Alan Gilbert
---
From: "Dr. David Alan Gilbert"
The following changes since commit 2b3805f370521deacab974b9c9ca07d2319a8890:
Merge remote-tracking branch
'remotes/stefanberger/tags/pull-tpm-2018-02-03-1' into staging (2018-02-05
09:31:37 +)
are available in the Git repository at:
1301 - 1400 of 3588 matches
Mail list logo