From: "Dr. David Alan Gilbert"
Notify the vhost-user client on reception of the 'postcopy-listen'
event from the source.
Signed-off-by: Dr. David Alan Gilbert
---
contrib/libvhost-user/libvhost-user.c | 16
contrib/libvhost-user/libvhost-user.h | 2 ++
hw/virtio/trace-events
From: "Dr. David Alan Gilbert"
Allow other userfaultfd's to be registered into the fault thread
so that handlers for shared memory can get responses.
Signed-off-by: Dr. David Alan Gilbert
---
migration/migration.c| 3 +
migration/migration.h| 2 +
migration/postcopy-ram.c | 212 +++
On Tue, Jun 27, 2017 at 12:10:18PM +0800, Peter Xu wrote:
> These two parameters:
>
> - MachineState::enforce_config_section
> - MigrationState::send_configuration
>
> are playing similar role here. This patch merges the first one into
> second, then we'll have a single place to reference whether
From: "Dr. David Alan Gilbert"
Stash the RAMBlock and offset for later use looking up
addresses.
Signed-off-by: Dr. David Alan Gilbert
---
hw/virtio/trace-events | 1 +
hw/virtio/vhost-user.c | 11 +++
2 files changed, 12 insertions(+)
diff --git a/hw/virtio/trace-events b/hw/virtio/
From: "Dr. David Alan Gilbert"
Allow replies with fds (for postcopy)
Signed-off-by: Dr. David Alan Gilbert
---
contrib/libvhost-user/libvhost-user.c | 29 -
1 file changed, 28 insertions(+), 1 deletion(-)
diff --git a/contrib/libvhost-user/libvhost-user.c
b/contri
From: "Dr. David Alan Gilbert"
Register the UFD that comes in as the response to the 'advise' method
with the postcopy code.
Signed-off-by: Dr. David Alan Gilbert
---
hw/virtio/vhost-user.c | 23 ++-
migration/postcopy-ram.h | 2 +-
2 files changed, 23 insertions(+), 2 d
From: "Dr. David Alan Gilbert"
Send requests back to the source for shared page requests.
Signed-off-by: Dr. David Alan Gilbert
---
migration/migration.h| 2 ++
migration/postcopy-ram.c | 31 ---
migration/postcopy-ram.h | 3 +++
migration/trace-events | 2
From: "Dr. David Alan Gilbert"
Add a hook to allow a client userfaultfd to be 'woken'
when a page arrives, and a walker that calls that
hook for relevant clients given a RAMBlock and offset.
Signed-off-by: Dr. David Alan Gilbert
---
migration/postcopy-ram.c | 16
migration/pos
From: "Dr. David Alan Gilbert"
When new regions are sent to the client using SET_MEM_TABLE, register
them with the userfaultfd.
Signed-off-by: Dr. David Alan Gilbert
---
contrib/libvhost-user/libvhost-user.c | 33 +
1 file changed, 33 insertions(+)
diff --git a
From: "Dr. David Alan Gilbert"
Resolve fault addresses read off the clients UFD into RAMBlock
and offset, and call back to the postcopy code to ask for the page.
Signed-off-by: Dr. David Alan Gilbert
---
hw/virtio/trace-events | 3 +++
hw/virtio/vhost-user.c | 28 +++-
From: "Dr. David Alan Gilbert"
Register a waker function in vhost-user code to be notified when
pages arrive or requests to previously mapped pages get requested.
Signed-off-by: Dr. David Alan Gilbert
---
hw/virtio/trace-events | 3 +++
hw/virtio/vhost-user.c | 26 ++
From: "Dr. David Alan Gilbert"
We need a better way, but at the moment we need the address of the
mappings sent back to qemu so it can interpret the messages on the
userfaultfd it reads.
Signed-off-by: Dr. David Alan Gilbert
---
contrib/libvhost-user/libvhost-user.c | 15 +-
hw/virtio/
From: "Dr. David Alan Gilbert"
Cause the vhost-user client to be woken up whenever:
a) We place a page in postcopy mode
b) We get a fault and the page has already been received
Signed-off-by: Dr. David Alan Gilbert
---
migration/postcopy-ram.c | 14 ++
migration/trace-events
From: "Dr. David Alan Gilbert"
Send a 'wake' request on a userfaultfd for a shared process.
The address in the clients address space is specified together
with the RAMBlock it was resolved to.
Signed-off-by: Dr. David Alan Gilbert
---
migration/postcopy-ram.c | 26 ++
m
From: "Dr. David Alan Gilbert"
When we receive a GET_VRING_BASE message set enable = false
to stop any new received packets modifying the ring.
Signed-off-by: Dr. David Alan Gilbert
---
contrib/libvhost-user/libvhost-user.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/contrib/libvhost-u
From: "Dr. David Alan Gilbert"
Clear the area and turn off THP.
Signed-off-by: Dr. David Alan Gilbert
---
contrib/libvhost-user/libvhost-user.c | 32 ++--
1 file changed, 30 insertions(+), 2 deletions(-)
diff --git a/contrib/libvhost-user/libvhost-user.c
b/contrib
From: "Dr. David Alan Gilbert"
Wire up a call to VHOST_USER_POSTCOPY_END message to the vhost clients
right before we ask the listener thread to shutdown.
Signed-off-by: Dr. David Alan Gilbert
---
hw/virtio/trace-events | 2 ++
hw/virtio/vhost-user.c | 30 ++
m
From: "Dr. David Alan Gilbert"
**HACK - better solution needed **
We have the situation where:
qemu bridge
send set_mem_table
map memory
a) mark area with UFD
send reply with ma
From: "Dr. David Alan Gilbert"
Tell QEMU we understand the protocol features needed for postcopy.
Signed-off-by: Dr. David Alan Gilbert
---
contrib/libvhost-user/libvhost-user.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/contrib/libvhost-user/libvhost-user.c
b/contr
From: "Dr. David Alan Gilbert"
Now that we have the mechanisms in here, allow shared memory in a
postcopy.
Signed-off-by: Dr. David Alan Gilbert
---
migration/postcopy-ram.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/migration/postcopy-ram.c b/migration/postcopy-ram.c
index fdd53
On Tue, Jun 27, 2017 at 12:10:15PM +0800, Peter Xu wrote:
> One less global variable, and it does only matter with migration.
>
> We keep the old "--only-migratable" option, but also now we support:
>
> -global migration.only-migratable=true
>
> Currently still keep the old interface.
>
> Hmm
The [NSEvent modifierFlags] method returns an NSEventModifierFlags type value
in Mac OS 10.10. It use to be of type NSUInteger. Replacing
NSEventModifierFlags with NSUInteger allows for the cooca.m file to be compiled
on older versions of Mac OS. This patch was been tested on Mac OS 10.6 and Mac
On 06/28/2017 01:47 PM, Stefan Hajnoczi wrote:
> This patch series fixes qemu-iotests 068. Since commit
> ea4f3cebc4e0224605ab9dd9724aa4e7768fe372 ("qemu-iotests: 068: test iothread
> mode") the test case has attempted to use dataplane without -M accel=kvm.
> Although QEMU is capable of running TC
In ppc_spapr_init when setting rma_size we have the following verification:
if (rma_alloc_size && (rma_alloc_size < node0_size)) {
spapr->rma_size = rma_alloc_size;
} else {
spapr->rma_size = node0_size;
/* With KVM, we don't actually know whether KVM supports an
On Wed, 28 Jun 2017 11:54:28 -0700 (PDT)
Stefano Stabellini wrote:
[...]
> > > @@ -125,10 +127,19 @@ static ssize_t xen_9pfs_pdu_vmarshal(V9fsPDU *pdu,
> > > Xen9pfsDev *xen_9pfs = container_of(pdu->s, Xen9pfsDev, state);
> > > struct iovec in_sg[2];
> > > int num;
> > > +ssize_
On Wed, 28 Jun 2017, Greg Kurz wrote:
> On Wed, 28 Jun 2017 11:54:28 -0700 (PDT)
> Stefano Stabellini wrote:
> [...]
> > > > @@ -125,10 +127,19 @@ static ssize_t xen_9pfs_pdu_vmarshal(V9fsPDU *pdu,
> > > > Xen9pfsDev *xen_9pfs = container_of(pdu->s, Xen9pfsDev, state);
> > > > struct iov
Le 27/06/2017 à 22:00, Richard Henderson a écrit :
> On 06/27/2017 12:12 PM, Laurent Vivier wrote:
>> case 3: /* Ordered Greater than or Equal Z || !(A || N) */
>> case 19: /* Greater than or Equal Z || !(A || N) */
>> +g_assert(FPSR_CC_A == (FPSR_CC_N >> 3));
>> +c->v1
On Wed 28 Jun 2017 04:58:00 PM CEST, Kashyap Chamarthy wrote:
> This patch documents (including their QMP invocations) all the four
> major kinds of live block operations:
>
> - `block-stream`
> - `block-commit`
> - `drive-mirror` (& `blockdev-mirror`)
> - `drive-backup` (& `blockdev-backup
On 06/28/2017 03:15 PM, Alberto Garcia wrote:
> On Wed 28 Jun 2017 04:58:00 PM CEST, Kashyap Chamarthy wrote:
>> This patch documents (including their QMP invocations) all the four
>> major kinds of live block operations:
>>
>> - `block-stream`
>> - `block-commit`
>> - `drive-mirror` (& `bloc
Second part of patches submitted in the v3.
This series adds a subset of single precision and
double precision instructions using
set_floatx80_rounding_precision() to round the result.
For some other instructions, we introduce a new
function, floatx80_round(), to round them manually.
It also add
fmovecr moves a floating point constant from the
FPU ROM to a floating point register.
Signed-off-by: Laurent Vivier
Reviewed-by: Richard Henderson
Reviewed-by: Philippe Mathieu-Daudé
---
target/m68k/fpu_helper.c | 34 ++
target/m68k/helper.h | 1 +
target/
fsglmul and fsgldiv truncate data to single precision before computing
results.
Signed-off-by: Laurent Vivier
Reviewed-by: Richard Henderson
---
target/m68k/fpu_helper.c | 28
target/m68k/helper.h | 2 ++
target/m68k/translate.c | 6 ++
3 files changed, 3
Add fssqrt, fdsqrt, fsadd, fdadd, fssub, fdsub, fsmul, fdmul,
fsdiv, fddiv.
The precision is managed using set_floatx80_rounding_precision().
Signed-off-by: Laurent Vivier
Reviewed-by: Richard Henderson
---
target/m68k/fpu_helper.c | 80
target/
use DisasCompare with FPU conditions in fscc and fbcc.
Signed-off-by: Laurent Vivier
---
target/m68k/translate.c | 210 ++--
1 file changed, 131 insertions(+), 79 deletions(-)
diff --git a/target/m68k/translate.c b/target/m68k/translate.c
index 7aa0fd
Add fsabs, fdabs, fsneg, fdneg, fsmove and fdmove.
The value is converted using the new floatx80_round() function.
Signed-off-by: Laurent Vivier
Reviewed-by: Richard Henderson
---
target/m68k/fpu_helper.c | 48 +---
target/m68k/helper.h | 8
From: Stefano Stabellini
Implement xen_9pfs_disconnect by unbinding the event channels. On
xen_9pfs_free, call disconnect if any event channels haven't been
disconnected.
If the frontend misconfigured the buffers set the backend to "Closing"
and disconnect it. Misconfigurations include requestin
Add a function to round a floatx80 to the defined precision
(floatx80_rounding_precision)
Signed-off-by: Laurent Vivier
Reviewed-by: Richard Henderson
Reviewed-by: Aurelien Jarno
---
fpu/softfloat.c | 16
include/fpu/softfloat.h | 1 +
2 files changed, 17 insertions(+
The 9p protocol relies on a reliable transport, but the current code
treats transport errors (ie, failure to marshal or unmarshal) as if
they were coming from the backend. This doesn't make sense: if the
transport failed, we should notify the guest that the transport is
broken and needs to be reset
Signed-off-by: Laurent Vivier
Reviewed-by: Richard Henderson
---
target/m68k/fpu_helper.c | 120 +++
target/m68k/helper.h | 6 +++
target/m68k/translate.c | 93
3 files changed, 189 insertions(+), 30 deletio
The 9p spec at http://man.cat-v.org/plan_9/5/intro reads:
"Each 9P message begins with a four-byte size field specify-
ing the length in bytes of the complete message including
the four bytes of the size field itself. The next byte is
the message type, one of the constants in the enumerati
If the guest sends a malformed request, we end up with a dangling pointer
in V9fsVirtioState. This doesn't seem to cause any bug, but let's remove
this side effect anyway.
Signed-off-by: Greg Kurz
Reviewed-by: Michael S. Tsirkin
---
hw/9pfs/virtio-9p-device.c |3 ++-
1 file changed, 2 inser
The 9P protocol is transport agnostic: if the guest misconfigured the
buffers, the best we can do is to set the broken flag on the device.
Since virtio_pdu_vmarshal() may be called by several active PDUs, we
check if the transport isn't broken already to avoid printing extra
error messages.
Signe
The ucontext_t type had a tag struct ucontext until now
but newer glibc will drop it so we need to adjust and use
the exposed type instead
Signed-off-by: Khem Raj
Cc: Kamil Rytarowski
Cc: Riku Voipio
Cc: Laurent Vivier
Cc: Paolo Bonzini
---
linux-user/host/aarch64/hostdep.h | 2 +-
linux-us
Contrary to what is written in the comment, a buggy guest can misconfigure
the transport buffers and pdu_marshal() may return an error. If this ever
happens, it is up to the transport layer to handle the situation (9P is
transport agnostic).
This fixes Coverity issue CID1348518.
Signed-off-by: G
Riku,
could you ACK this patch, so I will add it in my next pull request for m68k?
Thanks,
Laurent
Le 20/06/2017 à 22:51, Laurent Vivier a écrit :
> Signed-off-by: Laurent Vivier
> ---
> linux-user/signal.c | 41 +
> 1 file changed, 41 insertions(+)
>
>
On 06/28/2017 12:44 PM, Laszlo Ersek wrote:
On 06/28/17 17:22, Peter Jones wrote:
On Tue, Jun 27, 2017 at 12:12:50PM -0400, Stefan Berger wrote:
On 06/14/2017 09:51 AM, Laszlo Ersek wrote:
Hi Stefan,
the MAINTAINERS file doesn't seem to cover any of the TPM-related files
in the tree:
bac
Hi
On Fri, Jun 23, 2017 at 6:28 AM Jia-Shiun Li wrote:
> In commit 9e0bc24f dev->log_size was reset to zero too early before
> syncing vhost log. It causes syncing to be skipped.
>
>
ooch, I guess I didn't realize it was also accessing dev->log_size when
taking dev->log in local variable.
I won
On 06/28/17 22:57, Stefan Berger wrote:
> On 06/28/2017 12:44 PM, Laszlo Ersek wrote:
>> On 06/28/17 17:22, Peter Jones wrote:
>>> On Tue, Jun 27, 2017 at 12:12:50PM -0400, Stefan Berger wrote:
On 06/14/2017 09:51 AM, Laszlo Ersek wrote:
> Hi Stefan,
>
> the MAINTAINERS file doesn'
On 2017-06-26 13:04, sochin.jiang wrote:
> From: "sochin.jiang"
>
> mirror_complete opens the backings, BDSs of the new open backings should
> have a
> same AioContext with the top when using iothreads, fix the code to guarantee
> this,
> also avoiding unexpected qemu exit(assert fails in bd
On Wed, 28 Jun 2017, Greg Kurz wrote:
> The 9p spec at http://man.cat-v.org/plan_9/5/intro reads:
>
> "Each 9P message begins with a four-byte size field specify-
> ing the length in bytes of the complete message including
> the four bytes of the size field itself. The next byte is
> the m
Eduardo Habkost wrote:
>
> So, this is a case where a user-provided config option (-machine
> enforce-config-section) should trigger a different default in another
> class (migration.send-configuration).
>
> Also, the new default triggered by -machine has a very specific
> priority:
>
> * AccelCl
On Wed, 28 Jun 2017, Greg Kurz wrote:
> Contrary to what is written in the comment, a buggy guest can misconfigure
> the transport buffers and pdu_marshal() may return an error. If this ever
> happens, it is up to the transport layer to handle the situation (9P is
> transport agnostic).
>
> This
On Wed, Jun 28, 2017 at 14:21:29 +0300, Lluís Vilanova wrote:
> Emilio G Cota writes:
> > I wanted to save you some time and sent a v9 yesterday with these
> > same changes -- although I see some changes in my v8 didn't make it
> > to your v9. For this iteration I only added more perf numbers to th
Signed-off-by: Max Reitz
---
Depends on Stefan's "virtio: use ioeventfd in TCG and qtest mode" series
to work at all, and on "mirror: Fix inconsistent backing AioContext for
after mirroring" (in my block branch) so it does not fail.
---
tests/qemu-iotests/106 | 97
On 2017-06-28 17:31, Pavel Butsykin wrote:
> On 28.06.2017 16:59, Max Reitz wrote:
>> On 2017-06-27 17:06, Pavel Butsykin wrote:
>>> On 26.06.2017 20:47, Max Reitz wrote:
On 2017-06-26 17:23, Pavel Butsykin wrote:
>>> []
>
> Is there any guarantee that in the future this will not chang
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Thursday, June 29, 2017 12:00 AM
>
> On Wed, 28 Jun 2017 06:04:10 +
> "Tian, Kevin" wrote:
>
> > > From: Alex Williamson [mailto:alex.william...@redhat.com]
> > > Sent: Wednesday, June 28, 2017 3:45 AM
> > >
> > > On Tue, 27
On 06/28/2017 11:59 AM, Vladimir Sementsov-Ogievskiy wrote:
> 27.06.2017 02:19, John Snow wrote:
>>
>> On 06/06/2017 12:26 PM, Vladimir Sementsov-Ogievskiy wrote:
>>> The function should collect statistics, about used/unused by top-level
>>> format driver space (in its .file) and allocation statu
Hi everyone. Hoping to get some feedback on this approach, or some
alternatives proposed below, to the following issue:
Currently libvirt immediately attempts to rebind a managed device back to the
host driver when it receives a DEVICE_DELETED event from QEMU. This is
problematic for 2 reasons:
1
This serves a similar purpose to virPCIDeviceAddressIOMMUGroupIterate,
but uses the iommu group number to find matches instead of a device
within the group. We refactor the code to use this new function and
also export it for use in subsequent patches.
Signed-off-by: Michael Roth
---
src/util/vi
QEMU emits DEVICE_DELETED events during a device's "unparent"
callback, but some additional cleanup occurs afterward via
"finalize". In most cases libvirt can ignore the latter, but in the
case of VFIO the closing of a device's group FD happens here, which
is something libvirt needs to wait for bef
Signed-off-by: Michael Roth
---
src/libvirt_private.syms | 1 +
src/util/virhostdev.c| 83
src/util/virhostdev.h| 8 +
3 files changed, 78 insertions(+), 14 deletions(-)
diff --git a/src/libvirt_private.syms b/src/libvirt_private.sym
It's only called from one place, and only takes the extra step of
freeing the device alias after reattach. Since another path through
qemuDomainRemoveHostDevice introduced in a subsequent patch will also
need to free the device alias, it'll be more readable to just start
calling it directly.
Signe
Currently we bind a managed hostdev back to the host driver (or
"unbind" from the perspective of the stub driver) immediately upon
receiving a DEVICE_DELETED event from QEMU. In cases where we have
more one device from the group attached to a guest, this runs the risk
of putting the group in a "non
There have been some comments on the ML about the usefulness of tci.
https://lists.nongnu.org/archive/html/qemu-devel/2017-06/msg04551.html
Peter Maydell> I'd prefer we just got rid of it.
https://lists.nongnu.org/archive/html/qemu-devel/2017-06/msg04296.html
Richard Henderson> Is it time t
moved in a9ded601..244f1441 to accel/
Signed-off-by: Philippe Mathieu-Daudé
---
MAINTAINERS | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 839f7ca063..06006fc7df 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -84,14 +84,10 @@ M: Paolo Bonz
moved in 92229a57 to accel/
Signed-off-by: Philippe Mathieu-Daudé
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 06006fc7df..86a08c5aac 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -273,8 +273,8 @@ Overall
M: Paolo Bonzini
TCI + MTTCG cause strange errors...
$ arm-softmmu/qemu-system-arm -machine raspi2 -cpu cortex-a7 -smp 4 -accel
tcg,thread=multi -kernel kernel7.img
qemu-system-arm: Guest expects a stronger memory ordering than the host
provides
This may cause strange/hard to debug errors
Segmentation fa
remove some copy/paste leftover, code seems sane.
while running Alex Bennée's image aarch64-linux-3.15rc2-buildroot.img:
Trace 0x7fa1904b0890 [0: ffc00036cd04]
IN:
0xffc00036cd24: 5ac00694 rev16 w20, w20
OP:
ffc00036cd24
moved in 56e2cd24..28b99f47 to accel/
Signed-off-by: Philippe Mathieu-Daudé
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 86a08c5aac..530293044b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -323,7 +323,6 @@ M: Stefano Stabellini
M: Anthony
"./configure --disable-tcg-interpreter" generates a warning:
./configure: --disable-tcg-interpreter is obsolete, Experimental TCG
interpreter has been removed"
"./configure --enable-tcg-interpreter" generates an error:
Experimental TCG interpreter has been removed
Signed-off-by: Philippe M
moved in 244f1441 to tcg/
Signed-off-by: Philippe Mathieu-Daudé
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 530293044b..9bad523060 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1654,7 +1654,7 @@ TCI target
M: Stefan Weil
Signed-off-by: Philippe Mathieu-Daudé
---
.travis.yml | 3 ---
1 file changed, 3 deletions(-)
diff --git a/.travis.yml b/.travis.yml
index 27a2d9cfb3..d10ee5ed79 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -74,9 +74,6 @@ matrix:
- env: CONFIG="--enable-gprof --enable-gcov --disable-pie"
Oh，I got it, thanks.
Sochin
On 2017/6/29 6:33, Max Reitz wrote:
> On 2017-06-26 13:04, sochin.jiang wrote:
>> From: "sochin.jiang"
>>
>> mirror_complete opens the backings, BDSs of the new open backings should
>> have a
>> same AioContext with the top when using iothreads, fix the code to
On Wed, Jun 28, 2017 at 04:13:57PM -0300, Eduardo Habkost wrote:
> On Tue, Jun 27, 2017 at 12:10:15PM +0800, Peter Xu wrote:
> > One less global variable, and it does only matter with migration.
> >
> > We keep the old "--only-migratable" option, but also now we support:
> >
> > -global migrati
On Thu, Jun 29, 2017 at 12:42:56AM +0200, Juan Quintela wrote:
> Eduardo Habkost wrote:
>
> >
> > So, this is a case where a user-provided config option (-machine
> > enforce-config-section) should trigger a different default in another
> > class (migration.send-configuration).
> >
> > Also, the
Hi, Daniel
On 06/28/2017 09:23 PM, Daniel P. Berrange wrote:
On Wed, Jun 28, 2017 at 09:08:49PM +0800, Mao Zhongyi wrote:
diff --git a/include/qemu/sockets.h b/include/qemu/sockets.h
index 5c326db..78e2b30 100644
--- a/include/qemu/sockets.h
+++ b/include/qemu/sockets.h
if (qemu_isd
Hi, Daniel
On 06/28/2017 09:27 PM, Daniel P. Berrange wrote:
On Wed, Jun 28, 2017 at 09:08:50PM +0800, Mao Zhongyi wrote:
When -net socket fails, it first reports a specific error, then
a generic one, like this:
$ qemu-system-x86_64 -net socket,
qemu-system-x86_64: -net socket: exactly
On Wed, Jun 28, 2017 at 12:37:04PM -0300, Eduardo Habkost wrote:
> On Wed, Jun 28, 2017 at 03:15:44PM +0800, Peter Xu wrote:
> > It'll be strange that the migration object inherits TYPE_DEVICE. Add
> > some explanations to it.
> >
> > Signed-off-by: Peter Xu
> > ---
> > migration/migration.c | 8
Hi, Eric
On 06/28/2017 10:23 PM, Eric Blake wrote:
On 06/28/2017 08:18 AM, Daniel P. Berrange wrote:
On Wed, Jun 28, 2017 at 09:08:47PM +0800, Mao Zhongyi wrote:
In net_socket_fd_init(), the 'default' case is odd: it warns,
then continues as if the socket type was SOCK_STREAM. The
comment expl
On Wed, Jun 28, 2017 at 08:49:32AM -0400, Alexey Perevalov wrote:
[...]
> @@ -2324,8 +2352,14 @@ static int ram_load_setup(QEMUFile *f, void *opaque)
[1]
>
> static int ram_load_cleanup(void *opaque)
> {
> +RAMBlock *rb;
> xbzrle_load_cleanup();
> compress_threads_load_cleanup
Migration is broken after the vfio integration work:
qemu-kvm: AHCI: Failed to start FIS receive engine: bad FIS receive buffer
address
qemu-kvm: Failed to load ich9_ahci:ahci
qemu-kvm: error while loading state for instance 0x0 of device
':00:1f.2/ich9_ahci'
qemu-kvm: load of migration fail
The Processor Compatibility Register (PCR) I used to set the
compatibility mode of the processor using the SET_ONE_REG ioctl on
KVM_REG_PPC_ARCH_COMPAT. Previously this was only called when a compat
mode was actually in use, however a recent patch made it unconditional.
Calling this in KVM_PR fails
On Wed, 2017-06-28 at 18:41 +0200, Greg Kurz wrote:
> On Wed, 28 Jun 2017 18:18:06 +0200
> Laurent Vivier wrote:
>
> > On 28/06/2017 13:59, Greg Kurz wrote:
> > > On Wed, 28 Jun 2017 12:23:06 +0200
> > > Cédric Le Goater wrote:
> > >
> > > > On 06/28/2017 11:18 AM, Laurent Vivier wrote:
> >
On Thu, 2017-06-29 at 15:37 +1000, Suraj Jitindar Singh wrote:
> On Wed, 2017-06-28 at 18:41 +0200, Greg Kurz wrote:
> > On Wed, 28 Jun 2017 18:18:06 +0200
> > Laurent Vivier wrote:
> >
> > > On 28/06/2017 13:59, Greg Kurz wrote:
> > > > On Wed, 28 Jun 2017 12:23:06 +0200
> > > > Cédric Le Goater
bdrv_open_driver() is called in two places, bdrv_new_open_driver() and
bdrv_open_common(). In the latter, failure cleanup in is in its caller,
bdrv_open_inherit(), which unrefs the bs->file of the failed driver open
if it exists. Let's check for this in bdrv_new_open_driver() as well.
Signed-off-b
Hi Michal,
Currently the sun4v machine is still at an alpha stage. Artyom has made
some good progress on the niagara machine which was merged for the 2.9
release and is able to run several OSs, so please try that and let us
know how you get on.
Note that I generally try and keep the wiki page at
Emilio G Cota writes:
> On Wed, Jun 28, 2017 at 14:21:29 +0300, Lluís Vilanova wrote:
>> Emilio G Cota writes:
>> > I wanted to save you some time and sent a v9 yesterday with these
>> > same changes -- although I see some changes in my v8 didn't make it
>> > to your v9. For this iteration I only
On 29.06.2017 07:37, Suraj Jitindar Singh wrote:
> On Wed, 2017-06-28 at 18:41 +0200, Greg Kurz wrote:
>> On Wed, 28 Jun 2017 18:18:06 +0200
>> Laurent Vivier wrote:
>>
>>> On 28/06/2017 13:59, Greg Kurz wrote:
On Wed, 28 Jun 2017 12:23:06 +0200
Cédric Le Goater wrote:
> On
Eduardo Habkost writes:
> On Wed, Jun 28, 2017 at 11:05:26AM +0200, Markus Armbruster wrote:
>> Eduardo Habkost writes:
>>
>> > Rationale
>> > -
>> >
>> > I'm often bothered by the fact that we can't write the following:
>> >
>> > foo(arg, errp);
>> > if (*errp) {
>> > h
On 27/06/17 18:59, Pasha Tatashin wrote:
Hi Pasha,
> Hi,
>
> I am trying to evaluate the current qemu support for sparc64 processors.
> First, it seems -smp is not supported for any processor, is this
> correct? When I set -smp greater than 1, I am getting:
>
> qemu-system-sparc64: Number of SM
29.06.2017 03:15, John Snow wrote:
On 06/28/2017 11:59 AM, Vladimir Sementsov-Ogievskiy wrote:
27.06.2017 02:19, John Snow wrote:
On 06/06/2017 12:26 PM, Vladimir Sementsov-Ogievskiy wrote:
The function should collect statistics, about used/unused by top-level
format driver space (in its .fil
301 - 391 of 391 matches
Mail list logo
