[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-commits] [qemu/qemu] 87c9cc: Changing error message of QMP 'migrat
|
From: |
GitHub |
|
Subject: |
[Qemu-commits] [qemu/qemu] 87c9cc: Changing error message of QMP 'migrate_set_downtim... |
|
Date: |
Thu, 02 Mar 2017 11:30:11 -0800 |
Branch: refs/heads/master
Home: https://github.com/qemu/qemu
Commit: 87c9cc1c30d2981e9686aaf245b3e2420062f7d4
https://github.com/qemu/qemu/commit/87c9cc1c30d2981e9686aaf245b3e2420062f7d4
Author: Daniel Henrique Barboza <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M migration/migration.c
Log Message:
-----------
Changing error message of QMP 'migrate_set_downtime' to seconds
Using QMP, the error message of 'migrate_set_downtime' was displaying
the values in milliseconds, being misleading with the command that
accepts the value in seconds:
{ "execute": "migrate_set_downtime", "arguments": {"value": 3000}}
{"error": {"class": "GenericError", "desc": "Parameter 'downtime_limit'
expects an integer in the range of 0 to 2000000 milliseconds"}}
This message is also seen in HMP when trying to set the same
parameter:
(qemu) migrate_set_parameter downtime-limit 3000000
Parameter 'downtime_limit' expects an integer in the range of 0 to
2000000 milliseconds
To allow for a proper error message when using QMP, a validation
of the user input was added in 'qmp_migrate_set_downtime'.
Signed-off-by: Daniel Henrique Barboza <address@hidden>
Message-Id: <address@hidden>
Reviewed-by: Juan Quintela <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: e84641f73dcf2963bfbafc5c3178c3254fb758a8
https://github.com/qemu/qemu/commit/e84641f73dcf2963bfbafc5c3178c3254fb758a8
Author: Halil Pasic <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M migration/vmstate.c
Log Message:
-----------
migration/vmstate: renames in (load|save)_state
The vmstate_(load|save)_state start out with an a void *opaque pointing
to some struct, and manipulate one or more elements of one field within
that struct.
First the field within the struct is pinpointed as opaque + offset, then
if this is a pointer the pointer is dereferenced to obtain a pointer to
the first element of the vmstate field. Pointers to further elements if
any are calculated as first_element + i * element_size (where i is the
zero based index of the element in question).
Currently base_addr and addr is used as a variable name for the pointer
to the first element and the pointer to the current element being
processed. This is suboptimal because base_addr is somewhat
counter-intuitive (because obtained as base + offset) and both base_addr
and addr not very descriptive (that we have a pointer should be clear
from the fact that it is declared as a pointer).
Let make things easier to understand by renaming base_addr to first_elem
and addr to curr_elem. This has the additional benefit of harmonizing
with other names within the scope (n_elems, vmstate_n_elems).
Signed-off-by: Halil Pasic <address@hidden>
Reviewed-by: Dr. David Alan Gilbert <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: cbfda0e6cfb9d2c7c99b9475bb85ef29f1643ce3
https://github.com/qemu/qemu/commit/cbfda0e6cfb9d2c7c99b9475bb85ef29f1643ce3
Author: Halil Pasic <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M migration/vmstate.c
Log Message:
-----------
migration/vmstate: split up vmstate_base_addr
Currently vmstate_base_addr does several things: it pinpoints the field
within the struct, possibly allocates memory and possibly does the first
pointer dereference. Obviously allocation is needed only for load.
Let us split up the functionality in vmstate_base_addr and move the
address manipulations (that is everything but the allocation logic) to
load and save so it becomes more obvious what is actually going on. Like
this all the address calculations (and the handling of the flags
controlling these) is in one place and the sequence is more obvious.
The newly introduced function vmstate_handle_alloc also fixes the
allocation for the unused VMS_VBUFFER|VMS_MULTIPLY|VMS_ALLOC scenario
and is substantially simpler than the original vmstate_base_addr.
In load and save some asserts are added so it's easier to debug
situations where we would end up with a null pointer dereference.
Signed-off-by: Halil Pasic <address@hidden>
Reviewed-by: Dr. David Alan Gilbert <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: 07d4e69147b4957e617812206a62a86f03294ad3
https://github.com/qemu/qemu/commit/07d4e69147b4957e617812206a62a86f03294ad3
Author: Halil Pasic <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M include/migration/vmstate.h
M migration/vmstate.c
Log Message:
-----------
migration/vmstate: fix array of ptr with nullptrs
Make VMS_ARRAY_OF_POINTER cope with null pointers. Previously the
reward for trying to migrate an array with some null pointers in it was
an illegal memory access, that is a swift and painless death of the
process. Let's make vmstate cope with this scenario.
The general approach is, when we encounter a null pointer (element),
instead of following the pointer to save/load the data behind it, we
save/load a placeholder. This way we can detect if we expected a null
pointer at the load side but not null data was saved instead.
Signed-off-by: Halil Pasic <address@hidden>
Reviewed-by: Guenther Hutzl <address@hidden>
Reviewed-by: Dr. David Alan Gilbert <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: cc95883185d7192aa3c455bb615bbe19a1e7d1e7
https://github.com/qemu/qemu/commit/cc95883185d7192aa3c455bb615bbe19a1e7d1e7
Author: Halil Pasic <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M tests/test-vmstate.c
Log Message:
-----------
tests/test-vmstate.c: test array of ptr with null
Add test for VMSTATE_ARRAY_OF_POINTER_TO_STRUCT with an array
containing some null pointer.
Signed-off-by: Halil Pasic <address@hidden>
Reviewed-by: Dr. David Alan Gilbert <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Fixed type case in assert to uintptr_t rather than uint64_t
Commit: 4333309961d1c9cd2131cd0d6b5690a71cec0f6a
https://github.com/qemu/qemu/commit/4333309961d1c9cd2131cd0d6b5690a71cec0f6a
Author: Halil Pasic <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M tests/test-vmstate.c
Log Message:
-----------
tests/test-vmstate.c: test array of ptr to primitive
Let's have a test for ptr arrays to some primitive type with some
not-null and null ptrs intermixed.
Signed-off-by: Halil Pasic <address@hidden>
Reviewed-by: Dr. David Alan Gilbert <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: 9cd49026aa3af71a06587a41ece54a8c25c57f88
https://github.com/qemu/qemu/commit/9cd49026aa3af71a06587a41ece54a8c25c57f88
Author: Laurent Vivier <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M scripts/vmstate-static-checker.py
Log Message:
-----------
vmstate-static-checker: update white list with spapr_pci
To fix migration between 2.7 and 2.8, some fields have
been renamed and managed with the help of a PHB property
(pre_2_8_migration):
5c4537b spapr: Fix 2.7<->2.8 migration of PCI host bridge
So we need to add them to the white list:
dma_liobn[0],
mem_win_addr, mem_win_size,
io_win_addr, io_win_size
become
mig_liobn,
mig_mem_win_addr, mig_mem_win_size,
mig_io_win_addr, mig_io_win_size
CC: David Gibson <address@hidden>
CC: Dr. David Alan Gilbert <address@hidden>
CC: Thomas Huth <address@hidden>
CC: Greg Kurz <address@hidden>
CC: Alexey Kardashevskiy <address@hidden>
Signed-off-by: Laurent Vivier <address@hidden>
Message-Id: <address@hidden>
Reviewed-by: Thomas Huth <address@hidden>
Reviewed-by: David Gibson <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: 7562f90707aa1f409ba2312569cb791241fca045
https://github.com/qemu/qemu/commit/7562f90707aa1f409ba2312569cb791241fca045
Author: Ashijeet Acharya <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M hw/core/qdev.c
M hw/usb/bus.c
M include/migration/migration.h
M migration/migration.c
M qdev-monitor.c
M stubs/vmstate.c
Log Message:
-----------
migrate: Introduce a 'dc->vmsd' check to avoid segfault for --only-migratable
Commit a3a3d8c7 introduced a segfault bug while checking for
'dc->vmsd->unmigratable' which caused QEMU to crash when trying to add
devices which do no set their 'dc->vmsd' yet while initialization.
Place a 'dc->vmsd' check prior to it so that we do not segfault for
such devices.
NOTE: This doesn't compromise the functioning of --only-migratable
option as all the unmigratable devices do set their 'dc->vmsd'.
Introduce a new function check_migratable() and move the
only_migratable check inside it, also use stubs to avoid user-mode qemu
build failures.
Signed-off-by: Ashijeet Acharya <address@hidden>
Message-Id: <address@hidden>
Reviewed-by: Dr. David Alan Gilbert <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: 128e4e108949b35dbe351fe122a3e34b834e185a
https://github.com/qemu/qemu/commit/128e4e108949b35dbe351fe122a3e34b834e185a
Author: Marc-André Lureau <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M migration/savevm.c
Log Message:
-----------
migration: fix id leak regression
This leak was introduced in commit
581f08bac22bdd5e081ae07f68071a0fc3c5c2c7.
(it stands out quickly with ASAN once the rest of the leaks are also
removed from make check with this series)
Cc: Dr. David Alan Gilbert <address@hidden>
Cc: Juan Quintela <address@hidden>
Signed-off-by: Marc-André Lureau <address@hidden>
Message-Id: <address@hidden>
Reviewed-by: Dr. David Alan Gilbert <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: 5f9412bbac3a6906b2277d6b8aea02bc12a8464d
https://github.com/qemu/qemu/commit/5f9412bbac3a6906b2277d6b8aea02bc12a8464d
Author: Dr. David Alan Gilbert <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M docs/migration.txt
Log Message:
-----------
migration: Update docs to discourage version bumps
Version bumps break backwards migration; update the docs
to explain to people that's bad and how to avoid it.
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Reviewed-by: Markus Armbruster <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: f9c8caa04f7f2bed12dc5a4d7e92a59fe6677b37
https://github.com/qemu/qemu/commit/f9c8caa04f7f2bed12dc5a4d7e92a59fe6677b37
Author: Vladimir Sementsov-Ogievskiy <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M migration/savevm.c
Log Message:
-----------
migration: fix use-after-free of to_dst_file
hmp_savevm calls qemu_savevm_state(f), which sets to_dst_file=f in
global migration state. Then hmp_savevm closes f (g_free called).
Next access to to_dst_file in migration state (for example,
qmp_migrate_set_speed) will use it after it was freed.
Signed-off-by: Vladimir Sementsov-Ogievskiy <address@hidden>
Reviewed-by: Dr. David Alan Gilbert <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: e8ca1db29b349e780743c504cb735c8e1d542a8c
https://github.com/qemu/qemu/commit/e8ca1db29b349e780743c504cb735c8e1d542a8c
Author: Dr. David Alan Gilbert <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M include/migration/migration.h
M migration/ram.c
M migration/savevm.c
Log Message:
-----------
postcopy: Transmit ram size summary word
Replace the host page-size in the 'advise' command by a pagesize
summary bitmap; if the VM is just using normal RAM then
this will be exactly the same as before, however if they're using
huge pages they'll be different, and thus:
a) Migration from/to old qemu's that don't understand huge pages
will fail early.
b) Migrations with different size RAMBlocks will also fail early.
This catches it very early; earlier than the detailed per-block
check in the next patch.
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Reviewed-by: Laurent Vivier <address@hidden>
Reviewed-by: Juan Quintela <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: ef08fb389fe4ae4a8f7529ae3ec7b4274b7b5248
https://github.com/qemu/qemu/commit/ef08fb389fe4ae4a8f7529ae3ec7b4274b7b5248
Author: Dr. David Alan Gilbert <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M migration/ram.c
Log Message:
-----------
postcopy: Transmit and compare individual page sizes
When using postcopy with hugepages, we require the source
and destination page sizes for any RAMBlock to match; note
that different RAMBlocks in the same VM can have different
page sizes.
Transmit them as part of the RAM information header and
fail if there's a difference.
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Reviewed-by: Laurent Vivier <address@hidden>
Reviewed-by: Juan Quintela <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: 29c59172015b24b442b2d85fa3b2382e262f3d74
https://github.com/qemu/qemu/commit/29c59172015b24b442b2d85fa3b2382e262f3d74
Author: Dr. David Alan Gilbert <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M migration/ram.c
Log Message:
-----------
postcopy: Chunk discards for hugepages
At the start of the postcopy phase, partially sent huge pages
must be discarded. The code for dealing with host page sizes larger
than the target page size can be reused for this case.
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Reviewed-by: Juan Quintela <address@hidden>
Reviewed-by: Laurent Vivier <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: d3a5038c461b9436e5bc82a802b7a843b79f417f
https://github.com/qemu/qemu/commit/d3a5038c461b9436e5bc82a802b7a843b79f417f
Author: Dr. David Alan Gilbert <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M exec.c
M include/exec/cpu-common.h
M include/migration/postcopy-ram.h
M migration/postcopy-ram.c
M migration/ram.c
M migration/trace-events
Log Message:
-----------
exec: ram_block_discard_range
Create ram_block_discard_range in exec.c to replace
postcopy_ram_discard_range and most of ram_discard_range.
Those two routines are a bit of a weird combination, and
ram_discard_range is about to get more complex for hugepages.
It's OS dependent code (so shouldn't be in migration/ram.c) but
it needs quite a bit of the innards of RAMBlock so doesn't belong in
the os*.c.
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Reviewed-by: Juan Quintela <address@hidden>
Reviewed-by: Laurent Vivier <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: e2fa71f527510387f9d474414eba7f9812c58347
https://github.com/qemu/qemu/commit/e2fa71f527510387f9d474414eba7f9812c58347
Author: Dr. David Alan Gilbert <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M exec.c
Log Message:
-----------
postcopy: enhance ram_block_discard_range for hugepages
Unfortunately madvise DONTNEED doesn't work on hugepagetlb
so use fallocate(FALLOC_FL_PUNCH_HOLE)
qemu_fd_getpagesize only sets the page based off a file
if the file is from hugetlbfs.
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Reviewed-by: Juan Quintela <address@hidden>
Reviewed-by: Laurent Vivier <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: 67f11b5c23fca79845c04ace6af0b686c82e0f22
https://github.com/qemu/qemu/commit/67f11b5c23fca79845c04ace6af0b686c82e0f22
Author: Dr. David Alan Gilbert <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M exec.c
M include/exec/cpu-common.h
M include/migration/migration.h
M migration/migration.c
Log Message:
-----------
postcopy: Record largest page size
Record the largest page size in use; we'll need it soon for allocating
temporary buffers.
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Reviewed-by: Juan Quintela <address@hidden>
Reviewed-by: Laurent Vivier <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: df9ff5e1e37982e666216fe9a324d118a30f178f
https://github.com/qemu/qemu/commit/df9ff5e1e37982e666216fe9a324d118a30f178f
Author: Dr. David Alan Gilbert <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M include/migration/postcopy-ram.h
M migration/postcopy-ram.c
M migration/ram.c
Log Message:
-----------
postcopy: Plumb pagesize down into place helpers
Now we deal with normal size pages and huge pages we need
to tell the place handlers the size we're dealing with
and make sure the temporary page is large enough.
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Reviewed-by: Juan Quintela <address@hidden>
Reviewed-by: Laurent Vivier <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: 41d84210d403a686052fb5fc4c9f027e13e92185
https://github.com/qemu/qemu/commit/41d84210d403a686052fb5fc4c9f027e13e92185
Author: Dr. David Alan Gilbert <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M include/migration/migration.h
M migration/postcopy-ram.c
Log Message:
-----------
postcopy: Use temporary for placing zero huge pages
The kernel can't do UFFDIO_ZEROPAGE for huge pages, so we have
to allocate a temporary (always zero) page and use UFFDIO_COPYPAGE
on it.
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Reviewed-by: Juan Quintela <address@hidden>
Reviewed-by: Laurent Vivier <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: 28abd2001445d4e702b1dc9147d0015b189cd37a
https://github.com/qemu/qemu/commit/28abd2001445d4e702b1dc9147d0015b189cd37a
Author: Dr. David Alan Gilbert <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M migration/ram.c
Log Message:
-----------
postcopy: Load huge pages in one go
The existing postcopy RAM load loop already ensures that it
glues together whole host-pages from the target page size chunks sent
over the wire. Modify the definition of host page that it uses
to be the RAM block page size and thus be huge pages where appropriate.
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Reviewed-by: Juan Quintela <address@hidden>
Reviewed-by: Laurent Vivier <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: 332847f0757ee057865fb989e70373092b3b4692
https://github.com/qemu/qemu/commit/332847f0757ee057865fb989e70373092b3b4692
Author: Dr. David Alan Gilbert <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M migration/postcopy-ram.c
Log Message:
-----------
postcopy: Mask fault addresses to huge page boundary
Currently the fault address received by userfault is rounded to
the host page boundary and a host page is requested from the source.
Use the current RAMBlock page size instead of the general host page
size so that for RAMBlocks backed by huge pages we request the whole
huge page.
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Reviewed-by: Juan Quintela <address@hidden>
Reviewed-by: Laurent Vivier <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: 4c011c37ecb37690b3c6463db78c71855694a911
https://github.com/qemu/qemu/commit/4c011c37ecb37690b3c6463db78c71855694a911
Author: Dr. David Alan Gilbert <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M migration/ram.c
Log Message:
-----------
postcopy: Send whole huge pages
The RAM save code uses ram_save_host_page to send whole
host pages at a time; change this to use the host page size associated
with the RAM Block which may be a huge page.
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Reviewed-by: Juan Quintela <address@hidden>
Reviewed-by: Laurent Vivier <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: 433bd0223c213a1f5033e9857d8829d249d3b480
https://github.com/qemu/qemu/commit/433bd0223c213a1f5033e9857d8829d249d3b480
Author: Dr. David Alan Gilbert <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M migration/postcopy-ram.c
Log Message:
-----------
postcopy: Allow hugepages
Allow huge pages in postcopy.
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Reviewed-by: Juan Quintela <address@hidden>
Reviewed-by: Laurent Vivier <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: 61a502128bc81df154ecaa7d42dc075832b169e8
https://github.com/qemu/qemu/commit/61a502128bc81df154ecaa7d42dc075832b169e8
Author: Dr. David Alan Gilbert <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M linux-headers/linux/userfaultfd.h
Log Message:
-----------
postcopy: Update userfaultfd.h header
Just the userfaultfd.h update from Paolo's header
update run;
* Drop this patch after Paolo's update goes in *
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: 7e8cafb7137502ce006cc48d0265f89399e0cb33
https://github.com/qemu/qemu/commit/7e8cafb7137502ce006cc48d0265f89399e0cb33
Author: Dr. David Alan Gilbert <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M migration/postcopy-ram.c
Log Message:
-----------
postcopy: Check for userfault+hugepage feature
We need extra Linux kernel support (~4.11) to support userfaults
on hugetlbfs; check for them.
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Reviewed-by: Juan Quintela <address@hidden>
Reviewed-by: Laurent Vivier <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: 0c1f4036db0a166fb74885c377a3691edb9ad659
https://github.com/qemu/qemu/commit/0c1f4036db0a166fb74885c377a3691edb9ad659
Author: Dr. David Alan Gilbert <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M docs/migration.txt
Log Message:
-----------
postcopy: Add doc about hugepages and postcopy
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Reviewed-by: Juan Quintela <address@hidden>
Reviewed-by: Laurent Vivier <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: 665414ad06aa1bc92e615db9641e58fb13d07de1
https://github.com/qemu/qemu/commit/665414ad06aa1bc92e615db9641e58fb13d07de1
Author: Dr. David Alan Gilbert <address@hidden>
Date: 2017-02-28 (Tue, 28 Feb 2017)
Changed paths:
M migration/postcopy-ram.c
Log Message:
-----------
postcopy: Add extra check for COPY function
As an extra sanity check, make sure the region we're registering
can perform UFFDIO_COPY; the COPY will fail later but this
gives a cleaner failure.
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Reviewed-by: Laurent Vivier <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Commit: 251501a3714096f807778f6d3f03711dcdb9ce29
https://github.com/qemu/qemu/commit/251501a3714096f807778f6d3f03711dcdb9ce29
Author: Peter Maydell <address@hidden>
Date: 2017-03-02 (Thu, 02 Mar 2017)
Changed paths:
M docs/migration.txt
M exec.c
M hw/core/qdev.c
M hw/usb/bus.c
M include/exec/cpu-common.h
M include/migration/migration.h
M include/migration/postcopy-ram.h
M include/migration/vmstate.h
M migration/migration.c
M migration/postcopy-ram.c
M migration/ram.c
M migration/savevm.c
M migration/trace-events
M migration/vmstate.c
M qdev-monitor.c
M scripts/vmstate-static-checker.py
M stubs/vmstate.c
M tests/test-vmstate.c
Log Message:
-----------
Merge remote-tracking branch 'remotes/dgilbert/tags/pull-migration-20170228a'
into staging
Migration pull
Note: The 'postcopy: Update userfaultfd.h header' is part of
Paolo's header update and will disappear if applied after it.
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
# gpg: Signature made Tue 28 Feb 2017 12:38:34 GMT
# gpg: using RSA key 0x0516331EBC5BFDE7
# gpg: Good signature from "Dr. David Alan Gilbert (RH2) <address@hidden>"
# gpg: WARNING: This key is not certified with a trusted signature!
# gpg: There is no indication that the signature belongs to the owner.
# Primary key fingerprint: 45F5 C71B 4A0C B7FB 977A 9FA9 0516 331E BC5B FDE7
* remotes/dgilbert/tags/pull-migration-20170228a: (27 commits)
postcopy: Add extra check for COPY function
postcopy: Add doc about hugepages and postcopy
postcopy: Check for userfault+hugepage feature
postcopy: Update userfaultfd.h header
postcopy: Allow hugepages
postcopy: Send whole huge pages
postcopy: Mask fault addresses to huge page boundary
postcopy: Load huge pages in one go
postcopy: Use temporary for placing zero huge pages
postcopy: Plumb pagesize down into place helpers
postcopy: Record largest page size
postcopy: enhance ram_block_discard_range for hugepages
exec: ram_block_discard_range
postcopy: Chunk discards for hugepages
postcopy: Transmit and compare individual page sizes
postcopy: Transmit ram size summary word
migration: fix use-after-free of to_dst_file
migration: Update docs to discourage version bumps
migration: fix id leak regression
migrate: Introduce a 'dc->vmsd' check to avoid segfault for --only-migratable
...
Signed-off-by: Peter Maydell <address@hidden>
Compare: https://github.com/qemu/qemu/compare/c9fc677a35e6...251501a37140
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Qemu-commits] [qemu/qemu] 87c9cc: Changing error message of QMP 'migrate_set_downtim...,
GitHub <=