From: Pavel Dovgalyuk
Replay mutex is held by vCPU thread and destroy function is called
from atexit of the main thread. Therefore we cannot destroy it safely.
Signed-off-by: Pavel Dovgalyuk
Acked-by: Paolo Bonzini
Message-Id: <20180227095254.1060.96971.stgit@pasha-VirtualBox>
Signed-off-by: P
From: Pavel Dovgalyuk
This patch fixes saving and loading the snapshots in the replay mode.
It is required for the snapshots created in the moment when the header
of the asynchronous event is read. This information was not saved in
the snapshot. After loading the vmstate replay continued with the
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-25-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
default-configs/alpha-softmmu.mak | 3 +++
hw/alpha/dp264.c | 10 --
2 files changed, 7 insertions(+), 6 deletions
From: Pavel Dovgalyuk
This patch adds saving/restoring of the host clock field 'last'.
It is used in host clock calculation and therefore clock may
become incorrect when using restored vmstate.
Signed-off-by: Pavel Dovgalyuk
Acked-by: Paolo Bonzini
Message-Id: <20180227095226.1060.50975.stgit@
From: Pavel Dovgalyuk
This patch adds a flag which denies recursive call of replay_checkpoint
function. Checkpoints may be accompanied by the hardware events. When event
is processed, virtual device may invoke timer modification functions that
also invoke the checkpoint function. This leads to in
From: Alex Bennée
Now instead of using the replay_lock to guard the output of the log we
now use it to protect the whole execution section. This replaces what
the BQL used to do when it was held during TCG execution.
We also introduce some rules for locking order - mainly that you
cannot take th
From: Pavel Dovgalyuk
This patch adds description of the replay log file format
into the docs/replay.txt.
Signed-off-by: Pavel Dovgalyuk
Acked-by: Paolo Bonzini
Message-Id: <20180227095220.1060.58759.stgit@pasha-VirtualBox>
Signed-off-by: Paolo Bonzini
---
docs/replay.txt | 69 ++
On 03/13/2018 04:34 PM, Peter Maydell wrote:
> Our BCM2836 type is really a generic one that can be any of
> the bcm283x family. Rename it accordingly. We change only
> the names which are visible via the header file to the
> rest of the QEMU code, leaving private function names
> in bcm2836.c as t
From: Alex Bennée
This script is a debugging tool for looking through the contents of a
replay log file. It is incomplete but should fail gracefully at events
it doesn't understand.
It currently understands two different log formats as the audio
record/replay support was merged during since MTTC
On 03/13/2018 04:34 PM, Peter Maydell wrote:
> The bcm2837 is pretty similar to the bcm2836, but it does have
> some differences. Notably, the MPIDR affinity aff1 values it
> sets for the CPUs are 0x0, rather than the 0xf that the bcm2836
> uses, and if this is wrong Linux will not boot.
>
> Rathe
From: Alex Bennée
The replay_mutex_lock/unlock/locked functions are now going to be used
for ensuring lock-step behaviour between the two threads. Make them
public API functions and also provide stubs for non-QEMU builds on
common paths.
Signed-off-by: Alex Bennée
Signed-off-by: Pavel Dovgalyuk
From: Pavel Dovgalyuk
This patch clarifies the description of the record/replay feature
in docs/replay.txt
Signed-off-by: Pavel Dovgalyuk
Message-Id: <20180227095333.1060.1331.stgit@pasha-VirtualBox>
Signed-off-by: Paolo Bonzini
Signed-off-by: Pavel Dovgalyuk
---
docs/replay.txt | 72 +++
On 03/13/2018 04:34 PM, Peter Maydell wrote:
> The TypeInfo and state struct for bcm2386 disagree about what the
> parent class is -- the TypeInfo says it's TYPE_SYS_BUS_DEVICE,
> but the BCM2386State struct only defines the parent_obj field
> as DeviceState. This would have caused problems if anyt
From: Pavel Dovgalyuk
This patch adds error reporting when fwrite cannot completely
save the buffer to the file.
Signed-off-by: Pavel Dovgalyuk
Message-Id: <20180227095259.1060.86410.stgit@pasha-VirtualBox>
Signed-off-by: Paolo Bonzini
Signed-off-by: Pavel Dovgalyuk
---
replay/replay-interna
On 03/13/2018 04:34 PM, Peter Maydell wrote:
> Now we have separate types for BCM2386 and BCM2387, we might as well
> just hard-code the CPU type they use rather than having it passed
> through as an object property. This then lets us put the initialization
> of the CPU object in init rather than r
On 03/13/2018 06:09 PM, Peter Maydell wrote:
> On 13 March 2018 at 16:55, Andrew Baumann
> wrote:
>>> From: Qemu-devel >> bounces+andrew.baumann=microsoft@nongnu.org> On Behalf Of Peter
>>> Maydell
>>> Sent: Tuesday, 13 March 2018 08:35
>>>
>>> Now we have separate types for BCM2386 and BCM23
This should help to avoid problems with accessing the device after
migration/resume without PV drivers by migrating its PCI configuration
space state. Without an explicitly defined state record it resets
every time a VM migrates which confuses the OS and makes every
access to xen-pvdevice MMIO regi
From: Pavel Dovgalyuk
cpu_io_recompile() function was broken by
the commit 9b990ee5a3cc6aa38f81266fb0c6ef37a36c45b9. Instead of regenerating
the block starting from PC of the original block, it just set the instruction
counter for TCG. In most cases this was unnoticed, but in icount mode
there wa
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-22-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
MAINTAINERS | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 07684a1f2d..b17324107f
On 02/02/2018 01:42 AM, Alistair Francis wrote:
>
> There are numorous QEMU machines that only have a single or a handful of
> valid CPU options. To simplyfy the management of specificying which CPU
> is/isn't valid let's create a property that can be set in the machine
> init. We can then check t
On 03/13/2018 06:09 PM, Peter Maydell wrote:
> On 13 March 2018 at 16:55, Andrew Baumann
> wrote:
>>> From: Qemu-devel >> bounces+andrew.baumann=microsoft@nongnu.org> On Behalf Of Peter
>>> Maydell
>>> Sent: Tuesday, 13 March 2018 08:35
>>>
>>> Now we have separate types for BCM2386 and BCM23
On 03/13/2018 04:34 PM, Peter Maydell wrote:
> For the rpi1 and 2 we want to boot the Linux kernel via some
> custom setup code that makes sure that the SMC instruction
> acts as a no-op, because it's used for cache maintenance.
> The rpi3 boots AArch64 kernels, which don't need SMC for
> cache mai
On 03/13/2018 04:34 PM, Peter Maydell wrote:
> Add some assertions that if we're about to boot an AArch64 kernel,
> the board code has not mistakenly set either secure_boot or
> secure_board_setup. It doesn't make sense to set secure_boot,
> because all AArch64 kernels must be booted in non-secure
On Mon, 12 Mar 2018 18:44:02 -0300
Eduardo Habkost wrote:
>On Tue, Mar 13, 2018 at 06:56:37AM +1000, Alexey G wrote:
>> On Mon, 12 Mar 2018 16:44:06 -0300
>> Eduardo Habkost wrote:
>>
>> >On Tue, Mar 13, 2018 at 04:34:01AM +1000, Alexey Gerasimenko
>> >wrote:
>> >> Current Xen/QEMU method t
From: Pavel Dovgalyuk
Function cpu_handle_interrupt calls cc->cpu_exec_interrupt to process
pending hardware interrupts. Under the hood cpu_exec_interrupt uses
cpu->exception_index to pass information to the internal function which
is usually common for exception and interrupt processing.
But thi
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20180313224719.4954-1-pbonz...@redhat.com
Subject: [Qemu-devel] [PULL 00/69] Misc patches for QEMU soft freeze
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
total=$(gi
On Tue, Mar 13, 2018 at 12:26:56PM +0100, BALATON Zoltan wrote:
1;5002;0c> Using log unimp is more appropriate for these messages and this also
> silences them by default so they won't clobber make check output when
> tests are added for this board.
>
> Signed-off-by: BALATON Zoltan
> Reviewed-by
From: Junyan He
We want to support incremental snapshot saving, this needs the file
system support dependency saving. Later snapshots may ref the dependent
snapshot's content, and most time should be cluster aligned.
Add a query function to check whether the file system support this, and
use the
From: Junyan He
For qcow2 format, we can increase the cluster's reference count of
dependent snapshot content and link the offset to the L2 table of
the new snapshot point. This way can avoid obvious snapshot's dependent
relationship, so when we delete some snapshot point, just decrease the
clust
From: Junyan He
The nvdimm size is huge, sometimes it is more than 256G or even more.
This is a huge burden for snapshot saving. One snapshot point with
nvdimm may occupy more than 50G disk space even with compression
enabled.
We need to introduce dependent snapshot manner to solve this problem.
From: Junyan He
When we save snapshot, we need qemu_file to support save dependency
operations. It should call brv_driver's save dependency functions
to implement these operations.
Signed-off-by: Junyan He
---
migration/qemu-file.c | 61 +++
migr
From: Junyan He
In snapshot saving, all nvdimm kind memory will be saved in different way
and we exclude all nvdimm kind memory region in ram.c
Signed-off-by: Junyan He
---
migration/ram.c | 17 +
vl.c| 1 +
2 files changed, 18 insertions(+)
diff --git a/migration
From: Junyan He
Signed-off-by: Junyan He
---
block/snapshot.c | 45 +
include/block/snapshot.h | 7 +++
2 files changed, 52 insertions(+)
diff --git a/block/snapshot.c b/block/snapshot.c
index eacc1f1..8cc40ac 100644
--- a/block/snapshot
From: Junyan He
We need to collect dirty log for nvdimm kind memory, need to enable
memory_region_set_log for more clients rather than just VGA.
Signed-off-by: Junyan He
---
memory.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/memory.c b/memory.c
index e70b6
From: Junyan He
We need to know the section_id when we do snapshot saving.
Add a parameter to save_live_iterate function call.
Signed-off-by: Junyan He
---
hw/ppc/spapr.c | 2 +-
hw/s390x/s390-stattrib.c | 2 +-
include/migration/register.h | 2 +-
migration/block.c
From: Junyan He
We need to get the bitmap content of the snapshot when enable dirty
log trace for nvdimm.
Signed-off-by: Junyan He
---
exec.c | 7 +++
include/exec/memory.h | 9 +
include/exec/ram_addr.h | 2 ++
memory.c| 7 +++
4 files change
From: Junyan He
The nvdimm size is huge, sometimes is more than 256G or even more.
This is a huge burden for snapshot saving. One snapshot point with
nvdimm may occupy more than 50G disk space even with compression
enabled.
We need to introduce dependent snapshot manner to solve this problem.
The
From: Junyan He
We need to know the snapshot saving information when we do dependent
snapshot saving, e.g the name of previous snapshot. Add this global
function to query the snapshot status is usable.
Signed-off-by: Junyan He
---
include/migration/snapshot.h | 3 +++
migration/savevm.c
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 1520990418-28258-1-git-send-email-junyan...@hotmail.com
Subject: [Qemu-devel] [PATCH 00/10] RFC: Optimize nvdimm kind memory for
snapshot.
=== TEST SCRIPT BEGIN ===
#!/bin/b
Hi,
This series failed build test on s390x host. Please find the details below.
Type: series
Message-id: 20180313171345.659672-1-ebl...@redhat.com
Subject: [Qemu-devel] [PULL 00/17] NBD patches for 2018-03-13 (2.12 softfreeze)
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoke
On 03/14/2018 12:35 AM, Michael S. Tsirkin wrote:
On Wed, Mar 07, 2018 at 08:34:25PM +0800, Wei Wang wrote:
Start the free page optimization after the migration bitmap is
synchronized. This can't be used in the stop© phase since the guest
is paused. Make sure the guest reporting has stopped befo
On 03/14/2018 12:49 AM, Michael S. Tsirkin wrote:
On Wed, Mar 07, 2018 at 08:34:24PM +0800, Wei Wang wrote:
Signed-off-by: Wei Wang
Signed-off-by: Liang Li
CC: Michael S. Tsirkin
CC: Dr. David Alan Gilbert
CC: Juan Quintela
I find it suspicious that neither unrealize nor reset
functions h
On 14/3/18 3:56 am, Alex Williamson wrote:
> [Cc +Eric]
>
> On Tue, 13 Mar 2018 15:53:19 +1100
> Alexey Kardashevskiy wrote:
>
>> On 7/3/18 1:17 pm, Alexey Kardashevskiy wrote:
>>> On 26/02/18 19:36, Alexey Kardashevskiy wrote:
On 19/02/18 13:46, Alexey Kardashevskiy wrote:
> On 16/
On Wed, Mar 14, 2018 at 10:41:36AM +0800, Wei Wang wrote:
> On 03/14/2018 12:35 AM, Michael S. Tsirkin wrote:
> > On Wed, Mar 07, 2018 at 08:34:25PM +0800, Wei Wang wrote:
> > > Start the free page optimization after the migration bitmap is
> > > synchronized. This can't be used in the stop© phase
On Wed, Mar 14, 2018 at 10:43:01AM +0800, Wei Wang wrote:
> On 03/14/2018 12:49 AM, Michael S. Tsirkin wrote:
> > On Wed, Mar 07, 2018 at 08:34:24PM +0800, Wei Wang wrote:
> >
> > > Signed-off-by: Wei Wang
> > > Signed-off-by: Liang Li
> > > CC: Michael S. Tsirkin
> > > CC: Dr. David Alan Gilbe
On Tue, Mar 13, 2018 at 05:15:41PM -0700, no-re...@patchew.org wrote:
[...]
> Your patch has style problems, please review. If any of these errors
> are false positives report them to the maintainer, see
> CHECKPATCH in MAINTAINERS.
> Checking PATCH 2/69: net: allow using any PCI NICs in -net or
We've got a U-Boot firmware for this board in our repository, and
the firmware prints some output to the serial console, so we can
check this board in the boot-serial tester, too.
Signed-off-by: Thomas Huth
---
Note: Patch has to be applied on top of the ppc-for-2.12 branch
tests/boot-serial-t
Hi,
I am implementing 'virtio-pmem' as a mechanism to
flush guest writes with 'fake DAX' flushing interface.
Below is the high level details of components:
1] 'virtio-pmem' device expose guest physical address
details(start, len).
2] 'virtio-pmem' driver in guest discovers this
inf
On Mon, Mar 12, 2018 at 07:36:05PM +0100, Cédric Le Goater wrote:
> On 02/19/2018 04:29 AM, David Gibson wrote:
> > On Fri, Feb 16, 2018 at 09:45:04AM +0100, Cédric Le Goater wrote:
> >> On a POWER9 processor, the first doubleword of the partition table
> >> entry (as pointed to by the PTCR) indica
Rebasing a couple of my development branches onto master this morning,
I'm noticing some GTK warnings when I close the QEMU GTK window directly
rather than using the "Quit" menu option:
$ ./qemu-system-ppc
(qemu-system-ppc:19782): GLib-GObject-WARNING **: invalid unclassed
pointer in cast to '
Currently we don't support pci multifunction. If a pci with
multifucntion is plugged, the guest will spin forever. This patch fixes
this.
Signed-off-by: Yi Min Zhao
Reviewed-by: Pierre Morel
---
hw/s390x/s390-pci-bus.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/hw/s390x/s39
Sincerely sorry for my negligence to cause this bug!
I will fix it as quick as I can!
Sorry again, I'm really ashamed about the mistake I have made.
Su Hang
> -Original Messages-
> From: "Dr. David Alan Gilbert"
> Sent Time: 2018-03-14 04:10:24 (Wednesday)
> To: "Vladimir Sementsov-Ogie
Hi,
This series failed docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
Type: series
Message-id: 1520990418-28258-1-git-send-email-junyan...@hotmail.com
Subject: [Qemu-devel] [PATCH 00/10
On 14.03.2018 06:14, Yi Min Zhao wrote:
> Currently we don't support pci multifunction. If a pci with
> multifucntion is plugged, the guest will spin forever. This patch fixes
> this.
>
> Signed-off-by: Yi Min Zhao
> Reviewed-by: Pierre Morel
> ---
> hw/s390x/s390-pci-bus.c | 10 ++
> 1
在 2018/3/14 下午1:35, Thomas Huth 写道:
On 14.03.2018 06:14, Yi Min Zhao wrote:
Currently we don't support pci multifunction. If a pci with
multifucntion is plugged, the guest will spin forever. This patch fixes
this.
Signed-off-by: Yi Min Zhao
Reviewed-by: Pierre Morel
---
hw/s390x/s390-pci-
On 03/14/2018 10:53 AM, Michael S. Tsirkin wrote:
On Wed, Mar 14, 2018 at 10:43:01AM +0800, Wei Wang wrote:
On 03/14/2018 12:49 AM, Michael S. Tsirkin wrote:
On Wed, Mar 07, 2018 at 08:34:24PM +0800, Wei Wang wrote:
Signed-off-by: Wei Wang
Signed-off-by: Liang Li
CC: Michael S. Tsirkin
CC:
On Tue, Mar 06, 2018 at 08:30:52PM +, Mark Cave-Ayland wrote:
> This is in preparation for moving the PCI bus wiring inside the uninorth
> host bridge devices. In the future it will be possible to remove this once the
> PICs have been switched to use qdev GPIOs.
>
> Signed-off-by: Mark Cave-Ay
On Tue, Mar 06, 2018 at 08:30:44PM +, Mark Cave-Ayland wrote:
> [This is for New World Machines: there is a follow-up patch for Old World
> Machines]
>
> This patchset is a combination of uninorth fixes/cleanup with the final aim
> of removing the remaining custom init functions and switching
On Tue, Mar 06, 2018 at 08:30:49PM +, Mark Cave-Ayland wrote:
> Signed-off-by: Mark Cave-Ayland
Applied to ppc-for-2.13.
> ---
> hw/pci-host/uninorth.c | 22 +--
> include/hw/pci-host/uninorth.h | 49
> ++
> 2 files changed, 5
On Tue, Mar 06, 2018 at 08:30:50PM +, Mark Cave-Ayland wrote:
> This is in preparation for moving the device wiring into the New World
> machine.
>
> Signed-off-by: Mark Cave-Ayland
Applied to ppc-for-2.13.
> ---
> hw/pci-host/uninorth.c | 16
> hw/ppc/mac.h | 1
On Wed, Mar 14, 2018 at 05:28:55AM +0100, Thomas Huth wrote:
> We've got a U-Boot firmware for this board in our repository, and
> the firmware prints some output to the serial console, so we can
> check this board in the boot-serial tester, too.
>
> Signed-off-by: Thomas Huth
Applied, thanks.
On Tue, Mar 06, 2018 at 08:30:44PM +, Mark Cave-Ayland wrote:
> [This is for New World Machines: there is a follow-up patch for Old World
> Machines]
>
> This patchset is a combination of uninorth fixes/cleanup with the final aim
> of removing the remaining custom init functions and switching
On 03/14/2018 10:51 AM, Michael S. Tsirkin wrote:
On Wed, Mar 14, 2018 at 10:41:36AM +0800, Wei Wang wrote:
On 03/14/2018 12:35 AM, Michael S. Tsirkin wrote:
On Wed, Mar 07, 2018 at 08:34:25PM +0800, Wei Wang wrote:
Start the free page optimization after the migration bitmap is
synchronized. T
501 - 563 of 563 matches
Mail list logo
