On Tue, Oct 18, 2016 at 01:37:46PM +0200, Igor Mammedov wrote:
> that's enough to make old code that depends on it
> to prevent QEMU starting with more than 255 CPUs.
>
> Signed-off-by: Igor Mammedov
Reviewed-by: Eduardo Habkost
--
Eduardo
On Tue, Oct 18, 2016 at 12:32:02PM +0100, Dr. David Alan Gilbert wrote:
> * Daniel P. Berrange (berra...@redhat.com) wrote:
> > On Wed, Oct 12, 2016 at 08:15:02PM +0100, Dr. David Alan Gilbert wrote:
> > > Hi,
> > > I had a look at a couple of readline like libraries;
> > > editline and linenoise
On Tue, Oct 18, 2016 at 12:25:17AM +0200, Tomáš Golembiovský wrote:
> Added two new options 'offset' and 'size'. This makes it possible to use
> only part of the file as a device. This can be used e.g. to limit the
> access only to single partition in a disk image or use a disk inside a
> tar archi
"Daniel P. Berrange" writes:
> On Wed, Oct 12, 2016 at 08:15:02PM +0100, Dr. David Alan Gilbert wrote:
>> Hi,
>> I had a look at a couple of readline like libraries;
>> editline and linenoise. A difficulty with using them is that
>> they both want fd's or FILE*'s; editline takes either but
>>
On Tue, 18 Oct 2016 08:39:05 -0200
Eduardo Habkost wrote:
> On Tue, Oct 18, 2016 at 11:12:04AM +0200, Igor Mammedov wrote:
> > On Mon, 17 Oct 2016 19:44:52 -0200
> > Eduardo Habkost wrote:
> >
> > > On Thu, Oct 13, 2016 at 11:52:39AM +0200, Igor Mammedov wrote:
> > > [...]
> > > > @@ -236,7
Switch from normal migration loadvm process into COLO checkpoint process if
COLO mode is enabled.
We add three new members to struct MigrationIncomingState,
'have_colo_incoming_thread' and 'colo_incoming_thread' record the COLO
related thread for secondary VM, 'migration_incoming_co' records the
o
We leave users to choose whatever heartbeat solution they want,
if the heartbeat is lost, or other errors they detect, they can use
experimental command 'x_colo_lost_heartbeat' to tell COLO to do failover,
COLO will do operations accordingly.
For example, if the command is sent to the PVM, the Pri
If users require SVM to takeover work, COLO incoming thread should
exit from loop while failover BH helps backing to migration incoming
coroutine.
Signed-off-by: zhanghailiang
Signed-off-by: Li Zhijian
Reviewed-by: Dr. David Alan Gilbert
---
v20:
- Rebase to master
v12:
- Improve error message
We need communications protocol of user-defined to control
the checkpointing process.
The new checkpointing request is started by Primary VM,
and the interactive process like below:
Checkpoint synchronizing points:
Primary Secondary
We can determine whether or not VM in destination should go into COLO mode
by referring to the info that was migrated.
We skip this section if COLO is not enabled (i.e.
migrate_set_capability colo off), so that, It doesn't break compatibility
with migration no matter whether users configure the --
We add helper function colo_supported() to indicate whether
colo is supported or not, with which we use to control whether or not
showing 'x-colo' string to users, they can use qmp command
'query-migrate-capabilities' or hmp command 'info migrate_capabilities'
to learn if colo is supported.
The de
When handling failover, COLO processes differently according to
the different stage of failover process, here we introduce a global
atomic variable to record the status of failover.
We add four failover status to indicate the different stage of failover process.
You should use the helpers to get a
On Tue, Oct 18, 2016 at 02:08:14PM +0200, Markus Armbruster wrote:
> "Daniel P. Berrange" writes:
>
> > On Wed, Oct 12, 2016 at 08:15:02PM +0100, Dr. David Alan Gilbert wrote:
> >> Hi,
> >> I had a look at a couple of readline like libraries;
> >> editline and linenoise. A difficulty with usin
Do checkpoint periodically, the default interval is 200ms.
Signed-off-by: zhanghailiang
Signed-off-by: Li Zhijian
Reviewed-by: Dr. David Alan Gilbert
---
v12:
- Add Reviewed-by tag
v11:
- Fix wrong sleep time for checkpoint period. (Dave's comment)
---
migration/colo.c | 12
1 fil
We should not destroy the state of SVM (Secondary VM) until we receive
the complete data of PVM's state, in case the primary fails in the process
of sending the state, so we cache the VM's state in secondary side before
load it into SVM.
Besides, we should call qemu_system_reset() before load VM s
configure --enable-colo/--disable-colo to switch COLO
support on/off.
COLO feature is enabled by default.
Signed-off-by: zhanghailiang
Signed-off-by: Li Zhijian
Signed-off-by: Gonglei
Reviewed-by: Dr. David Alan Gilbert
---
v19:
- fix colo_supported() to return true
v11:
- Turn COLO on in defa
Guest will enter this state when paused to save/restore VM state
under COLO checkpoint.
Cc: Eric Blake
Cc: Markus Armbruster
Signed-off-by: zhanghailiang
Signed-off-by: Li Zhijian
Signed-off-by: Gonglei
Reviewed-by: Dr. David Alan Gilbert
Reviewed-by: Eric Blake
---
qapi-schema.json | 5 ++
Add a new migration state: MIGRATION_STATUS_COLO. Migration source side
enters this state after the first live migration successfully finished
if COLO is enabled by command 'migrate_set_capability x-colo on'.
We reuse migration thread, so the process of checkpointing will be handled
in migration t
This is the 21th version of COLO frame series.
Rebase to the latest master.
Cc: Juan Quintela
Cc: Amit Shah
Cc: Hai Huang
Cc: Weidong Han
Cc: Dong eddie
Cc: Stefan Hajnoczi
Cc: Jason Wang
Cc: Dr. David Alan Gilbert (git)
zhanghailiang (17):
migration: Introduce capability 'x-colo' to
Add checkpoint-delay parameter for migrate-set-parameters, so that
we can control the checkpoint frequency when COLO is in periodic mode.
Cc: Luiz Capitulino
Cc: Eric Blake
Cc: Markus Armbruster
Signed-off-by: zhanghailiang
Signed-off-by: Li Zhijian
Reviewed-by: Dr. David Alan Gilbert
---
v2
For primary side, if COLO gets failover request from users.
To be exact, gets 'x_colo_lost_heartbeat' command.
COLO thread will exit the loop while the failover BH does the
cleanup work and resumes VM.
Signed-off-by: zhanghailiang
Signed-off-by: Li Zhijian
Reviewed-by: Dr. David Alan Gilbert
--
This new communication path will be used for returning messages
from Secondary side to Primary side.
Signed-off-by: zhanghailiang
Signed-off-by: Li Zhijian
Reviewed-by: Dr. David Alan Gilbert
---
v13:
- Remove useless error report
v12:
- Add Reviewed-by tag
v11:
- Rebase master to use qemu_file
Version 2.0 of the semihosting specification introduces new trap
instructions for AArch32: HLT 0xF000 for A32 and HLT 0x3C for T32.
Implement these (in the same way we implement the existing HLT
semihosting trap for A64).
The old traps via SVC and BKPT are unaffected.
Signed-off-by: Peter Maydell
Introduce the design of COLO, and how to test it.
Signed-off-by: zhanghailiang
---
v21:
- Fix some minor typos and grammar from Eric
---
docs/COLO-FT.txt | 189 +++
1 file changed, 189 insertions(+)
create mode 100644 docs/COLO-FT.txt
diff --
VM checkpointing is to synchronize the state of PVM to SVM, just
like migration does, we re-use save helpers to achieve migrating
PVM's state to Secondary side.
COLO need to cache the data of VM's state in the secondary side before
synchronize it to SVM. COLO need the size of the data to determine
On Tue, Oct 18, 2016 at 4:03 PM, Anand J wrote:
> Added script to check duplicate #include entries. This check will scan
> and print the files in which duplicate #include entries are present.
>
> Script might output false positive entries as well. Such entries should
> not be removed. So if it fi
On Tue, Oct 18, 2016 at 4:03 PM, Anand J wrote:
> Some files contain multiple #includes of the same header file.
> Removed most of those unnecessary duplicate entries using
> scripts/clean-includes.
>
> Signed-off-by: Anand J
> ---
> accel.c | 1 -
> cputlb.c
On Tue, 18 Oct 2016 08:56:28 -0200
Eduardo Habkost wrote:
> On Thu, Oct 13, 2016 at 11:52:40AM +0200, Igor Mammedov wrote:
> > ACPI ID is 32 bit wide on CPUs with x2APIC support.
> > Extend 'id' property to support it.
> >
> > Signed-off-by: Igor Mammedov
> > ---
> > v3:
> >keep original be
On 10/18/2016 12:02 AM, Alex Williamson wrote:
> On Fri, 14 Oct 2016 15:19:01 -0700
> Neo Jia wrote:
>
>> On Fri, Oct 14, 2016 at 10:51:24AM -0600, Alex Williamson wrote:
>>> On Fri, 14 Oct 2016 09:35:45 -0700
>>> Neo Jia wrote:
>>>
On Fri, Oct 14, 2016 at 08:46:01AM -0600, Alex Williams
* Daniel P. Berrange (berra...@redhat.com) wrote:
> On Tue, Oct 18, 2016 at 02:08:14PM +0200, Markus Armbruster wrote:
> > "Daniel P. Berrange" writes:
> >
> > > On Wed, Oct 12, 2016 at 08:15:02PM +0100, Dr. David Alan Gilbert wrote:
> > >> Hi,
> > >> I had a look at a couple of readline like l
On 18/10/2016 12:52, David Gibson wrote:
> The 'addr' parameter to qvirtio_config_read*() doesn't have a consistent
> meaning: when using the virtio-pci versions, it's a full PCI space address,
> but for virtio-mmio, it's an offset from the device's base mmio address.
>
> This means that the cal
On Tue, 18 Oct 2016 09:27:37 -0200
Eduardo Habkost wrote:
> On Fri, Oct 14, 2016 at 01:25:35PM +0200, Igor Mammedov wrote:
> > it would prevent starting guest with incorrect configs
> > where interrupts couldn't be delivered to CPUs with
> > APIC IDs > 255.
> >
> > Signed-off-by: Igor Mammedov
On Thu, Oct 13, 2016 at 11:52:35AM +0200, Igor Mammedov wrote:
> Signed-off-by: Igor Mammedov
Reviewed-by: Eduardo Habkost
But I have a few questions below that are not directly related to
this patch:
> ---
> include/hw/acpi/acpi-defs.h | 18 +++
> hw/i386/acpi-build.c| 78
>
On Tue, Oct 18, 2016 at 4:11 PM, Peter Lieven wrote:
> Am 17.10.2016 um 21:34 schrieb Ashijeet Acharya:
>>
>> On Tue, Oct 18, 2016 at 12:59 AM, Eric Blake wrote:
>>>
>>> On 10/17/2016 01:00 PM, Ashijeet Acharya wrote:
>>>
One more relatively easy question though, will we include @port as an
On Tue, Oct 18, 2016 at 02:44:55PM +0200, Igor Mammedov wrote:
> On Tue, 18 Oct 2016 09:27:37 -0200
> Eduardo Habkost wrote:
>
> > On Fri, Oct 14, 2016 at 01:25:35PM +0200, Igor Mammedov wrote:
> > > it would prevent starting guest with incorrect configs
> > > where interrupts couldn't be deliver
On Tue, Oct 18, 2016 at 02:36:10PM +0200, Igor Mammedov wrote:
> On Tue, 18 Oct 2016 08:56:28 -0200
> Eduardo Habkost wrote:
>
> > On Thu, Oct 13, 2016 at 11:52:40AM +0200, Igor Mammedov wrote:
> > > ACPI ID is 32 bit wide on CPUs with x2APIC support.
> > > Extend 'id' property to support it.
> >
On Mon, Oct 17, 2016 at 05:20:22PM -0200, Eduardo Habkost wrote:
> On Sat, Oct 15, 2016 at 12:52:48AM +0200, Laurent Vivier wrote:
> > Modify all CPUs to call it from XXX_cpu_realizefn() function.
> >
> > Remove all the cannot_destroy_with_object_finalize_yet as
> > unsafe references have been mov
On Tue, 18 Oct 2016 10:47:02 -0200
Eduardo Habkost wrote:
> On Thu, Oct 13, 2016 at 11:52:35AM +0200, Igor Mammedov wrote:
> > Signed-off-by: Igor Mammedov
>
> Reviewed-by: Eduardo Habkost
>
> But I have a few questions below that are not directly related to
> this patch:
>
> > ---
> > in
Am 18.10.2016 um 00:25 hat Tomáš Golembiovský geschrieben:
> Added two new options 'offset' and 'size'. This makes it possible to use
> only part of the file as a device. This can be used e.g. to limit the
> access only to single partition in a disk image or use a disk inside a
> tar archive (like
Am 18.10.2016 um 14:46 hat Ashijeet Acharya geschrieben:
> On Tue, Oct 18, 2016 at 4:11 PM, Peter Lieven wrote:
> > Am 17.10.2016 um 21:34 schrieb Ashijeet Acharya:
> >>
> >> On Tue, Oct 18, 2016 at 12:59 AM, Eric Blake wrote:
> >>>
> >>> On 10/17/2016 01:00 PM, Ashijeet Acharya wrote:
> >>>
> >>
On Thu, Oct 13, 2016 at 11:52:36AM +0200, Igor Mammedov wrote
[...]
> @@ -2441,18 +2440,33 @@ build_srat(GArray *table_data, BIOSLinker *linker,
> MachineState *machine)
>
> for (i = 0; i < apic_ids->len; i++) {
> int j = numa_get_node_for_cpu(i);
> -int apic_id = apic_ids-
On Tue, Oct 18, 2016 at 10:47:02AM -0200, Eduardo Habkost wrote:
> On Thu, Oct 13, 2016 at 11:52:35AM +0200, Igor Mammedov wrote:
> > Signed-off-by: Igor Mammedov
>
> Reviewed-by: Eduardo Habkost
Reviewed-by withdrawn. See below:
[...]
> > diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build
On Tue, Oct 18, 2016 at 6:34 PM, Kevin Wolf wrote:
> Am 18.10.2016 um 14:46 hat Ashijeet Acharya geschrieben:
>> On Tue, Oct 18, 2016 at 4:11 PM, Peter Lieven wrote:
>> > Am 17.10.2016 um 21:34 schrieb Ashijeet Acharya:
>> >>
>> >> On Tue, Oct 18, 2016 at 12:59 AM, Eric Blake wrote:
>> >>>
>> >>
From: Aleksandar Markovic
This patch implements Qemu user mode adjtimex() syscall support.
Syscall adjtimex() reads and optionally sets parameters for a clock
adjustment algorithm used in network synchonization or similar scenarios.
Its declaration is:
int adjtimex(struct timex *buf);
The cor
iku.voipio/qemu.git tags/pull-linux-user-20161018
for you to fetch changes up to cee1d8afec98e0e686c894b06982e08b8bf242ba:
linux-user: disable unicore32 linux-user build (2016-10-18 11:57:57 +0300)
Linux-user changes, mostly bu
From: Aleksandar Markovic
If syscalls msgrcv() and msgsnd() fail, they return E2BIG, EACCES,
EAGAIN, EFAULT, EIDRM, EINTR, EINVAL, ENOMEM, or ENOMSG.
By examining negative scenarios of these syscalls for Mips, it was
established that ENOMSG does not have the same value accross all
platforms, but
From: Aleksandar Markovic
There are currently several problems related to syslog() support.
For example, if the second argument "bufp" of target syslog() syscall
is NULL, the current implementation always returns error code EFAULT.
However, NULL is a perfectly valid value for the second argument
On Tue, Oct 18, 2016 at 03:00:07PM +0200, Andrew Jones wrote:
> On Mon, Oct 17, 2016 at 05:20:22PM -0200, Eduardo Habkost wrote:
> > On Sat, Oct 15, 2016 at 12:52:48AM +0200, Laurent Vivier wrote:
> > > Modify all CPUs to call it from XXX_cpu_realizefn() function.
> > >
> > > Remove all the cannot
From: Aleksandar Markovic
Since not all Linux host platforms support socketcall() (most notably
Intel), do_socketcall() function in Qemu's syscalls.c is implemented to
mirror the corespondant implementation of socketcall() in Linux kernel,
and to utilise individual socket operations that are supp
From: Aleksandar Markovic
Conversion of file creation flags (O_CREAT, ...) from target to host
was missing.
Also, this patch implements better error handling.
Signed-off-by: Aleksandar Markovic
Signed-off-by: Riku Voipio
---
linux-user/syscall.c | 16 +---
1 file changed, 9 inser
From: Peter Maydell
In commit 40df8c0c0722 support was added for target-specific
handling of SHMLBA. Unfortunately the sparc64-specific part
of the change got lost somewhere between the patch being
posted to the list and going into master:
http://patchwork.ozlabs.org/patch/646980/
http://patchw
From: Aleksandar Markovic
This patch implements Qemu user mode syncfs() syscall support. Syscall
syncfs() syncs the filesystem containing file determined by the open
file descriptor passed as the argument to syncfs().
The implementation consists of a straightforward invocation of host's
syncfs()
From: Aleksandar Markovic
This patch implements Qemu user mode ustat() syscall support.
Syscall ustat() returns information about a mounted filesystem.
Its declaration is:
int ustat(dev_t dev, struct ustat *ubuf);
Its Linux kernel implementation is at fs/compat.c, line 334.
The Qemu implemen
From: Aleksandar Markovic
There is a duplicate item in strace.list. It is benign, but it
shouldn't be there, since it may lead to confusion and even bugs
in the future. It is the only duplicate in strace.list. This
patch removes it.
Signed-off-by: Aleksandar Markovic
Signed-off-by: Riku Voipio
From: Peter Maydell
The sigevent structure includes a union with some fields which
are pointers. For the QEMU target_sigevent structure we must
represent these as abi_ulongs, not host function pointers.
This error was causing the compiler to believe it should 8-align
the _sigev_un union on a 64-
From: Aleksandar Markovic
This patch implements Qemu user mode clock_adjtime() syscall support.
The implementation is based on invocation of host's clock_adjtime().
Signed-off-by: Aleksandar Rikalo
Signed-off-by: Aleksandar Markovic
Signed-off-by: Riku Voipio
---
configure | 18
From: Felix Janda
This commit essentially reverts commit
3af72a4d98dca033492102603734cbc63cd2694a, which has replaced
five-argument calls to mremap() by direct mremap syscalls for
compatibility with glibc older than version 2.4.
The direct syscall was buggy for 64bit targets on 32bit hosts
becau
From: Peter Maydell
The epoll event array which epoll_wait() allocates has a size
determined by the guest which could potentially be quite large.
Use g_try_new() rather than alloca() so that we can fail more
cleanly if the guest hands us an oversize value. (ENOMEM is
not a documented return value
From: Laurent Vivier
Signed-off-by: Laurent Vivier
Reviewed-by: Peter Maydell
Signed-off-by: Riku Voipio
---
linux-user/syscall.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 3396d4b..e005401 100644
--- a/linux-user/syscall.
From: Aleksandar Markovic
linux-user/mips64/termbits.h and linux-user/mips/termbits.h
originate from the same files in Linux kernel. There is no plan
to split original headers in Linux kernel into Mips32 and Mips64
versions any time soon. Therefore, it is better not to have
separate Mips32 and Mi
From: Aleksandar Markovic
Array mips_syscall_args[] determines number of arguments for each
syscall on Mips32. It wasn't updated with newer syscalls. Also,
preadv and pwritev have 5 arguments, not 6.
Signed-off-by: Aleksandar Markovic
Signed-off-by: Riku Voipio
---
linux-user/main.c | 24
From: Aleksandar Markovic
By looking at the file arch/mips/kernel/scall32-o32.S in Linux
kernel, it can be deduced that, for Mips32 platform, syscall
corresponding to number _NR_fadvise64 as defined in kernel file
arch/mips/include/uapi/asm/unistd.h translates to kernel function
sys_fadvise64_64,
From: Laurent Vivier
Used by fedora21 on ppc64 in the network initialization
Signed-off-by: Laurent Vivier
Signed-off-by: Riku Voipio
---
linux-user/syscall.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index e005401..bbdf316 100644
--- a/li
From: Dejan Jovicevic
This system call performs the same task as the readv() system call,
with the exception of having the fourth argument, offset, which
specifes the file offset at which the input operation is to be performed.
Because of this, the preadv() implementation is based on the readv()
* Daniel P. Berrange (berra...@redhat.com) wrote:
> On Tue, Oct 18, 2016 at 12:32:02PM +0100, Dr. David Alan Gilbert wrote:
> > * Daniel P. Berrange (berra...@redhat.com) wrote:
> > > On Wed, Oct 12, 2016 at 08:15:02PM +0100, Dr. David Alan Gilbert wrote:
> > > > Hi,
> > > > I had a look at a cou
From: Aleksandar Markovic
Update linux-user/mips/termbits.h with ioctl definitions from kernel
file arch/mips/include/uapi/asm/ioctls.h.
Signed-off-by: Aleksandar Markovic
Signed-off-by: Riku Voipio
---
linux-user/mips/termbits.h | 12
1 file changed, 12 insertions(+)
diff --git
From: Riku Voipio
In order to cleanup linux-user, we need support for most relatively
modern syscalls. unicore32 lacks support for syscalls like
epoll_pwait, preventing cleaning up the CONFIG_EPOLL mess.
This patch can be reverted when unicore32 starts either supporting
the syscalls as defined i
* Halil Pasic (pa...@linux.vnet.ibm.com) wrote:
> The handling of VMStateField.start is currently quite broken if
> VMS_ALLOC is present (that is for VMSTATE_VBUFFER_ALLOC_UINT32) but
> fortunately also quite underutilized -- nobody is using .start != 0.
>
> Let's prove with this patch that it's r
From: Dejan Jovicevic
This system call performs the same task as the writev() system call,
with the exception of having the fourth argument, offset, which
specifes the file offset at which the input operation is to be performed.
Because of this, the pwritev() implementation is based on the writev
On Thu, Oct 13, 2016 at 11:52:37AM +0200, Igor Mammedov wrote:
> Signed-off-by: Igor Mammedov
> ---
> hw/acpi/cpu.c | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/hw/acpi/cpu.c b/hw/acpi/cpu.c
> index 902f5c9..5ac89fe 100644
> --- a/hw/acpi/cpu.c
> +++ b/hw/acpi/cpu.c
> @@ -531,6
On 10/18/2016 02:29 AM, Christian Borntraeger wrote:
> For automated testing purposes it can be helpful to exit qemu
> (poweroff) when the guest panics. Make this the default unless
> -no-shutdown is specified.
>
> For internal-errors like errors from KVM_RUN the behaviour is
> not changed, in oth
On Tue, 18 Oct 2016 21:52:06 +1100
David Gibson wrote:
> The 'addr' parameter to qvirtio_config_read*() doesn't have a consistent
> meaning: when using the virtio-pci versions, it's a full PCI space address,
> but for virtio-mmio, it's an offset from the device's base mmio address.
>
> This mean
On 18/10/2016 12:52, David Gibson wrote:
> The PCI IO space (aka PIO, aka legacy IO) and PCI memory space (aka MMIO)
> are distinct address spaces by the PCI spec (although parts of one might be
> aliased to parts of the other in some cases).
>
> However, qpci_io_read*() and qpci_io_write*() can
Am 18.10.2016 um 15:14 hat Ashijeet Acharya geschrieben:
> On Tue, Oct 18, 2016 at 6:34 PM, Kevin Wolf wrote:
> > Am 18.10.2016 um 14:46 hat Ashijeet Acharya geschrieben:
> >> On Tue, Oct 18, 2016 at 4:11 PM, Peter Lieven wrote:
> >> > Am 17.10.2016 um 21:34 schrieb Ashijeet Acharya:
> >> >>
> >>
2016-10-17 15:20-0200, Marcelo Tosatti:
> On Mon, Oct 17, 2016 at 04:50:09PM +0200, Radim Krčmář wrote:
>> 2016-10-17 07:47-0200, Marcelo Tosatti:
>> > On Fri, Oct 14, 2016 at 06:20:31PM -0300, Eduardo Habkost wrote:
>> >> I have been wondering: should we allow live migration with the
>> >> invtsc
On 18/10/2016 11:54, Dr. David Alan Gilbert wrote:
> I've not quite figured it out but we're linked against the stubs/ monitor
> code rather than the real monitor code; and the stubs monitor_vprintf discards
> and the stubs monitor_cur_is_qmp() always returns false, so to silence things
> we just
On 10/18/2016 04:24 AM, Marc-André Lureau wrote:
> Use the libvhost-user library.
>
> This ended up being a rather large patch that cannot be easily splitted,
s/splitted/split/ (One of those weird English verbs that has the same
spelling in multiple tenses)
> due to massive code move and API cha
On Tue, Oct 18, 2016 at 02:25:25PM +0100, Dr. David Alan Gilbert wrote:
> * Daniel P. Berrange (berra...@redhat.com) wrote:
> > On Tue, Oct 18, 2016 at 12:32:02PM +0100, Dr. David Alan Gilbert wrote:
> > > * Daniel P. Berrange (berra...@redhat.com) wrote:
> > > > On Wed, Oct 12, 2016 at 08:15:02PM
On Tue, 18 Oct 2016 11:07:21 -0200
Eduardo Habkost wrote:
> On Thu, Oct 13, 2016 at 11:52:36AM +0200, Igor Mammedov wrote
> [...]
> > @@ -2441,18 +2440,33 @@ build_srat(GArray *table_data, BIOSLinker *linker,
> > MachineState *machine)
> >
> > for (i = 0; i < apic_ids->len; i++) {
> >
2016-10-18 15:36+0200, Radim Krčmář:
> 2016-10-17 18:24+0200, Paolo Bonzini:
>> We should also blacklist the TSC deadline timer when invtsc is not
>> available.
>
> True.
>
> I was thinking that with Wanpeng's VMX preemption patches, we might not
> need the TSC nor paravirtual deadline timer, the
On Tue, 18 Oct 2016 11:34:55 -0200
Eduardo Habkost wrote:
> On Thu, Oct 13, 2016 at 11:52:37AM +0200, Igor Mammedov wrote:
> > Signed-off-by: Igor Mammedov
> > ---
> > hw/acpi/cpu.c | 5 +
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/hw/acpi/cpu.c b/hw/acpi/cpu.c
> > index 902f
Michael S. Tsirkin writes:
> On Tue, Jun 28, 2016 at 11:01:29AM +0200, Peter Lieven wrote:
>> Signed-off-by: Peter Lieven
>> ---
>> include/qemu/mmap-alloc.h | 6 ++
>> util/mmap-alloc.c | 17 +
>> 2 files changed, 23 insertions(+)
>>
>> diff --git a/include/qemu/m
2016-10-17 18:24+0200, Paolo Bonzini:
> On 17/10/2016 16:50, Radim Krčmář wrote:
>> 2016-10-17 07:47-0200, Marcelo Tosatti:
>>> On Fri, Oct 14, 2016 at 06:20:31PM -0300, Eduardo Habkost wrote:
I have been wondering: should we allow live migration with the
invtsc flag enabled, if TSC scali
On 18/10/2016 01:58, Marcelo Tosatti wrote:
> > We should also blacklist the TSC deadline timer when invtsc is not
> > available.
>
> Actually, a nicer fix would be to check the different
> frequencies and scale the deadline relative to the difference.
You cannot know what exactly the guest wa
2016-10-17 21:58-0200, Marcelo Tosatti:
> On Mon, Oct 17, 2016 at 07:11:01PM -0200, Eduardo Habkost wrote:
>> On Mon, Oct 17, 2016 at 06:24:38PM +0200, Paolo Bonzini wrote:
>> > On 17/10/2016 16:50, Radim Krčmář wrote:
>> > > 2016-10-17 07:47-0200, Marcelo Tosatti:
>> [...]
>> > >> since Linux gues
On Tue, 18 Oct 2016 10:59:17 -0200
Eduardo Habkost wrote:
> On Tue, Oct 18, 2016 at 02:36:10PM +0200, Igor Mammedov wrote:
> > On Tue, 18 Oct 2016 08:56:28 -0200
> > Eduardo Habkost wrote:
> >
> > > On Thu, Oct 13, 2016 at 11:52:40AM +0200, Igor Mammedov wrote:
> > > > ACPI ID is 32 bit wid
On Tue, 18 Oct 2016 11:05:47 -0200
Eduardo Habkost wrote:
> On Tue, Oct 18, 2016 at 10:47:02AM -0200, Eduardo Habkost wrote:
> > On Thu, Oct 13, 2016 at 11:52:35AM +0200, Igor Mammedov wrote:
> > > Signed-off-by: Igor Mammedov
> >
> > Reviewed-by: Eduardo Habkost
>
> Reviewed-by withdra
On Mon, 10/17 22:56, Auger Eric wrote:
> > make[1]: *** No rule to make target `../hw/core/platform-bus-stub.o',
> > needed by `qemu-system-x86_64'. Stop.
> I can't figure out why this rule is missing?
>
> I compiled on x86 and aarch64 with
> ./configure --target-list="x86_64-softmmu" --enable-w
* Daniel P. Berrange (berra...@redhat.com) wrote:
> On Tue, Oct 18, 2016 at 02:25:25PM +0100, Dr. David Alan Gilbert wrote:
> > * Daniel P. Berrange (berra...@redhat.com) wrote:
> > > On Tue, Oct 18, 2016 at 12:32:02PM +0100, Dr. David Alan Gilbert wrote:
> > > > * Daniel P. Berrange (berra...@redh
On Thu, Oct 13, 2016 at 11:52:38AM +0200, Igor Mammedov wrote:
> Switch to modern cpu hotplug at machine startup time if
> a cpu present at boot has apic-id in range unsupported
> by legacy cpu hotplug interface (i.e. > 254), to avoid
> killing QEMU from legacy cpu hotplug code with error:
>"ac
On Tue, Oct 18, 2016 at 03:46:05PM +0200, Igor Mammedov wrote:
> On Tue, 18 Oct 2016 11:34:55 -0200
> Eduardo Habkost wrote:
>
> > On Thu, Oct 13, 2016 at 11:52:37AM +0200, Igor Mammedov wrote:
> > > Signed-off-by: Igor Mammedov
> > > ---
> > > hw/acpi/cpu.c | 5 +
> > > 1 file changed, 5 i
> On 17 Oct 2016, at 01:35 AM, Kevin Wolf wrote:
>
> The e1000e emulation zeroes out any used rx descriptor and then writes a
> completely newly constructed value there. By doing this, it doesn't only
> update the write-back area of the descriptors (as it's supposed to do),
> but it also clears t
Hi Fam,
On 18/10/2016 15:34, Fam Zheng wrote:
> On Mon, 10/17 22:56, Auger Eric wrote:
>>> make[1]: *** No rule to make target `../hw/core/platform-bus-stub.o',
>>> needed by `qemu-system-x86_64'. Stop.
>> I can't figure out why this rule is missing?
>>
>> I compiled on x86 and aarch64 with
>> .
On Tue, Oct 18, 2016 at 12:20:09AM +0200, Andreas Färber wrote:
> Am 17.10.2016 um 23:04 schrieb Eduardo Habkost:
> > On Tue, Oct 11, 2016 at 05:41:13PM -0300, Eduardo Habkost wrote:
> >> Eduardo Habkost (6):
> >> qdev: qdev_class_set_props() function
>
> s/qdev_/device_/?
I used qdev_ because
On Tue, Oct 18, 2016 at 04:01:56PM +0200, Igor Mammedov wrote:
> On Tue, 18 Oct 2016 10:59:17 -0200
> Eduardo Habkost wrote:
>
> > On Tue, Oct 18, 2016 at 02:36:10PM +0200, Igor Mammedov wrote:
> > > On Tue, 18 Oct 2016 08:56:28 -0200
> > > Eduardo Habkost wrote:
> > >
> > > > On Thu, Oct 13,
On 10/18/2016 03:27 PM, Dr. David Alan Gilbert wrote:
> * Halil Pasic (pa...@linux.vnet.ibm.com) wrote:
>> > The handling of VMStateField.start is currently quite broken if
>> > VMS_ALLOC is present (that is for VMSTATE_VBUFFER_ALLOC_UINT32) but
>> > fortunately also quite underutilized -- nobody
> On 18 Oct 2016, at 10:24, Marc-André Lureau
> wrote:
>
> Add a library to help implementing vhost-user backend (or slave).
>
> Dealing with vhost-user as an application developper isn't so easy: you
s/developper/developer/
Felipe
> have all the trouble with any protocol: validation, unix
On 10/18/2016 08:33 AM, Kevin Wolf wrote:
>> I have successfully converted NFS block driver to use this set of
>> runtime opts which I think is the required condition to add
>> blockdev-add compatibility later. Also, since I do not have 'port' as
>> a runtime option, I can directly add blockdev-ad
* Halil Pasic (pa...@linux.vnet.ibm.com) wrote:
>
>
> On 10/18/2016 03:27 PM, Dr. David Alan Gilbert wrote:
> > * Halil Pasic (pa...@linux.vnet.ibm.com) wrote:
> >> > The handling of VMStateField.start is currently quite broken if
> >> > VMS_ALLOC is present (that is for VMSTATE_VBUFFER_ALLOC_UIN
On Tue, Oct 18, 2016 at 12:07:30AM +0200, Andreas Färber wrote:
> Am 17.10.2016 um 23:02 schrieb Eduardo Habkost:
> > Ping?
> >
> > Markus, do you want to merge this through your tree?
> >
> > On Tue, Oct 11, 2016 at 09:37:45AM -0300, Eduardo Habkost wrote:
> >> A few fixes on check-qom-proplist
101 - 200 of 396 matches
Mail list logo
