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
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 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: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 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: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: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 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:
在 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 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
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
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
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
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 '
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
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
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
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
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 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 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 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 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
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
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
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
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 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
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 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
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
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
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
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.
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
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
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
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
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 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 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 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
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
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
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
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:
> 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
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:
> 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 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 +++
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
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
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:
> 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: 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 ++
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 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: 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 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: 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: Alex Bennée
This is modelled after the iothread mutex lock. We keep a TLS flag to
indicate when that thread has acquired the lock and assert we don't
double-lock or release when we shouldn't have.
Signed-off-by: Alex Bennée
Tested-by: Pavel Dovgalyuk
Message-Id: <20180227095237.1060.4466
From: Pavel Dovgalyuk
Virtual clock is warped from iothread and vcpu thread. When the hardware
events associated with warp checkpoint, then interrupt delivering may be
non-deterministic if checkpoint is processed in different threads in record
and replay.
This patch disables event processing for
From: Philippe Mathieu-Daudé
So far, it is only used by the MIPS Fulong 2E mini PC.
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-21-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAIN
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-23-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
MAINTAINERS| 1 +
hw/isa/Makefile.objs | 2 +-
hw/isa/smc37c669-superio.c | 115 ++
From: Pavel Dovgalyuk
This patch does not allows saving/loading vmstate when
replay events queue is not empty. There is no reliable
way to save events queue, because it describes internal
coroutine state. Therefore saving and loading operations
should be deferred to another record/replay step.
S
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-12-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
hw/isa/isa-superio.c | 41 +
hw/isa/pc87312.c | 43 -
From: Alex Bennée
This time commit 802f045a5f61b781df55e4492d896b4d20503ba7 broke the
replay file format. Also add a comment about this to
replay-internal.h.
Signed-off-by: Alex Bennée
Reviewed-off-by: Pavel Dovgalyuk
Acked-by: Paolo Bonzini
Message-Id: <20180227095231.1060.91180.stgit@pasha-
From: Philippe Mathieu-Daudé
This function only initialize the ISA bus.
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-19-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
hw/isa/vt82c686.c | 2 +-
hw/mips/mips_fulong2e.c | 2 +-
include/hw/isa/vt82c686.h |
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-24-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
default-configs/alpha-softmmu.mak | 2 ++
hw/alpha/dp264.c | 4
2 files changed, 6 insertions(+)
diff --git a/default
From: Pavel Dovgalyuk
This patch fixes assignment to internal events_enabled variable.
Now it is set only in record/replay mode. This affects the behavior
of the external functions that check this flag.
Signed-off-by: Pavel Dovgalyuk
Acked-by: Paolo Bonzini
Message-Id: <20180227095209.1060.458
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-15-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
hw/isa/isa-superio.c | 22 ++
hw/isa/pc87312.c | 36
hw/isa/trace-event
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-20-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
hw/isa/vt82c686.c | 20
hw/mips/mips_fulong2e.c | 15 +++
include/hw/isa/vt82c686.h | 2 ++
3 fi
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-13-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
hw/isa/isa-superio.c | 36
hw/isa/pc87312.c | 46 +++---
From: Pavel Dovgalyuk
Asynchronous events saved at checkpoints may invoke
callbacks when processed. These callbacks may also generate/read
new events (e.g. clock reads). Therefore event processing flag must be
reset before callback invocation.
Signed-off-by: Pavel Dovgalyuk
Acked-by: Paolo Bonz
From: Philippe Mathieu-Daudé
Move the SouthBridge peripherals first, and keep the Super I/O
peripherals last.
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-16-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
hw/mips/mips_malta.c | 14 +++---
1 file changed,
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-10-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
hw/isa/pc87312.c | 11 ++-
include/hw/isa/pc87312.h | 6 --
2 files changed, 14 insertions(+), 3 deletions(-)
diff --g
From: Philippe Mathieu-Daudé
Since the PC87312 inherits this abstract model, we remove the I8042
instance in the PREP machine.
Signed-off-by: Philippe Mathieu-Daudé
Acked-by: David Gibson
Message-Id: <20180308223946.26784-14-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
hw/isa/isa-superi
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-26-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
hw/i386/pc.c | 72 ++--
1 file changed, 41 insertions(+), 31 deletions(-)
diff --gi
From: Philippe Mathieu-Daudé
This matches the isa_register_ioport() prototype.
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-7-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
hw/isa/pc87312.c | 14 +++---
include/hw/isa/pc87312.h | 2 +-
2 files ch
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-8-f4...@amsat.org>
Reviewed-by: Mark Cave-Ayland
Signed-off-by: Paolo Bonzini
---
hw/isa/pc87312.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/hw/isa/pc87312.c b/
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-18-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
hw/mips/mips_fulong2e.c | 83 -
1 file changed, 41 insertions(+), 42 deletions(-)
diff --gi
This new header file provides heavy-weight "global" memory barriers that
enforce memory ordering on each running thread belonging to the current
process. For now, use a dummy implementation that issues memory barriers
on both sides (matching what QEMU has been doing so far).
Signed-off-by: Paolo
From: Philippe Mathieu-Daudé
Missed while moving it in 0d09e41a51aa.
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-5-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
MAINTAINERS | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAIN
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-9-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
MAINTAINERS | 2 ++
hw/isa/Makefile.objs | 1 +
hw/isa/isa-superio.c | 28
include/hw/isa
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-17-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
hw/isa/isa-superio.c | 19 +++
hw/mips/mips_malta.c | 35 ++-
include/hw/isa/superio
From: Thomas Huth
The global hack for creating SCSI devices has recently been removed,
but this apparently broke SCSI devices on some boards that were not
ready for this change yet. For the pica61 machine you now get:
$ mips64-softmmu/qemu-system-mips64 -M pica61 -cdrom x.iso
qemu-system-mips64:
From: Philippe Mathieu-Daudé
- Move the header from hw/isa/ to hw/dma/
- Remove the old i386/pc dependency
- use a bool type for the high_page_enable argument
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-3-f4...@amsat.org>
Reviewed-by: Mark Cave-Ayland
Signed-off-by:
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Acked-by: David Gibson (hw/ppc)
Message-Id: <20180308223946.26784-6-f4...@amsat.org>
Reviewed-by: Mark Cave-Ayland
Signed-off-by: Paolo Bonzini
---
hw/isa/pc87312.c | 2 +-
hw/ppc/prep.c| 2 +-
include/hw/
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-11-f4...@amsat.org>
Signed-off-by: Paolo Bonzini
---
hw/isa/isa-superio.c | 65
hw/isa/pc87312.c | 38 +++-
Allow distributions to disable the Intel and/or AMD IOMMU devices.
Reviewed-by: Thomas Huth
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Paolo Bonzini
---
default-configs/i386-softmmu.mak | 2 ++
default-configs/x86_64-softmmu.mak | 2 ++
hw/i386/Makefile.objs | 4 ++--
3
From: Philippe Mathieu-Daudé
Again... (after 07dc788054d7 and 9157eee1b1c0).
We now extract the ISA bus specific helpers.
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20180308223946.26784-2-f4...@amsat.org>
Reviewed-by: Mark Cave-Ayland
Signed-off-by: Paolo Bonzini
---
MAINTAINERS
We will use them in the next patch, document what they do.
Signed-off-by: Paolo Bonzini
---
docs/devel/atomics.txt | 57 ++
1 file changed, 30 insertions(+), 27 deletions(-)
diff --git a/docs/devel/atomics.txt b/docs/devel/atomics.txt
index 10c5fa
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Acked-by: David Gibson (hw/ppc)
Message-Id: <20180308223946.26784-4-f4...@amsat.org>
Reviewed-by: Mark Cave-Ayland
Signed-off-by: Paolo Bonzini
---
MAINTAINERS | 1 +
hw/alpha/dp264.c | 3 ++-
hw/i386/p
From: Peter Xu
This patch allows the socket chardev async connection be setup with
non-default gcontext. We do it by postponing the setup to machine done,
since until then we can know which context we should run the async
operation on.
Reviewed-by: Paolo Bonzini
Signed-off-by: Peter Xu
Messag
From: Peter Xu
Now qio_channel_tls_handshake() is ready to receive the context. Let
socket chardev use it, then the TLS handshake of chardev will always be
with the chardev's context.
Signed-off-by: Peter Xu
Message-Id: <20180306053320.15401-9-pet...@redhat.com>
Acked-by: Stefan Hajnoczi
Revi
Actually enable the global memory barriers if supported by the OS.
Because only recent versions of Linux include the support, they
are disabled by default. Note that it also has to be disabled
for QEMU to run under Wine.
Before this patch, rcutorture reports 85 ns/read for my machine,
after the p
From: Thomas Huth
Since commit 67a1de0d195a there is no space anymore between the
version number and the parentheses when running configure with
--with-pkgversion=foo :
$ qemu-system-s390x --version
QEMU emulator version 2.11.50(foo)
But the space is included when building without that option
1 - 100 of 563 matches
Mail list logo