On Tue, Jun 23, 2015 at 07:39:33PM -0400, Don Slutz wrote:
> From: Don Slutz
>
> This is done by adding a new machine property vmware-port-ring3 that
> needs to be enabled to have any effect. It only effects accel=tcg
> mode. It is needed if you want to use VMware tools in accel=tcg
> mode.
>
after try the patch
http://lists.nongnu.org/archive/html/qemu-devel/2015-06/msg07377.html with
qemu.git commit(d2966f804d70a244f5dde395fc5d22a50ed3e74e)
the guest can get IP, but after save/retore or live migration, the guest is
alive, but ping or ssh guest's IP fail .
--
You received this bu
On 2015/7/1 0:38, Dr. David Alan Gilbert wrote:
Hi,
An observation I've got, and this is from the previous version; if there
is a problem with the network that carries the comparison traffic, the failure
is
difficult to dtect - you start COLO both VMs seem to be running and COLO
starts up fi
On Tue, Jun 30, 2015 at 02:16:59PM +0800, Hong Bo Li wrote:
>
> On 6/29/2015 18:01, Michael S. Tsirkin wrote:
> >On Mon, Jun 29, 2015 at 05:24:53PM +0800, Hong Bo Li wrote:
> >>This patch introduce a new facility(and bus)
> >>to hold devices representing information actually
> >>provided by s390 f
ne2000_receive already checks the same conditions and drops the packet
if it's not ready, removing the .can_receive callback avoids the
necessity to add explicit flushes when the conditions turn true (which
is required by the new semantics of .can_receive since 6e99c63
"net/socket: Drop net_socket_
Ugh, sorry, this version is buggy, I'll resend.
On Wed, Jul 01, 2015 at 01:51:43PM +1000, David Gibson wrote:
> From: Greg Kurz
>
> If a guest passes the reg property of a valid VIO object that is not a VTY
> to either H_GET_TERM_CHAR or H_PUT_TERM_CHAR, QEMU hits a dynamic cast
> assertion and
If a guest passes the reg property of a valid VIO object that is not a VTY
to either H_GET_TERM_CHAR or H_PUT_TERM_CHAR, QEMU hits a dynamic cast
assertion and aborts.
PAPR+ says "Hypervisor checks the termno parameter for validity against the
Vterm IOA unit addresses assigned to the partition, el
On Mon, Jun 29, 2015 at 11:35:23AM +0100, Peter Maydell wrote:
> On 29 June 2015 at 06:36, David Gibson wrote:
> > At present, the core device model code for 8250-like serial ports
> > (serial.c) and the code for serial ports attached to ISA-style legacy IO
> > (serial-isa.c) are both controlled b
On 07/01/2015 11:09 AM, Michael R. Hines wrote:
> On 03/25/2015 04:36 AM, Wen Congyang wrote:
>> Block replication is a very important feature which is used for
>> continuous checkpoints(for example: COLO).
>>
>> Usage:
>> Please refer to docs/block-replication.txt
>>
>> You can get the patch here:
On Tue, Jun 30, 2015 at 02:04:31PM +0200, Greg Kurz wrote:
> If a guest passes the reg property of a valid VIO object that is not a VTY
> to either H_GET_TERM_CHAR or H_PUT_TERM_CHAR, QEMU hits a dynamic cast
> assertion and aborts.
>
> PAPR+ says "Hypervisor checks the termno parameter for validi
From: Greg Kurz
If a guest passes the reg property of a valid VIO object that is not a VTY
to either H_GET_TERM_CHAR or H_PUT_TERM_CHAR, QEMU hits a dynamic cast
assertion and aborts.
PAPR+ says "Hypervisor checks the termno parameter for validity against the
Vterm IOA unit addresses assigned to
On 03/25/2015 04:36 AM, Wen Congyang wrote:
Block replication is a very important feature which is used for
continuous checkpoints(for example: COLO).
Usage:
Please refer to docs/block-replication.txt
You can get the patch here:
https://github.com/wencongyang/qemu-colo/commits/block-replication
On Tue, 06/30 19:25, sfel...@gmail.com wrote:
> From: Scott Feldman
>
> Commit 6e99c63 ("net/socket: Drop net_socket_can_send") changed the
> semantics around .can_receive for sockets to now require the device to
> flush queued pkts when transitioning to a .can_receive=true state. Rocker
> devic
On Tue, Jun 30, 2015 at 6:47 PM, Fam Zheng wrote:
> On Tue, 06/30 07:41, sfel...@gmail.com wrote:
>> From: Scott Feldman
>>
>> Commit 6e99c63 ("net/socket: Drop net_socket_can_send") changed the
>> semantics around .can_receive for sockets to now require the device to
>> flush queued pkts when tr
Commit 6e99c63 ("net/socket: Drop net_socket_can_send") changed the
semantics around .can_receive for sockets to now require the device to
flush queued pkts when transitioning to a .can_receive=true state. But
it's OK to drop incoming packets when the link is not active.
Signed-off-by: Fam Zheng
From: Scott Feldman
Commit 6e99c63 ("net/socket: Drop net_socket_can_send") changed the
semantics around .can_receive for sockets to now require the device to
flush queued pkts when transitioning to a .can_receive=true state. Rocker
device was not flushing the queue on .can_receive=true transiti
On Tue, Jun 30, 2015 at 6:57 PM, Serge Vakulenko wrote:
> Hi Peter and Leon,
>
> With a bit of thinking, I agree, that the question of session
> termination on WAIT instruction is quite complicated in case of
> multi-core system, background i/o activity, mipsR6 core etc. So I'm
> going to find ano
> What you are suggesting is:
> If table_offset is not as expected, then check if it's a chelsio device.
> If it's not, then print a message. On the other hand, if it's a chelsio
> device, then let msix_init() catch the error. Why ? And if we are sure that
> msix_init will error out, what's the p
Hi Peter and Leon,
With a bit of thinking, I agree, that the question of session
termination on WAIT instruction is quite complicated in case of
multi-core system, background i/o activity, mipsR6 core etc. So I'm
going to find another solution for the task. What I essentially want
here is to stop
Right,
I may have send the patch a bit too soon, I need to take care of that.
-Original Message-
From: Bandan Das [mailto:b...@redhat.com]
Sent: Tuesday, June 30, 2015 6:48 PM
To: Gabriel Laupre
Cc: jb-gnumli...@wisemo.com; Casey Leedom; m...@redhat.com;
qemu-devel@nongnu.org; Anish Bha
Fix pba_offset initialization value for Chelsio T5 Virtual Function
device. The T5 hardware has a bug in it where it reports a Pending Interrupt
Bit Array Offset of 0x8000 for its SR-IOV Virtual Functions instead
of the 0x1000 that the hardware actually uses internally. As the hardware
doesn't retu
Gabriel Laupre writes:
> @ Bandan ...
>> > + + /* Chelsio T5 Virtual Function devices are encoded as 0x58xx
>> > for T5 + * adapters. The T5 hardware returns an incorrect value of
>> > 0x8000 for + * the VF PBA offset. The correct value is 0x1000, so
>> > we hard code that + * here. */ + if (vend
On Tue, 06/30 07:41, sfel...@gmail.com wrote:
> From: Scott Feldman
>
> Commit 6e99c63 ("net/socket: Drop net_socket_can_send") changed the
> semantics around .can_receive for sockets to now require the device to
> flush queued pkts when transitioning to a .can_receive=true state. Rocker
> devic
Ping...
Thanks
Tiejun
On 2015/6/5 16:44, Tiejun Chen wrote:
v8:
* Rebase on the latest qemu tree
* Cleanup one xen leftover in patch #3
v7:
* Instead of "-gfx_passthru" we'd like to make that a machine
option, "-machine xxx,igd-passthru=on""
* try to make something as common shared by oth
Hi Frederic,
Understood.
I will reorganize the patch set, run it through the checkpatch script
and resubmit.
Thanks,
--Serge
2015-06-30 1:16 GMT-07:00 Frederic Konrad :
> Hi,
>
> This is nice.
>
> You should use the checkpatch (script/checkpatch) to check the coding style
> of
> your patch.
> T
Hi Peter,
Thanks for feedback. I will prepare v2 patch set and resubmit it with
cover letter, as you proposed. Some other issues fixed as well.
Regards,
--Serge
2015-06-30 0:44 GMT-07:00 Peter Crosthwaite :
> Hi,
>
> On Mon, Jun 29, 2015 at 10:00 PM, Serge Vakulenko wrote:
>> Please find below
@ Bandan
...
> > +
> > +/* Chelsio T5 Virtual Function devices are encoded as 0x58xx for T5
> > + * adapters. The T5 hardware returns an incorrect value of 0x8000
> > for
> > + * the VF PBA offset. The correct value is 0x1000, so we hard code
> > that
> > + * here.
The 2.88 drive is more suitable as a default because
it can still read 1.44 images correctly, but the reverse
is not true.
Since there exist virtio-win drivers that are shipped on
2.88 floppy images, this patch will allow VMs booted without
a floppy disk inserted to later insert a 2.88MB floppy an
The old test assumes a 1.44MB drive.
Assert that the QEMU default drive is now either 1.44 or 2.88.
Signed-off-by: John Snow
---
tests/fdc-test.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/fdc-test.c b/tests/fdc-test.c
index 416394f..7c47385 100644
--- a/tests/fdc-
2.88MB capable drives can accept 1.44MB floppies,
for instance. To rework the pick_geometry function,
we need to know if our current drive can even accept
the type of disks we're considering.
NB: This allows us to distinguish between all of the
"total sectors" collisions between 1.20MB and 1.44MB
This one is the crazy one.
fd_revalidate currently uses pick_geometry to tell if the diskette
geometry has changed upon an eject/insert event, but it won't allow us
to insert a 1.44MB diskette into a 2.88MB drive. This is inflexible.
The new algorithm applies a new heuristic to guessing disk geom
Code motion: I want to refactor pick_geometry to work with
the FDrive type directly, so shuffle it below that definition.
Signed-off-by: John Snow
---
hw/block/fdc.c | 120 -
1 file changed, 60 insertions(+), 60 deletions(-)
diff --git a/h
Lessen the number of parameters it takes.
Signed-off-by: John Snow
---
hw/block/fdc.c | 39 +++
1 file changed, 15 insertions(+), 24 deletions(-)
diff --git a/hw/block/fdc.c b/hw/block/fdc.c
index be6bf25..4004b98 100644
--- a/hw/block/fdc.c
+++ b/hw/block/fd
We want to change the current default drive type,
but to be kind, we need to allow users to specify
the old drive type somehow.
Signed-off-by: John Snow
---
hw/block/fdc.c | 13 +
hw/core/qdev-properties.c| 12
include/hw/block/fdc.h | 7 +--
Allows us to distinguish between the current DISK type and the current
DRIVE type. The DRIVE is what's reported to CMOS, the DISK is whatever
the revalidate function suspects has been inserted into the drive.
The 'drive' field maintains the same meaning as it did previously, however,
the revalidat
Respect the default drive type as proffered via the CLI.
This patch overloads the "drive out" parameter of pick_geometry
to be used as a "default hint" which is offered by fd_revalidate.
Signed-off-by: John Snow
---
hw/block/fdc.c | 27 +--
1 file changed, 25 insertions(
What happens currently is if a drive is not inserted, we
won't match any of the drive types (None) or the geometries,
so we'll wind up picking the very first drive (1.44MB type)
as a default.
This patch makes the default picking a lot more explicit.
If a floppy image is inserted, QEMU will contin
Yep, it's been broken for 10 years too.
No, it's not a CVE.
The problem is that QEMU doesn't have a configuration option
for the type of floppy drive you want. It determines it based
on the diskette you insert at boot.
If you don't insert one, it always chooses a 1.44MB type.
I want to change th
Today, I shall continue to try the test for qemu linux-user, and try to
finish gcc testsuite within this month.
Welcome any ideas, suggestions, and completions.
Thanks.
On 06/19/2015 09:12 AM, Chen Gang wrote:
> On 06/19/2015 06:02 AM, Peter Maydell wrote:
>> On 13 June 2015 at 14:07, Chen Gang
On 06/30/2015 09:17 PM, Max Reitz wrote:
> On 29.06.2015 03:16, Wen Congyang wrote:
>> On 06/26/2015 11:16 PM, Max Reitz wrote:
>>> On 26.06.2015 16:27, Wen Congyang wrote:
At 2015/6/26 21:47, Max Reitz Wrote:
> On 25.06.2015 08:41, Wen Congyang wrote:
>> We can use block job mirror to
On 07/01/2015 03:01 AM, Dr. David Alan Gilbert wrote:
> * Wen Congyang (we...@cn.fujitsu.com) wrote:
>> On 06/27/2015 03:03 AM, Dr. David Alan Gilbert wrote:
>
>
>
>>> Ah, I hadn't realised you could do that; so do you just do:
>>>
>>> migrate_set_parameter colo on
>>> migrate -d -b tcp:otherhho
ping
On 06/24/2015 05:45 PM, Chen Fan wrote:
For now, for vfio pci passthough devices when qemu receives
an error from host aer report, there just terminate the guest,
but usually user want to know what error occurred but stop the
guest, so this patches add aer capability support for vfio device
On Tue, Jun 30, 2015 at 4:33 AM, Denis V. Lunev wrote:
> From: Andrey Smetanin
>
> Sending of notification is done by exiting vcpu to user space
> if KVM_REQ_HV_CRASH is enabled for vcpu. kvm_run structure
> will contains system_event with type KVM_SYSTEM_EVENT_CRASH
> and flag KVM_SYSTEM_EVENT_F
On Tue, Jun 30, 2015 at 4:33 AM, Denis V. Lunev wrote:
> From: Andrey Smetanin
>
> Hyper-V crash msr's are per vm, aren't per vcpu, so mark them
> as partition wide.
>
> Signed-off-by: Andrey Smetanin
> Signed-off-by: Denis V. Lunev
> CC: Paolo Bonzini
> CC: Gleb Natapov
Reviewed-by: Peter Ho
On Tue, Jun 30, 2015 at 4:33 AM, Denis V. Lunev wrote:
> From: Andrey Smetanin
>
> Added hyper-v crash msr's(HV_X64_MSR_CRASH*) data and control
> geters and setters.
>
> User space allowed to setup Hyper-V crash ctl msr.
> This msr should be setup to HV_X64_MSR_CRASH_CTL_NOTIFY
> value so Hyper-
On Tue, Jun 30, 2015 at 4:33 AM, Denis V. Lunev wrote:
> From: Andrey Smetanin
>
> Added KVM_REQ_HV_CRASH - vcpu request used for notify user space(QEMU)
> about Hyper-V crash.
>
> Signed-off-by: Andrey Smetanin
> Signed-off-by: Denis V. Lunev
> CC: Paolo Bonzini
> CC: Gleb Natapov
Reviewed-b
On Tue, Jun 30, 2015 at 4:33 AM, Denis V. Lunev wrote:
> From: Andrey Smetanin
>
> Added kvm Hyper-V context hv crash variables as storage
> of Hyper-V crash msrs.
>
> Signed-off-by: Andrey Smetanin
> Signed-off-by: Denis V. Lunev
> CC: Paolo Bonzini
> CC: Gleb Natapov
Reviewed-by: Peter Horn
On Tue, Jun 30, 2015 at 4:33 AM, Denis V. Lunev wrote:
> From: Andrey Smetanin
>
> Added Hyper-V crash msrs values - HV_X64_MSR_CRASH*.
>
> Signed-off-by: Andrey Smetanin
> Signed-off-by: Denis V. Lunev
> CC: Paolo Bonzini
> CC: Gleb Natapov
Reviewed-by: Peter Hornyack
> ---
> arch/x86/inc
On Tue, Jun 30, 2015 at 4:33 AM, Denis V. Lunev wrote:
> From: Andrey Smetanin
>
> vcpu_debug is useful macro like kvm_debug but additionally
> includes vcpu context inside output.
>
> Signed-off-by: Andrey Smetanin
> Signed-off-by: Denis V. Lunev
> CC: Paolo Bonzini
> CC: Gleb Natapov
Review
On Tue, Jun 30, 2015 at 4:33 AM, Denis V. Lunev wrote:
> From: Andrey Smetanin
>
> This patch introduce Hyper-V related source code file - hyperv.c and
> per vm and per vcpu hyperv context structures.
> All Hyper-V MSR's and hypercall code moved into hyperv.c.
> All Hyper-V kvm/vcpu fields moved
Le 30/06/2015 19:20, Peter Maydell a écrit :
> On 30 June 2015 at 18:13, Laurent Vivier wrote:
>>
>>
>> Le 30/06/2015 18:45, Peter Maydell a écrit :
>>> On 30 June 2015 at 17:19, Laurent Vivier wrote:
When guest base is disabled, RESERVED_VA is 0, and
(__guest < RESERVED_VA) is always
Nice one, thanks!
---
Sent from my phone
On 01/07/2015 1:43 am, "Peter Maydell" wrote:
> On 30 June 2015 at 16:02, Sergey Fedorov wrote:
> > TLBI ALLE1IS is an operation that does invalidate TLB entries on all PEs
> > in the same Inner Sharable domain, not just on the current CPU. So we
> > mus
Or you end up formalizing the concept of PCI Quirks as the kernel does rather
than scattering special exception code through the source ...
Casey
From: Alex Williamson [alex.william...@redhat.com]
Sent: Tuesday, June 30, 2015 3:28 PM
To: Bandan Das
Cc:
On Tue, 2015-06-30 at 17:58 -0400, Bandan Das wrote:
> Gabriel Laupre writes:
> ...
> > +/* Test the size of the pba variables and catch if they extend outside
> > of
> > + * the specified BAR. If it is the case, we have a broken
> > configuration or
> > + * we need to apply a hardwa
Gabriel Laupre writes:
...
> +/* Test the size of the pba variables and catch if they extend outside of
> + * the specified BAR. If it is the case, we have a broken configuration
> or
> + * we need to apply a hardware specific quirk. */
> +if (vdev->msix->table_offset >=
> +
Le 30/06/2015 19:49, Peter Maydell a écrit :
> Syscall 370 is name_to_handle_at, and 355 is signalfd4. (Likely if
> name_to_handle_at succeeds then it'll want open_by_handle_at too.)
>
> This patch implements the signalfd syscalls, though we haven't got to
> reviewing it yet.
> http://patchwork
On Tue, 2015-06-30 at 14:03 -0700, Gabriel Laupre wrote:
> Fix pba_offset initialization value for Chelsio T5 Virtual Function
> device. The T5 hardware has a bug in it where it reports a Pending Interrupt
> Bit Array Offset of 0x8000 for its SR-IOV Virtual Functions instead
> of the 0x1000 that th
Fix pba_offset initialization value for Chelsio T5 Virtual Function
device. The T5 hardware has a bug in it where it reports a Pending Interrupt
Bit Array Offset of 0x8000 for its SR-IOV Virtual Functions instead
of the 0x1000 that the hardware actually uses internally. As the hardware
doesn't retu
On Tue, Jun 30, 2015 at 1:16 PM, Peter Maydell wrote:
> On 30 June 2015 at 21:10, Peter Crosthwaite
> wrote:
>> On Tue, Jun 30, 2015 at 12:42 PM, Peter Maydell
>> wrote:
>>> The point here is that "do we need to do this" is exactly
>>> dependent on what we're doing with the CPU. Only if we
>>> w
On 30 June 2015 at 21:10, Peter Crosthwaite
wrote:
> On Tue, Jun 30, 2015 at 12:42 PM, Peter Maydell
> wrote:
>> The point here is that "do we need to do this" is exactly
>> dependent on what we're doing with the CPU. Only if we
>> want to put the guest into NS do we do this, and the
>> condition
On Tue, Jun 30, 2015 at 12:42 PM, Peter Maydell
wrote:
> On 30 June 2015 at 20:01, Peter Crosthwaite
> wrote:
>> On Tue, Jun 30, 2015 at 6:07 AM, Peter Maydell
>> wrote:
>>> If our builtin kernel bootloader is directly booting a kernel in
>>> the NonSecure world, then we must configure the GIC
On Tue, Jun 30, 2015 at 12:45 PM, Peter Maydell
wrote:
> On 30 June 2015 at 20:21, Peter Crosthwaite
> wrote:
>> If booting Linux, call the Linux specific init routine for all devs
>> that support it.
>>
>> Signed-off-by: Peter Crosthwaite
>>
>> ---
>> Doesn't solve the problem of conditional se
On Thu, Jun 25, 2015 at 08:39:56PM +0100, Richard W.M. Jones wrote:
> Currently if qemu is connected to a curl source (eg. web server), and
> the web server fails / times out / dies, you always see a bogus EIO
> "Input/output error".
>
> For example, choose a large file located on any local webser
On Wed, Jun 10, 2015 at 08:28:44PM -0700, Josh Durgin wrote:
> The old one still works for now, but will not work indefinitely.
>
> Signed-off-by: Josh Durgin
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 4ed8215..
On Wed, Jun 10, 2015 at 08:28:45PM -0700, Josh Durgin wrote:
> To be safe, when cache=none is used ceph settings should not be able
> to override it to turn on caching. This was previously possible with
> rbd_cache=true in the rbd device configuration or a ceph configuration
> file. Similarly, rbd
On Wed, Jun 10, 2015 at 08:28:43PM -0700, Josh Durgin wrote:
> RBDAIOCB.status was only used for cancel, which was removed in
> 7691e24dbebb46658e89b3f950fda6ec78bbb823.
>
> RBDAIOCB.sector_num was never used.
>
> RADOSCB.done and rcbid were never used.
>
> RBD_FD* are obsolete since the pipe wa
On 30 June 2015 at 20:21, Peter Crosthwaite
wrote:
> Change all the interrupt groups to 1 to enable interrupts from the NS
> world. This gives a Linux guest full control of the interrupts when
> booting directly with -kernel.
>
> Signed-off-by: Peter Crosthwaite
> ---
> Needs to be rebased on Pet
On 30 June 2015 at 20:21, Peter Crosthwaite
wrote:
> If booting Linux, call the Linux specific init routine for all devs
> that support it.
>
> Signed-off-by: Peter Crosthwaite
>
> ---
> Doesn't solve the problem of conditional setup, e.g. GIC needs to only
> do NS setup on NS boot. I think this
On 30 June 2015 at 20:01, Peter Crosthwaite
wrote:
> On Tue, Jun 30, 2015 at 6:07 AM, Peter Maydell
> wrote:
>> If our builtin kernel bootloader is directly booting a kernel in
>> the NonSecure world, then we must configure the GIC to put all
>> the IRQs into the NonSecure group. (By default all
On Mon, Jun 29, 2015 at 01:50:21PM +0530, Bharata B Rao wrote:
> Hi,
>
> Here is the v4 of the patchset that refactors pc_dimm_plug and adds
> an API to lookup NUMA node by address.
Applied to the numa tree. Thanks!
git://github.com/ehabkost/qemu.git numa
--
Eduardo
Change all the interrupt groups to 1 to enable interrupts from the NS
world. This gives a Linux guest full control of the interrupts when
booting directly with -kernel.
Signed-off-by: Peter Crosthwaite
---
Needs to be rebased on Peter's work
---
---
hw/intc/arm_gic.c | 21 +
Introduce an interface for a device with some basic linux awareness.
Allows devices to implement setup routines to emulate the device as
when Linux handoff happens. Some devices needs this to emulate
firmware or bootloader behaviour.
This allows use of -kernel -dtb -initrd style boots on platforms
Useful for iterating through an entire QOM subtree.
Signed-off-by: Peter Crosthwaite
---
include/qom/object.h | 15 +++
qom/object.c | 25 ++---
2 files changed, 37 insertions(+), 3 deletions(-)
diff --git a/include/qom/object.h b/include/qom/object.h
ind
If booting Linux, call the Linux specific init routine for all devs
that support it.
Signed-off-by: Peter Crosthwaite
---
Doesn't solve the problem of conditional setup, e.g. GIC needs to only
do NS setup on NS boot. I think this should be solved by passing the
boot_info to the GIC as opaque dat
Hi Peter and All,
QEMU continues to support booting Linux kernels directly without firmware,
but Linux is becoming more and more reliant on firmware or bootloader setup.
In cases where the firmware is very complicated, the firmware should just be
run as the guest and Linux boot is defeatured. But
On Tue, Jun 30, 2015 at 6:07 AM, Peter Maydell wrote:
> If our builtin kernel bootloader is directly booting a kernel in
> the NonSecure world, then we must configure the GIC to put all
> the IRQs into the NonSecure group. (By default all interrupts
> are configured to be Secure on reset, which me
* Wen Congyang (we...@cn.fujitsu.com) wrote:
> On 06/27/2015 03:03 AM, Dr. David Alan Gilbert wrote:
> > Ah, I hadn't realised you could do that; so do you just do:
> >
> > migrate_set_parameter colo on
> > migrate -d -b tcp:otherhhost:port
> >
> > How does the secondary know to feed that data
On Tue, Jun 30, 2015 at 11:55:59AM +0100, Peter Maydell wrote:
> On 30 June 2015 at 11:50, Zhu Guihua wrote:
> > Originally, there are some devices (such as hpet, rtc) reset before apic
> > reset.
> > When these devices reset, they would send irq to apic.
>
> In our current (arguably broken) rese
On Tue, Jun 30, 2015 at 12:24:22PM +0200, Andreas Färber wrote:
> Am 30.06.2015 um 08:31 schrieb Zhu Guihua:
> > On 06/26/2015 01:28 AM, Andreas Färber wrote:
> >> Am 25.06.2015 um 19:00 schrieb Paolo Bonzini:
> >>> On 25/06/2015 04:17, Zhu Guihua wrote:
> Add a wrapper to specify reset order
Ping
On 06/10/2015 08:28 PM, Josh Durgin wrote:
Patches 1 and 2 are simple cleanups. 3 and 4 fix the precedence of
cache options and ceph settings. The cache option precedence in
particular is important due to the potential for misconfigurations
(ceph.conf setting rbd_cache=true, qemu setting ca
Ping
On 06/23/15 19:39, Don Slutz wrote:
Changes v7 to v8:
Rebase to master
Drop patch #1 since commit 965eb2fcdfe919ecced6c34803535ad32dc1249c
fixed this.
Paolo Bonzini
Ok to pull v7 1,2,3, and 9.
Added Acked-by: Paolo Bonzini
Moved v7 #9 to v8 #3
Eric Blak
On Tue, Jun 30, 2015 at 7:10 AM, Leon Alrae wrote:
> Hi Serge,
>
> On 30/06/2015 06:02, Serge Vakulenko wrote:
>> Signed-off-by: Serge Vakulenko
>> ---
>> target-mips/op_helper.c | 7 +++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/target-mips/op_helper.c b/target-mips/op_helper.c
Syscall 370 is name_to_handle_at, and 355 is signalfd4. (Likely if
name_to_handle_at succeeds then it'll want open_by_handle_at too.)
This patch implements the signalfd syscalls, though we haven't got to reviewing
it yet.
http://patchwork.ozlabs.org/patch/478072/
It looks like systemd is coping
On 30 June 2015 at 18:38, Peter Crosthwaite
wrote:
> On Tue, Jun 30, 2015 at 4:58 AM, Johannes Schlatow
> wrote:
>> The interval interrupt is not set if the timer is in decrement mode.
>> This is because x >=0 and x < interval after leaving the while-loop.
>>
>> Signed-off-by: Johannes Schlatow
On Tue, Jun 30, 2015 at 6:51 AM, Peter Maydell wrote:
> Implement the YIELD instruction in the ARM and Thumb translators to
> actually yield control back to the top level loop rather than being
> a simple no-op. (We already do this for A64.)
>
> Signed-off-by: Peter Maydell
Reviewed-by: Peter Cr
Public bug reported:
Qemu seems to be missing syscalls 370 and 355 when running qemu usermode
arm. These are used by systemd or some similar new package. This can be
detected by creating an debian sid armhf with qemu debootstrap. When the
system is launched with "systemd-nspawn -bD sid-arm" this h
On Tue, Jun 30, 2015 at 6:51 AM, Peter Maydell wrote:
> Currently we use DISAS_WFE for both WFE and YIELD instructions.
> This is functionally correct because at the moment both of them
> are implemented as "yield this CPU back to the top level loop so
> another CPU has a chance to run". However i
On Tue, Jun 30, 2015 at 4:58 AM, Johannes Schlatow
wrote:
> The interval interrupt is not set if the timer is in decrement mode.
> This is because x >=0 and x < interval after leaving the while-loop.
>
> Signed-off-by: Johannes Schlatow
Reviewed-by: Peter Crosthwaite
Can this go via target-arm
On 30 June 2015 at 18:13, Laurent Vivier wrote:
>
>
> Le 30/06/2015 18:45, Peter Maydell a écrit :
>> On 30 June 2015 at 17:19, Laurent Vivier wrote:
>>> When guest base is disabled, RESERVED_VA is 0, and
>>> (__guest < RESERVED_VA) is always false as __guest is unsigned.
>>>
>>> With -Werror=typ
On Tuesday, June 30, 2015 06:07:40 PM Peter Maydell wrote:
> On 30 June 2015 at 18:01, Paul Moore wrote:
> > I'm starting to wonder if the 32-bit ARM build system didn't have
> > __NR_cacheflush defined in the system headers; that might explain some of
> > the behavior. Could you check your syste
Le 30/06/2015 18:45, Peter Maydell a écrit :
> On 30 June 2015 at 17:19, Laurent Vivier wrote:
>> When guest base is disabled, RESERVED_VA is 0, and
>> (__guest < RESERVED_VA) is always false as __guest is unsigned.
>>
>> With -Werror=type-limits, this triggers an error:
>>
>> include/exec/c
On 30 June 2015 at 18:01, Paul Moore wrote:
> I'm starting to wonder if the 32-bit ARM build system didn't have
> __NR_cacheflush defined in the system headers; that might explain some of the
> behavior. Could you check your system to see if it has __NR_cacheflush
> defined (try /usr/include/asm/
On Tuesday, June 30, 2015 10:39:34 AM Andrew Jones wrote:
> On Mon, Jun 29, 2015 at 04:24:55PM -0400, Paul Moore wrote:
> > Hmm, so either the kernel is screwing up with the seccomp filter for this
> > particular syscall (unlikely) or libseccomp is screwing up the filter
> > creation (more likely).
On 30 June 2015 at 17:19, Laurent Vivier wrote:
> When guest base is disabled, RESERVED_VA is 0, and
> (__guest < RESERVED_VA) is always false as __guest is unsigned.
>
> With -Werror=type-limits, this triggers an error:
>
> include/exec/cpu_ldst.h:60:31: error: comparison of unsigned expressi
Hi,
An observation I've got, and this is from the previous version; if there
is a problem with the network that carries the comparison traffic, the failure
is
difficult to dtect - you start COLO both VMs seem to be running and COLO
starts up fine, but it's only later that you realise that you a
When guest base is disabled, RESERVED_VA is 0, and
(__guest < RESERVED_VA) is always false as __guest is unsigned.
With -Werror=type-limits, this triggers an error:
include/exec/cpu_ldst.h:60:31: error: comparison of unsigned expression < 0
is always false [-Werror=type-limits]
(!RE
On Mon, Jun 29, 2015 at 06:38:13PM -0400, John Snow wrote:
> On 06/25/2015 08:12 AM, Stefan Hajnoczi wrote:
> > +/* The purpose of this is to keep txn alive until all jobs have been added
> > */
> > +void block_job_txn_begin(BlockJobTxn *txn)
> > +{
> > +block_job_txn_unref(txn);
> > +}
> > +
On Tue, 30 Jun 2015 15:56:13 +0200
Eduardo Otubo wrote:
> On Tue, Jun 30, 2015 at 11=18=21AM +0200, Igor Mammedov wrote:
> > On Tue, 30 Jun 2015 10:07:52 +0200
> > Eduardo Otubo wrote:
> >
> > > Hello all,
> > >
> > > I compiled the HEAD of the master branch and was testing memory
> > > hotunp
On 06/30/2015 11:27 AM, Stefan Hajnoczi wrote:
> On Mon, Jun 29, 2015 at 06:39:08PM -0400, John Snow wrote:
>>
>>
>> On 06/25/2015 08:12 AM, Stefan Hajnoczi wrote:
>>> Join the transaction when the backup block job is in incremental backup
>>> mode.
>>>
>>> This ensures that the sync bitmap is no
On 30 June 2015 at 16:02, Sergey Fedorov wrote:
> TLBI ALLE1IS is an operation that does invalidate TLB entries on all PEs
> in the same Inner Sharable domain, not just on the current CPU. So we
> must use tlbiall_is_write() here.
>
> Signed-off-by: Sergey Fedorov
> ---
> target-arm/helper.c | 2
1 - 100 of 231 matches
Mail list logo
