Reason: we don't want commit to that interface yet. Possibly
the implementation will be switched over to use fsdev.
Suggested-by: Paolo Bonzini pbonz...@redhat.com
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
hw/usb/dev-mtp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Eric Blake ebl...@redhat.com writes:
Commit dfab4892 restored this file, but did not address any of the
grammar problems that had been fixed in passing when moving events
out of this file. There are also a couple events that were
undocumented since introduction, and one that had been added
On 2014-07-22 21:06, Michael S. Tsirkin wrote:
On Mon, Jul 21, 2014 at 12:04:22AM +0200, Jan Kiszka wrote:
On 2014-07-20 23:03, Michael S. Tsirkin wrote:
On Sun, Jul 20, 2014 at 11:45:10PM +0200, Jan Kiszka wrote:
On 2014-07-20 21:48, Michael S. Tsirkin wrote:
On Sat, Jul 19, 2014 at
Il 22/07/2014 17:47, Le Tan ha scritto:
+static inline void define_quad(IntelIOMMUState *s, hwaddr addr, uint64_t val,
+uint64_t wmask, uint64_t w1cmask)
+{
+*((uint64_t *)s-csr[addr]) = val;
All these casts are not endian-safe. Please use ldl_le_p, ldq_le_p,
Am 22.07.2014 um 22:06 hat Max Reitz geschrieben:
On 21.07.2014 17:52, Eric Blake wrote:
On 07/19/2014 02:35 PM, Max Reitz wrote:
Many qemu-img subcommands only read the source file(s) once. For these
use cases, a full write-back cache is unnecessary and mainly clutters
host cache memory.
When using the icount option on ARM, the virtual
clock starts counting at realtime clock but it
should start at 0.
This small fix addresses this issue.
Signed-off-by: Sebastian Tanase sebastian.tan...@openwide.fr
---
cpus.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Il 23/07/2014 11:11, Sebastian Tanase ha scritto:
When using the icount option on ARM, the virtual
clock starts counting at realtime clock but it
should start at 0.
This small fix addresses this issue.
Signed-off-by: Sebastian Tanase sebastian.tan...@openwide.fr
Thanks, this is ok for 2.2.
Am 23.07.2014 11:16, schrieb Paolo Bonzini:
Il 23/07/2014 11:11, Sebastian Tanase ha scritto:
When using the icount option on ARM, the virtual
clock starts counting at realtime clock but it
should start at 0.
This small fix addresses this issue.
Signed-off-by: Sebastian Tanase
On 23 July 2014 10:11, Sebastian Tanase sebastian.tan...@openwide.fr wrote:
When using the icount option on ARM, the virtual
clock starts counting at realtime clock but it
should start at 0.
This small fix addresses this issue.
Signed-off-by: Sebastian Tanase sebastian.tan...@openwide.fr
Il 23/07/2014 11:41, Peter Maydell ha scritto:
On 23 July 2014 10:11, Sebastian Tanase sebastian.tan...@openwide.fr wrote:
When using the icount option on ARM, the virtual
clock starts counting at realtime clock but it
should start at 0.
This small fix addresses this issue.
Signed-off-by:
When using the icount option on ARM, the virtual
clock starts counting at realtime clock but it
should start at 0.
The reason why the virtual clock starts at realtime clock
is because the first time we call qemu_clock_warp (which
calls icount_warp_rt) in tcg_exec_all, qemu_icount_bias
(which is
On 07/08/2014 08:55 PM, Alex Williamson wrote:
On Mon, 2014-07-07 at 13:27 +0100, Eric Auger wrote:
Signed-off-by: Eric Auger eric.au...@linaro.org
---
hw/vfio/pci.c | 12
1 file changed, 12 deletions(-)
diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
index 5c7bfd5..a7df3de 100644
On 23 July 2014 11:02, Eric Auger eric.au...@linaro.org wrote:
On 07/09/2014 12:41 AM, Alex Williamson wrote:
On Mon, 2014-07-07 at 13:27 +0100, Eric Auger wrote:
+vdev-vbasedev.ops = vfio_pci_ops;
+
+vdev-vbasedev.type = VFIO_DEVICE_TYPE_PCI;
+vdev-vbasedev.name =
On Tue, Jul 22, 2014 at 01:26:00PM +0100, Stefano Stabellini wrote:
On Tue, 22 Jul 2014, Roger Pau Monné wrote:
On 27/05/14 15:29, Stefan Hajnoczi wrote:
On Fri, May 23, 2014 at 05:57:48PM +0200, Roger Pau Monne wrote:
The current behaviour of tap_open for BSD systems differ greatly from
Hi,
I've enabled DEBUG_MMAP in linux-user/mmap.c and got debug info of memory
layout.
This is the debug output of guest memory layout from qemu (including
the last mmap call marked with *).
mmap: start=0x0804a000 len=0x00021000 prot=rw- flags=MAP_ANON
MAP_PRIVATE fd=0 offset=
Hi all,
I post this to both QEMU and libusb because I'm not sure where the error could
be located.
I have an application using libusb which is running for months without any
issues on the host system.
When I start QEMU - which uses libusb, too - the errors begin. I route some USB
ports to my
On 07/23/2014 12:24 PM, Peter Maydell wrote:
On 23 July 2014 11:02, Eric Auger eric.au...@linaro.org wrote:
On 07/09/2014 12:41 AM, Alex Williamson wrote:
On Mon, 2014-07-07 at 13:27 +0100, Eric Auger wrote:
+vdev-vbasedev.ops = vfio_pci_ops;
+
+vdev-vbasedev.type =
On 07/23/2014 01:25 AM, Markus Armbruster wrote:
Eric Blake ebl...@redhat.com writes:
Commit dfab4892 restored this file, but did not address any of the
grammar problems that had been fixed in passing when moving events
out of this file. There are also a couple events that were
14.07.2014, 18:59, Peter Maydell peter.mayd...@linaro.org:
Since softfloat's status flags are sticky ...
What does it mean?
This document explains how IOThreads and the main loop are related,
especially how to write code that can run in an IOThread. Currently
only virtio-blk-data-plane uses these techniques. The next obvious
target is virtio-scsi; there has also been work on virtio-net.
Signed-off-by: Stefan
diff from v1:
split into series [Markus]
fix SPICE_MIGRATE_COMPLETE typo [Markus]
Eric Blake (5):
docs: grammar fixes to qmp-events
docs: split SPICE_* event docs
docs: document missing SPICE_MIGRATE_COMPLETED event
docs: document missing POWERDOWN event
docs: document missing
The SPICE_MIGRATE_COMPLETED event was first documented in
7cfadb6b. But since dfab4892 later restored this flie to the
state prior to qmp events, and we never documented it in the
past, anyone using this file instead of qapi will miss out on
this event.
* docs/qmp/qmp-events.txt
The POWERDOWN event was first documented in 0aab9ec3. But since
dfab4892 later restored this file to the state prior to qmp events,
and we never documented it in the past, anyone using this file
instead of qapi will miss out on this event. Tweak the existing
wording of SHUTDOWN to match
The VSERPORT_CHANGE event was added in e2ae6159. The patch for
this event was prepared at a time when this file was gone, even
though it got applied immediately after dfab4892 restored this
file. Duplicate the documentation into this file, so that
anyone using this file instead of qapi will not
When converting to qmp events, commits 7cfadb6b and a6330785
fixed some grammar as part of moving text between files. But
since dfab4892 later restored this file to the state prior to
qmp events, we have to do it again.
* docs/qmp/qmp-events.txt (RESET, SPICE_INITIALIZED): Tweak.
Signed-off-by:
For consistency with the rest of this file, every event should be
listed in isolation. Compare how commit 7cfadb6b split
SPICE_CONNECTED and SPICE_DISCONNECTED into separate qmp events.
* docs/qmp/qmp-events.txt (SPICE_CONNECTED, SPICE_DISCONNECTED):
Split.
Signed-off-by: Eric Blake
On 07/23/2014 05:55 AM, Stefan Hajnoczi wrote:
This document explains how IOThreads and the main loop are related,
especially how to write code that can run in an IOThread. Currently
only virtio-blk-data-plane uses these techniques. The next obvious
target is virtio-scsi; there has also been
On 23 July 2014 12:55, Dmitry Poletaev poletaev-q...@yandex.ru wrote:
14.07.2014, 18:59, Peter Maydell peter.mayd...@linaro.org:
Since softfloat's status flags are sticky ...
What does it mean?
Sticky here means that the status flags accumulate the
status from a sequence of operations: a
Management software, such as OpenStack and RHEV's vdsm, want to be able
to allocate disk space on demand. The basic use case is to start a VM
with a small disk and then the disk is enlarged when QEMU hits a ENOSPC
condition.
To this end, the management software has to be notified when QEMU
Management software, such as OpenStack and RHEV's vdsm, wants to be able
to allocate VM disk space on demand. The basic use case is to start a VM
with a small disk and then the disk is enlarged when QEMU hits a ENOSPC
condition.
To this end, the management software has to be notified when QEMU
This event has the same characteristics of the other rate-limited
events, mainly we can emit dozens of it. Rate limit it then.
Signed-off-by: Luiz Capitulino lcapitul...@redhat.com
---
monitor.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/monitor.c b/monitor.c
index 5bc70a6..33abe6c
Eric Blake ebl...@redhat.com writes:
The SPICE_MIGRATE_COMPLETED event was first documented in
7cfadb6b. But since dfab4892 later restored this flie to the
this file
state prior to qmp events, and we never documented it in the
past, anyone using this file instead of qapi will miss out on
On 22/07/14 14:26, Stefano Stabellini wrote:
On Tue, 22 Jul 2014, Roger Pau Monné wrote:
On 27/05/14 15:29, Stefan Hajnoczi wrote:
On Fri, May 23, 2014 at 05:57:48PM +0200, Roger Pau Monne wrote:
The current behaviour of tap_open for BSD systems differ greatly from
it's Linux counterpart.
On Wed, 23 Jul 2014, Roger Pau Monné wrote:
On 22/07/14 14:26, Stefano Stabellini wrote:
On Tue, 22 Jul 2014, Roger Pau Monné wrote:
On 27/05/14 15:29, Stefan Hajnoczi wrote:
On Fri, May 23, 2014 at 05:57:48PM +0200, Roger Pau Monne wrote:
The current behaviour of tap_open for BSD systems
qemu-img archipelago:volumename[/mport=mapperd_port[:vport=vlmcd_port]
[:segment=segment_name]] [size]
Signed-off-by: Chrysostomos Nanakos cnana...@grnet.gr
---
block/archipelago.c | 146 +++
1 file changed, 146 insertions(+)
diff --git
Introduce new enum BlockdevOptionsArchipelago.
@volume: #Name of the Archipelago volume image
@mport: #'mport' is the port number on which mapperd is
listening. This is optional and if not specified,
QEMU will make
v7:
- Fix coding style issues.
- Rename __archipelago_submit_request function to archipelago_submit_request.
- Set X_NONBLOCK flag to xseg_receive().
- Return -EIO to .bdrv_getlength() if archipelago_volume_info() fails.
- Fix segment_name mem leak.
- Bump version number from 2.1 to 2.2 in
VM Image on Archipelago volume is specified like this:
file.driver=archipelago,file.volume=volumename[,file.mport=mapperd_port[,
file.vport=vlmcd_port][,file.segment=segment_name]]
'archipelago' is the protocol.
'mport' is the port number on which mapperd is listening. This is optional
and if
VM Image on Archipelago volume can also be specified like this:
file=archipelago:volumename[/mport=mapperd_port[:vport=vlmcd_port][:
segment=segment_name]]
Examples:
file=archipelago:my_vm_volume
file=archipelago:my_vm_volume/mport=123
file=archipelago:my_vm_volume/mport=123:vport=1234
Signed-off-by: Chrysostomos Nanakos cnana...@grnet.gr
---
tests/qemu-iotests/common|6 ++
tests/qemu-iotests/common.rc |9 -
2 files changed, 14 insertions(+), 1 deletion(-)
diff --git a/tests/qemu-iotests/common b/tests/qemu-iotests/common
index e4083f4..70df659 100644
于 2014/7/23 20:26, Eric Blake 写道:
The POWERDOWN event was first documented in 0aab9ec3. But since
dfab4892 later restored this file to the state prior to qmp events,
and we never documented it in the past, anyone using this file
instead of qapi will miss out on this event. Tweak the existing
Reviewed-by: Wenchao Xia wenchaoq...@gmail.com
Reviewed-by: Wenchao Xia wenchaoq...@gmail.com
I didn't expect dot in schema before.
migrate colo info to migration target to tell the target colo is
enabled.
Signed-off-by: Yang Hongyang yan...@cn.fujitsu.com
---
Makefile.objs | 1 +
include/migration/migration-colo.h | 3 ++
migration-colo-comm.c | 68 ++
We need a buffer to store migration data.
On save side:
all saved data was write into colo buffer first, so that we can know
the total size of the migration data. this can also separate the data
transmission from colo control data, we use colo control data over
socket fd to synchronous both
Virtual machine (VM) replication is a well known technique for
providing application-agnostic software-implemented hardware fault
tolerance non-stop service. COLO is a high availability solution.
Both primary VM (PVM) and secondary VM (SVM) run in parallel. They
receive the same request from
Add a migration capability 'colo'. If this capability is on,
The migration will never end, and the VM will be continuously
checkpointed.
Signed-off-by: Yang Hongyang yan...@cn.fujitsu.com
---
include/qapi/qmp/qerror.h | 3 +++
migration.c | 6 ++
qapi-schema.json | 5
Integrate COLO checkpointed save flow into qemu migration.
Add a migrate state: MIG_STATE_COLO, enter this migrate state
after the first live migration successfully finished.
Create a colo thread to do the checkpointed save.
Signed-off-by: Yang Hongyang yan...@cn.fujitsu.com
---
We use COLO agent to compare the packets returned by
Primary VM and Secondary VM, and decide whether to start a
checkpoint according to some rules. It is a linux kernel
module for host.
COLO controller communicate with the agent through ioctl().
Signed-off-by: Yang Hongyang yan...@cn.fujitsu.com
implement colo checkpoint protocol.
Checkpoint synchronzing points.
Primary Secondary
NEW @
Suspend
SUSPENDED @
SuspendSave state
SEND@
implement colo restore
Signed-off-by: Yang Hongyang yan...@cn.fujitsu.com
---
migration-colo.c | 43 +++
1 file changed, 35 insertions(+), 8 deletions(-)
diff --git a/migration-colo.c b/migration-colo.c
index 03ac157..8596845 100644
--- a/migration-colo.c
reuse migration bitmap under colo checkpoint, only send dirty pages
per-checkpoint.
Signed-off-by: Yang Hongyang yan...@cn.fujitsu.com
---
arch_init.c| 20 +++-
include/migration/migration-colo.h | 2 ++
migration-colo.c | 6 ++
The ram cache was initially the same as PVM's memory. At
checkpoint, we cache the dirty memory of PVM into ram cache
(so that ram cache always the same as PVM's memory at every
checkpoint), flush cached memory to SVM after we received
all PVM dirty memory(only needed to flush memory that was
both
is_slaver is to determine whether the QEMU instance is a
slaver(migration target) at runtime.
is_master is to determine whether the QEMU instance is a
master(migration starter) at runtime.
This 2 APIs will be used later.
Signed-off-by: Yang Hongyang yan...@cn.fujitsu.com
---
migration-colo.c |
On 07/23/2014 08:25 AM, Yang Hongyang wrote:
Add a migration capability 'colo'. If this capability is on,
The migration will never end, and the VM will be continuously
checkpointed.
Signed-off-by: Yang Hongyang yan...@cn.fujitsu.com
---
include/qapi/qmp/qerror.h | 3 +++
migration.c
On 07/08/2014 03:43 PM, Alexander Graf wrote:
On 07.07.14 09:08, Eric Auger wrote:
This new module implements routines which help in dynamic instantiation
of sysbus devices. Machine files can use those generic routines.
---
Dynamic sysbus device allocation fully written by Alex Graf.
On 07/08/2014 03:51 PM, Alexander Graf wrote:
On 07.07.14 09:08, Eric Auger wrote:
Allows sysbus devices to be instantiated from command line by
using -device option
---
Inspired from what Alex Graf did in ppc e500
https://lists.gnu.org/archive/html/qemu-ppc/2014-07/msg00012.html
I'm understood. So, am I right?
From: Dmitry Poletaev poletaev-q...@yandex.ru
Signed-off-by: Dmitry Poletaev poletaev-q...@yandex.ru
---
target-i386/fpu_helper.c | 21 ++---
1 file changed, 18 insertions(+), 3 deletions(-)
diff --git a/target-i386/fpu_helper.c
Public bug reported:
[root@localhost pkgs]# qemu-img create virtualdisk.img 100M
qemu-img: symbol lookup error: qemu-img: undefined symbol: glfs_discard_async
[root@localhost pkgs]# qemu-i386 create virtualdisk.img 100M
Error while loading create: No such file or directory
[root@localhost pkgs]#
Public bug reported:
hxtool (part of the early build process) is a bash script. Running it
with /bin/sh yields a syntax error on line 10:
10 STEXI*|ETEXI*|SQMP*|EQMP*) flag=$(($flag^1))
$(( expr )) is a bash extension, not part of /bin/sh.
Note that replacing the sh in the first
On 07/08/2014 03:52 PM, Alexander Graf wrote:
On 07.07.14 09:08, Eric Auger wrote:
This method is meant to be called on sysbus device dynamic
instantiation (-device option). Devices that support this
kind of instantiation must implement this method.
Signed-off-by: Eric Auger
On 07/08/2014 03:53 PM, Alexander Graf wrote:
On 07.07.14 09:08, Eric Auger wrote:
The base address of the platform bus sometimes is used to build the
reg property.
---
Actually I did not succeed in doing it another way with Calxeda xgmac.
If someone knows how to do without, please
On 07/23/2014 08:25 AM, Yang Hongyang wrote:
Virtual machine (VM) replication is a well known technique for
providing application-agnostic software-implemented hardware fault
tolerance non-stop service. COLO is a high availability solution.
Both primary VM (PVM) and secondary VM (SVM) run in
On 07/23/2014 08:25 AM, Yang Hongyang wrote:
introduce an api colo_supported() to indicate COLO support, returns
true if colo supported(configured with --enable-colo).
Space before () in English sentences:
s/supported(configured/supported (configured/
As I mentioned in the cover letter,
On 07/23/2014 08:25 AM, Yang Hongyang wrote:
Guest will enter this state when paused to save/resore VM state
s/resore/restore/
under colo checkpoint.
Signed-off-by: Yang Hongyang yan...@cn.fujitsu.com
---
qapi-schema.json | 4 +++-
vl.c | 8
2 files changed, 11
On 07/23/2014 04:21 AM, Felix von Leitner wrote:
Public bug reported:
hxtool (part of the early build process) is a bash script. Running it
with /bin/sh yields a syntax error on line 10:
10 STEXI*|ETEXI*|SQMP*|EQMP*) flag=$(($flag^1))
$(( expr )) is a bash extension, not
I actually have bash installed as /bin/sh and /bin/bash.
But I also have heirloom sh installed, which installs itself as /sbin/sh, and
that happened to be first in my $PATH.
Since the makefiles use sh script to run the scripts, that called the
heirloom sh.
On 07/23/2014 10:13 AM, Felix von Leitner wrote:
I actually have bash installed as /bin/sh and /bin/bash.
But I also have heirloom sh installed, which installs itself as /sbin/sh, and
that happened to be first in my $PATH.
Since the makefiles use sh script to run the scripts, that called
Changing the ACPI table size causes migration to break, and the memory
hotplug work opened our eyes on how horribly we were breaking things in
2.0 already.
Unfortunately when reviewing the design I assumed incorrectly that all
tables would be placed in separate fw_cfg files. This would have been
This replaces the _PRT constant with a method that computes it.
The problem is that the DSDT+SSDT have grown from 2.0 to 2.1,
enough to cross the 8k barrier (we align the ACPI tables to 4k
before putting them in fw_cfg). This causes problems with
migration and the pc-2.0 machine type.
The
Changing the ACPI table size causes migration to break, and the memory
hotplug work opened our eyes on how horribly we were breaking things in
2.0 already.
The ACPI table size is rounded to the next 4k, which one would think
gives some headroom. In practice this is not the case, because the user
On 23 July 2014 16:04, Dmitry Poletaev poletaev-q...@yandex.ru wrote:
I'm understood. So, am I right?
Pretty much, except it's better to use the accessor functions
get_float_exception_flags() and set_float_exception_flags().
+if (env-fp_status.float_exception_flags FPUS_IE) {
+
On 23 July 2014 17:31, Eric Blake ebl...@redhat.com wrote:
Rather than change the Makefile to invoke the script with bash, we could
instead bend over backwards to rewrite the script in a way that works
with non-POSIX shells (as in, flag=`expr $flag ^ 1`), but that feels
backwards to me. Until
Hi everyone,
I am pleased to announce that the QEMU v1.7.2 stable release is now
available at:
http://wiki.qemu.org/download/qemu-1.7.2.tar.bz2
v1.7.2 is now tagged in the official qemu.git repository,
and the stable-1.7 branch has been updated accordingly:
On 07/23/2014 08:25 AM, Yang Hongyang wrote:
We need a buffer to store migration data.
On save side:
all saved data was write into colo buffer first, so that we can know
s/was write/is written/
the total size of the migration data. this can also separate the data
transmission from colo
On 07/23/14 18:37, Paolo Bonzini wrote:
This replaces the _PRT constant with a method that computes it.
The problem is that the DSDT+SSDT have grown from 2.0 to 2.1,
enough to cross the 8k barrier (we align the ACPI tables to 4k
before putting them in fw_cfg). This causes problems with
On 07/23/14 18:37, Paolo Bonzini wrote:
Changing the ACPI table size causes migration to break, and the memory
hotplug work opened our eyes on how horribly we were breaking things in
2.0 already.
The ACPI table size is rounded to the next 4k, which one would think
gives some headroom. In
kvm_set_phys_mem doesn't work on arm64 with memory 1GB. It exits with:
kvm_set_phys_mem: error registering slot: Invalid argument
An example of the failing address and size are start_addr == 0x90011000
and size=0xaffef000. As you can see both of these are 4K aligned, not
64K aligned.
At
Am 22.07.2014 17:47, schrieb Le Tan:
Add support for emulating Intel IOMMU according to the VT-d specification for
the q35 chipset machine. Implement the logic for DMAR (DMA remapping) without
PASID support. Use register-based invalidation for context-cache invalidation
and IOTLB invalidation.
On Sat, Jul 19, 2014 at 12:27:21AM +, Kay, Allen M wrote:
For the MCH PCI registers that do need to be read - can you tell us which
ones those are?
In qemu/hw/xen_pt_igd.c/igd_pci_read(), following MCH PCI config register
reads are passthrough to the host HW. Some of the registers
If bdrv_unref() is passed a NULL BDS pointer, it is safe to
exit with no operation. This will allow cleanup code to blindly
call bdrv_unref() on a BDS that has been initialized to NULL.
Reviewed-by: Max Reitz mre...@redhat.com
Signed-off-by: Jeff Cody jc...@redhat.com
---
block.c | 3 +++
1
Use the block layer to create, and write to, the image file in the
VDI .bdrv_create() operation.
This has a couple of benefits: Images can now be created over protocols,
and hacks such as NOCOW are not needed in the image format driver, and
the underlying file protocol appropriate for the host OS
Changes from v2 - v3:
* Patch 2: Removed extra #ifdef __linux__ from top of file (Max)
* Patch 4: Removed extra #ifdef __linux__ from top of file (Max)
* Patch 5: Removed output from debug cruft (Max)
* Added Max's R-b to remaining patches
Changes from v1 - v2:
* Patch 2:
Use the block layer to create, and write to, the image file in the VPC
.bdrv_create() operation.
This has a couple of benefits: Images can now be created over protocols,
and hacks such as NOCOW are not needed in the image format driver, and
the underlying file protocol appropriate for the host OS
This updates the VDI corruption test to also test static VDI image
creation, as well as the default dynamic image creation.
Reviewed-by: Max Reitz mre...@redhat.com
Signed-off-by: Jeff Cody jc...@redhat.com
---
tests/qemu-iotests/084 | 16 ++--
tests/qemu-iotests/084.out | 14
Most QEMU code uses 'ret' for function return values. The VDI driver
uses a mix of 'result' and 'ret'. This cleans that up, switching over
to the standard 'ret' usage.
Reviewed-by: Max Reitz mre...@redhat.com
Signed-off-by: Jeff Cody jc...@redhat.com
---
block/vdi.c | 36
On 23.07.14 17:33, Eric Auger wrote:
On 07/08/2014 03:52 PM, Alexander Graf wrote:
On 07.07.14 09:08, Eric Auger wrote:
This method is meant to be called on sysbus device dynamic
instantiation (-device option). Devices that support this
kind of instantiation must implement this method.
On 23.07.14 16:58, Eric Auger wrote:
On 07/08/2014 03:43 PM, Alexander Graf wrote:
On 07.07.14 09:08, Eric Auger wrote:
This new module implements routines which help in dynamic instantiation
of sysbus devices. Machine files can use those generic routines.
---
Dynamic sysbus device
Hi Paolo,
2014-07-23 15:58 GMT+08:00 Paolo Bonzini pbonz...@redhat.com:
Il 22/07/2014 17:47, Le Tan ha scritto:
+static inline void define_quad(IntelIOMMUState *s, hwaddr addr, uint64_t
val,
+uint64_t wmask, uint64_t w1cmask)
+{
+*((uint64_t *)s-csr[addr]) =
Hi Stefan,
2014-07-24 4:29 GMT+08:00 Stefan Weil s...@weilnetz.de:
Am 22.07.2014 17:47, schrieb Le Tan:
Add support for emulating Intel IOMMU according to the VT-d specification for
the q35 chipset machine. Implement the logic for DMAR (DMA remapping) without
PASID support. Use register-based
On Wed, Jul 16, 2014 at 10:29 AM, Michael Tokarev m...@tls.msk.ru wrote:
16.07.2014 21:23, ronnie sahlberg wrote:
If you ask debian to upgrade. Could you ask them to wait and upgrade after I
have release the next version, hopefully if all goes well, at the end
of this week?
There's no
On 2014/7/24 4:54, Konrad Rzeszutek Wilk wrote:
On Sat, Jul 19, 2014 at 12:27:21AM +, Kay, Allen M wrote:
For the MCH PCI registers that do need to be read - can you tell us which ones
those are?
In qemu/hw/xen_pt_igd.c/igd_pci_read(), following MCH PCI config register reads
are
From: Hu Tao hu...@cn.fujitsu.com
This patch is to solve a problem that when you add a hot-pluggable memory,
you can't remove the memory.
Its approach is to set GPE status bit by qemu, then trigger SCI interrupt to
notify
guest os. Guest os checks device status, and free memory resource if
On 07/23/2014 11:44 PM, Eric Blake wrote:
On 07/23/2014 08:25 AM, Yang Hongyang wrote:
Virtual machine (VM) replication is a well known technique for
providing application-agnostic software-implemented hardware fault
tolerance non-stop service. COLO is a high availability solution.
Both primary
On Mon, 07/21 14:18, Maria Kustova wrote:
The purpose of the test runner is to prepare the test environment (e.g. create
a work directory, a test image, etc), execute a program under test with
parameters, indicate a test failure if the program was killed during the test
execution and collect
Note that on a successful boot, dmesg | grep cirrus shows:
[9.064581] fb: conflicting fb hw usage cirrusdrmfb vs EFI VGA - removing
generic driver
[9.133808] fbcon: cirrusdrmfb (fb0) is primary device
[9.431359] cirrus :00:02.0: fb0: cirrusdrmfb frame buffer device
[9.431362]
96 matches
Mail list logo
