On 11/03/2017 06:55 PM, Tetsuo Handa wrote:
I'm commenting without understanding the logic.
Wei Wang wrote:
+
+bool xb_preload(gfp_t gfp);
+
Want __must_check annotation, for __radix_tree_preload() is marked
with __must_check annotation. By error failing to check result of
xb_preload() will le
On 11/04/2017 07:28 PM, Tetsuo Handa wrote:
Wei Wang wrote:
On 11/03/2017 07:25 PM, Tetsuo Handa wrote:
If this is inside vb->balloon_lock mutex (isn't this?), xb_set_page() must not
use __GFP_DIRECT_RECLAIM allocation, for leak_balloon_sg_oom() will be blocked
on vb->balloon_lock mutex.
OK. Si
On Mon, 30 Oct 2017 19:58:15 +0100
Halil Pasic wrote:
> On 10/30/2017 06:38 PM, Pierre Morel wrote:
> > On 30/10/2017 18:08, Christian Borntraeger wrote:
> >>
> >> On 10/30/2017 05:59 PM, Cornelia Huck wrote:
> >>> On Mon, 30 Oct 2017 14:48:23 +0100
> >>> Christian Borntraeger wrote:
> >>>
>
On 11/06/2017 09:52 AM, Cornelia Huck wrote:
> On Mon, 30 Oct 2017 19:58:15 +0100
> Halil Pasic wrote:
>
>> On 10/30/2017 06:38 PM, Pierre Morel wrote:
>>> On 30/10/2017 18:08, Christian Borntraeger wrote:
On 10/30/2017 05:59 PM, Cornelia Huck wrote:
> On Mon, 30 Oct 2017 14:4
On Fri, Nov 3, 2017 at 4:11 PM, Michael S. Tsirkin wrote:
> On Fri, Nov 03, 2017 at 09:23:07AM +0100, Ladi Prosek wrote:
>> On Fri, Nov 3, 2017 at 8:20 AM, Gerd Hoffmann wrote:
>> >
>> >> > > Signed-off-by: Ladi Prosek
>> >> >
>> >> > I wonder whether it's a problem that legacy devices ignore
>>
unsubscribe qemu-devel
Hi all,
qemu core dump, max_core="unlimited", dump_guest_core=0, kill -11 pid
to generate a qemu core file, the Rss of qemu itself is ~40MB, the
core file is almost ~40MB in centos 6.x, but ~400MB in cents 7.x, any
idea?
Regards,
Wanpeng Li
Hi,
> > So in my humble opinion the right thing for people to do is simply
> > to
> > avoid legacy devices. Is something preventing that?
>
> The same reasons why the concept of transitional devices exists at
> all?
We discussing future driver versions running on future qemu versions,
so we sh
Testing now with qemu 2.10.1
Will need 1 day to see drift or not
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1086782
Title:
HPET time drift windows 7 64bits guest
Status in QEMU:
Incomplete
B
On Fri, Oct 13, 2017 at 09:26:17AM -0500, Eric Blake wrote:
[adding Markus, and block list]
On 10/13/2017 09:16 AM, Alberto Garcia wrote:
On Mon 02 Oct 2017 04:33:28 PM CEST, Pradeep Jagadeesh wrote:
This patch factors out code to use the ThrottleLimits
structure.
{ 'struct': 'BlockIOThrot
Hello,
i've upgraded some servers from kernel 4.4 to 4.12 - both running Qemu
2.9.1.
If i migrate a VM from a host running kernel 4.4 to a host running 4.12
i get:
kvm: virtio-net: saved image requires TUN_F_UFO support
kvm: Failed to load virtio-net-device:tmp
kvm: Failed to load virtio-net:vir
On 06/11/2017 10:38, Stefan Priebe - Profihost AG wrote:
> Hello,
>
> i've upgraded some servers from kernel 4.4 to 4.12 - both running Qemu
> 2.9.1.
>
> If i migrate a VM from a host running kernel 4.4 to a host running 4.12
> i get:
>
> kvm: virtio-net: saved image requires TUN_F_UFO support
>
On 06/11/2017 10:11, Wanpeng Li wrote:
> Hi all,
>
> qemu core dump, max_core="unlimited", dump_guest_core=0, kill -11 pid
> to generate a qemu core file, the Rss of qemu itself is ~40MB, the
> core file is almost ~40MB in centos 6.x, but ~400MB in cents 7.x, any
> idea?
My suspicion is the memor
This is RFC v3 of Monitor Out-Of-Band series. It's getting longer and
changes happens between versions, so I decided to re-write the cover
letter.
This series was born from this one:
https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg04310.html
The idea comes from Markus Armbruster and
This is not a problem if we are only having one single loop thread like
before. However, after per-monitor thread is introduced, this is not
true any more, and the race can happen.
The race can be triggered with "make check -j8" sometimes:
qemu-system-x86_64: /root/git/qemu/chardev/char-io.c:9
We can simplify object_property_get_str() using the new
qobject_get_try_str().
Signed-off-by: Peter Xu
---
qom/object.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/qom/object.c b/qom/object.c
index c58c52d518..9cbeb51f0b 100644
--- a/qom/object.c
+++ b/qom/object
The only difference from qstring_get_str() is that it allows the qstring
to be NULL. If so, NULL is returned.
CC: Eric Blake
CC: Markus Armbruster
Signed-off-by: Peter Xu
---
include/qapi/qmp/qstring.h | 1 +
qobject/qstring.c | 10 ++
2 files changed, 11 insertions(+)
diff
On 06/11/2017 10:48, Stefan Priebe - Profihost AG wrote:
> Hi Paolo,
>
> Am 06.11.2017 um 10:40 schrieb Paolo Bonzini:
>> On 06/11/2017 10:38, Stefan Priebe - Profihost AG wrote:
>>> Hello,
>>>
>>> i've upgraded some servers from kernel 4.4 to 4.12 - both running Qemu
>>> 2.9.1.
>>>
>>> If i migra
There are many places for monitor init its globals, at least:
- monitor_init_qmp_commands() at the very beginning
- single function to init monitor_lock
- in the first entry of monitor_init() using "is_first_init"
Unify them a bit.
Signed-off-by: Peter Xu
---
include/monitor/monitor.h | 2 +-
It'll be passed to emit() as well when it happens. Since at it, add a
typedef for the emitter function.
Signed-off-by: Peter Xu
---
include/qapi/qmp/json-streamer.h | 10 --
monitor.c| 7 ---
qga/main.c | 5 +++--
qobject/json-streamer
A quick way to fetch string from qobject when it's a QString.
Signed-off-by: Peter Xu
---
include/qapi/qmp/qstring.h | 1 +
qobject/qstring.c | 11 +++
2 files changed, 12 insertions(+)
diff --git a/include/qapi/qmp/qstring.h b/include/qapi/qmp/qstring.h
index 34278bd639..12ae
Monitor code now can be run in more than one thread. Let the suspend
and resume code for thread safety.
---
monitor.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/monitor.c b/monitor.c
index 1e87de87f8..47e969244d 100644
--- a/monitor.c
+++ b/monitor.c
@@ -4003,7 +4003,
There was no QMP capabilities defined. Define the first "oob" as
capability to allow out-of-band messages.
Also, touch up qmp-test.c to test the new bits.
Signed-off-by: Peter Xu
---
monitor.c| 15 +--
qapi-schema.json | 13 +
tests/qmp-test.c | 10 +-
3
In monitor_qmp_read(), we have the hack to temporarily replace the
cur_mon pointer. Now we move this hack deeper inside the QMP dispatcher
routine since the Monitor pointer can be passed in to that using the new
JSON Parser opaque field now.
This does not make much sense as a single patch. Howev
Originally QMP goes throw these steps:
JSON Parser --> QMP Dispatcher --> Respond
/|\(2)(3) |
(1) | \|/ (4)
+- main thread +
This patch does this:
JSON Parser QMP Dispatcher --> Respond
/|\ |
It's part of the data init. Collect it.
Reviewed-by: Dr. David Alan Gilbert
Signed-off-by: Peter Xu
---
monitor.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/monitor.c b/monitor.c
index e36fb5308d..3940737c1c 100644
--- a/monitor.c
+++ b/monitor.c
@@ -568,13 +56
Hi Paolo,
Am 06.11.2017 um 10:40 schrieb Paolo Bonzini:
> On 06/11/2017 10:38, Stefan Priebe - Profihost AG wrote:
>> Hello,
>>
>> i've upgraded some servers from kernel 4.4 to 4.12 - both running Qemu
>> 2.9.1.
>>
>> If i migrate a VM from a host running kernel 4.4 to a host running 4.12
>> i get
Introduce qmp_cap_enabled() and qmp_oob_enabled() helpers.
---
monitor.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/monitor.c b/monitor.c
index dba56fbcdf..442d711d5d 100644
--- a/monitor.c
+++ b/monitor.c
@@ -1038,6 +1038,16 @@ static void monitor_init_qmp_commands(void)
It was QLIST. I want to use this list to do monitor priority job later,
which need tail insertion ability. So switching to a tail queue.
Signed-off-by: Peter Xu
---
monitor.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/monitor.c b/monitor.c
index ac5313023b..
This event will be emitted if one QMP request is dropped. Along,
declare an enum for the reasons.
Signed-off-by: Peter Xu
---
qapi-schema.json | 35 +++
1 file changed, 35 insertions(+)
diff --git a/qapi-schema.json b/qapi-schema.json
index 531fd4c0db..650714da0
A tiny refactoring, preparing to split the QMP dispatcher away.
Signed-off-by: Peter Xu
---
monitor.c | 48 +++-
1 file changed, 31 insertions(+), 17 deletions(-)
diff --git a/monitor.c b/monitor.c
index 442d711d5d..1e87de87f8 100644
--- a/monitor.c
+
For each Monitor, add one field "use_io_thr" to show whether it will be
using the dedicated monitor IO thread to handle input/output. When set,
monitor IO parsing work will be offloaded to dedicated monitor IO
thread, rather than the original main loop thread.
This only works for QMP. HMP will a
Set maximum QMP request queue length to 8. If queue full, instead of
queue the command, we directly return a "request-dropped" event, telling
client that specific command is dropped.
Note that this flow control mechanism is only valid if OOB is enabled.
If it's not, the effective queue length wil
After this patch, we will allow QMP clients to enable QMP capabilities
when sending the first "qmp_capabilities" command. Originally we are
starting QMP session with no arguments like:
{ "execute": "qmp_capabilities" }
Now we can enable some QMP capabilities using (take OOB as example,
which i
Here "oob" stands for "Out-Of-Band". When "allow-oob" is set, it means
the command allows out-of-band execution.
The "oob" idea is proposed by Markus Armbruster in following thread:
https://lists.gnu.org/archive/html/qemu-devel/2017-09/msg02057.html
This new "allow-oob" boolean will be expose
Create one IOThread for the monitors, prepared to handle all the
input/output IOs using existing iothread framework.
Signed-off-by: Peter Xu
---
monitor.c | 34 ++
1 file changed, 34 insertions(+)
diff --git a/monitor.c b/monitor.c
index a70ab5606b..df1ec8d037 10
So it can get rid of being run on main thread.
Signed-off-by: Peter Xu
---
qapi/migration.json | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/qapi/migration.json b/qapi/migration.json
index bbc4671ded..95098072dd 100644
--- a/qapi/migration.json
+++ b/qapi/migration.json
@
Update both the developer and spec for the new QMP OOB (Out-Of-Band)
command.
Signed-off-by: Peter Xu
---
docs/devel/qapi-code-gen.txt | 51 +++-
docs/interop/qmp-spec.txt| 32 +++
2 files changed, 74 insertions(+), 9 deletions(
2017-11-06 17:41 GMT+08:00 Paolo Bonzini :
> On 06/11/2017 10:11, Wanpeng Li wrote:
>> Hi all,
>>
>> qemu core dump, max_core="unlimited", dump_guest_core=0, kill -11 pid
>> to generate a qemu core file, the Rss of qemu itself is ~40MB, the
>> core file is almost ~40MB in centos 6.x, but ~400MB in
Having "allow-oob" to true for a command does not mean that this command
will always be run in out-of-band mode. The out-of-band quick path will
only be executed if we specify the extra "run-oob" flag when sending the
QMP request:
{ "execute": "command-that-allows-oob",
"arguments": {
Start to use dedicate IO thread for QMP monitors that are not using
MUXed chardev.
Signed-off-by: Peter Xu
---
monitor.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/monitor.c b/monitor.c
index a2550d79a8..be6b3a914f 100644
--- a/monitor.c
+++ b/monitor.c
@@ -36,6 +36,7
Test the new OOB capability. Here we used the "dump-guest-memory"
command to hang the thread a bit to test working of OOB preemption.
Note that currently it is only running for x86/arm/ppc/s390x.
Note that for some platforms we may need to specify "-cpu" to make sure
the dump-guest-memory command
For those monitors who has enabled IO thread, we'll offload the
responding procedure into IO thread. The main reason is that chardev is
not thread safe, and we need to do all the read/write IOs in the same
thread. For use_io_thr=true monitors, that thread is the IO thread.
We do this isolation i
OOB introduced DROP event for flow control. This should not affect old
QMP clients. Add a command batching check to make sure of it.
---
tests/qmp-test.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/tests/qmp-test.c b/tests/qmp-test.c
index 292c5f135a..729ec59b0a 1006
Hi Paolo,
Am 06.11.2017 um 10:49 schrieb Paolo Bonzini:
> On 06/11/2017 10:48, Stefan Priebe - Profihost AG wrote:
>> Hi Paolo,
>>
>> Am 06.11.2017 um 10:40 schrieb Paolo Bonzini:
>>> On 06/11/2017 10:38, Stefan Priebe - Profihost AG wrote:
Hello,
i've upgraded some servers from ker
On 06/11/2017 09:54, Christian Borntraeger wrote:
On 11/06/2017 09:52 AM, Cornelia Huck wrote:
On Mon, 30 Oct 2017 19:58:15 +0100
Halil Pasic wrote:
On 10/30/2017 06:38 PM, Pierre Morel wrote:
On 30/10/2017 18:08, Christian Borntraeger wrote:
On 10/30/2017 05:59 PM, Cornelia Huck wrote:
Hi Peter,
On 02/11/2017 13:53, Peter Maydell wrote:
> On 23 October 2017 at 16:35, Eric Auger wrote:
>> The ITS is not fully properly reset at the moment. Caches are
>> not emptied.
>>
>> After a reset, in case we attempt to save the state before
>> the bound devices have registered their MSIs an
Le 06/11/2017 à 01:44, Alexey Kardashevskiy a écrit :
> On 04/11/17 06:38, Laurent Vivier wrote:
>> linux-user binaries don't need firmware and NMI,
>> so don't add them in this case, move QDEV
>> firmware functions to qdev-fw.c
>
>
> When configured with --target-list=ppc64-linux-user , config-h
> -Original Message-
> From: longpeng
> Sent: Monday, November 06, 2017 2:21 PM
> To: berra...@redhat.com; pbonz...@redhat.com; Gonglei (Arei)
> Cc: longpeng; qemu-devel@nongnu.org
> Subject: [PATCH] crypto: afalg: fix a NULL pointer dereference
>
> Test-crypto-hash calls qcrypto_hash_byt
On 06/11/2017 11:01, Wanpeng Li wrote:
> 2017-11-06 17:41 GMT+08:00 Paolo Bonzini :
>> On 06/11/2017 10:11, Wanpeng Li wrote:
>>> Hi all,
>>>
>>> qemu core dump, max_core="unlimited", dump_guest_core=0, kill -11 pid
>>> to generate a qemu core file, the Rss of qemu itself is ~40MB, the
>>> core fil
On 6 November 2017 at 07:30, Auger Eric wrote:
> Hi Shanker,
>
> On 03/11/2017 13:37, Shanker Donthineni wrote:
>> The commit cddafd8f353d ("hw/intc/arm_gicv3_its: Implement state save
>> /restore") breaks the backward compatibility with the older kernels
>> where vITS save/restore support is not
Hi guys,
What a long time iteration it is.
Hoping this is the final version if no big arguments exist as
discussed with Stefan at KVM Forum 2017 this October. People
can submit patches to fix some grammar issues or little problems,
and then Xin' can submit the asymmetric crypto services spec
bas
On Fri, Nov 03, 2017 at 06:54:44PM +, Peter Maydell wrote:
> On 16 October 2017 at 21:16, Daniel P. Berrange wrote:
> > From: Knut Omang
> >
> > If an offset of ports is specified to the inet_listen_saddr function(),
> > and two or more processes tries to bind from these ports at the same tim
On Fri, Nov 03, 2017 at 06:03:55PM +, Peter Maydell wrote:
> On 3 November 2017 at 15:33, Daniel P. Berrange wrote:
> > This short series of patches improves the reliability of the submodule
> > handling to cope with various dev env scenarios that have since emerged
>
> Can I ask you to write
On Fri, Nov 03, 2017 at 06:46:57PM +, Peter Maydell wrote:
On 8 August 2017 at 21:38, Jens Freimann wrote:
@@ -333,8 +333,13 @@ static NetSocketState
*net_socket_fd_init_dgram(NetClientState *peer,
* by ONLY ONE process: we must "clone" this dgram socket --jjo
*/
-if (is_c
On 6 November 2017 at 00:56, Brad Smith wrote:
> Define TIME_MAX to LLONG_MAX for OpenBSD since OpenBSD uses 64-bit time_t.
>
> Signed-off-by: Brad Smith
>
>
> diff --git a/include/qemu/osdep.h b/include/qemu/osdep.h
> index 6855b94bbf..824714049b 100644
> --- a/include/qemu/osdep.h
> +++ b/inclu
Alexey Kardashevskiy writes:
> Running "qemu-system-ppc64 -machine prep -device i82374" creates an ISA
> bus with two i82374 DMA controllers - one is implicit from ppc_prep_init(),
> the other one is from "-device i82374". QEMU asserts but it is not
> immediately clear why.
>
> This adds an error
On 26 October 2017 at 09:00, Alexey Kardashevskiy wrote:
> Running "qemu-system-ppc64 -machine prep -device i82374" creates an ISA
> bus with two i82374 DMA controllers - one is implicit from ppc_prep_init(),
> the other one is from "-device i82374". QEMU asserts but it is not
> immediately clear
HI Paolo,
could this patchset be related?
Greets,
Stefan
Am 06.11.2017 um 10:52 schrieb Stefan Priebe - Profihost AG:
> Hi Paolo,
>
> Am 06.11.2017 um 10:49 schrieb Paolo Bonzini:
>> On 06/11/2017 10:48, Stefan Priebe - Profihost AG wrote:
>>> Hi Paolo,
>>>
>>> Am 06.11.2017 um 10:40 schrieb Pa
On 6 November 2017 at 10:09, Auger Eric wrote:
> Hi Peter,
>
> On 02/11/2017 13:53, Peter Maydell wrote:
>> On 23 October 2017 at 16:35, Eric Auger wrote:
>>> The ITS is not fully properly reset at the moment. Caches are
>>> not emptied.
>>>
>>> After a reset, in case we attempt to save the state
The following changes since commit b33afc415622e5eb26e0f14fd27eb86e32a5472e:
Merge remote-tracking branch
'remotes/stsquad/tags/pull-ci-updates-for-softfreeze-021117-2' into staging
(2017-11-03 10:08:34 +)
are available in the git repository at:
git://github.com/stefanha/qemu.git tags/
This hunk should not have been merged but I forgot to remove it. Let's
remove it before it slips into a QEMU release.
¯\_(ツ)_/¯
Reviewed-by: Thomas Huth
Signed-off-by: Stefan Hajnoczi
Message-id: 20171103154041.12617-1-stefa...@redhat.com
Signed-off-by: Stefan Hajnoczi
---
util/aio-posix.c |
On Mon, Nov 06, 2017 at 10:51:16AM +, Peter Maydell wrote:
> On 6 November 2017 at 00:56, Brad Smith wrote:
> > Define TIME_MAX to LLONG_MAX for OpenBSD since OpenBSD uses 64-bit time_t.
> >
> > Signed-off-by: Brad Smith
> >
> >
> > diff --git a/include/qemu/osdep.h b/include/qemu/osdep.h
> >
On 06/11/2017 12:09, Stefan Priebe - Profihost AG wrote:
> HI Paolo,
>
> could this patchset be related?
Uh oh, yes it should. Jason, any ways to fix it? I suppose we need to
disable UFO in the newest machine types, but do we also have to do
(software) UFO in vhost-net and QEMU for migration co
On 6 November 2017 at 00:53, Brad Smith wrote:
> OpenBSD/i386 uses elf_i386_obsd for the emulation linker.
>
> Signed-off-by: Brad Smith
>
>
> diff --git a/configure b/configure
> index dd73cce62f..02799d38ac 100755
> --- a/configure
> +++ b/configure
> @@ -5159,9 +5159,9 @@ if test \( "$cpu" = "
The Makefile attempts to optimize the handling of submodules by using MAKELEVEL
to only check the submodule status when running from the top level make
invokation. This causes problems for people who are using a makefile of their
own to in turn invoke QEMU's makefile, as MAKELEVEL is already set to
Signed-off-by: Marc-André Lureau
---
hw/misc/vmcoreinfo.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/hw/misc/vmcoreinfo.c b/hw/misc/vmcoreinfo.c
index a618e12677..31db57ab44 100644
--- a/hw/misc/vmcoreinfo.c
+++ b/hw/misc/vmcoreinfo.c
@@ -79,6 +79,7 @@ static void vmcoreinfo_device_class
vmcoreinfo is built for all targets. However, it requires fw_cfg with
DMA operations support (write operation). Restrict vmcoreinfo exposure
to architectures that are supporting FW_CFG_DMA, that is arm-virt and
x86 only atm.
Signed-off-by: Marc-André Lureau
---
default-configs/arm-softmmu.mak
** Tags added: arm
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/696094
Title:
TI Stellaris lm3s811evb (ARM Cortex-M3) : Systick interrupt not
working
Status in QEMU:
New
Bug description:
I
** Tags added: arm
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/657006
Title:
arm v7M - svc insn doesn't trigger PendSV handler
Status in QEMU:
Incomplete
Bug description:
The svc instructio
On 06.11.2017 12:53, Marc-André Lureau wrote:
> vmcoreinfo is built for all targets. However, it requires fw_cfg with
> DMA operations support (write operation). Restrict vmcoreinfo exposure
> to architectures that are supporting FW_CFG_DMA, that is arm-virt and
> x86 only atm.
>
> Signed-off-by:
On Mon, 11/06 11:26, Paolo Bonzini wrote:
> On 06/11/2017 11:01, Wanpeng Li wrote:
> > 2017-11-06 17:41 GMT+08:00 Paolo Bonzini :
> >> On 06/11/2017 10:11, Wanpeng Li wrote:
> >>> Hi all,
> >>>
> >>> qemu core dump, max_core="unlimited", dump_guest_core=0, kill -11 pid
> >>> to generate a qemu core
On 06/11/2017 12:59, Fam Zheng wrote:
>>> Could you point out the patchset for the fix?
>> Between 447b0d0b9ee8a0ac216c3186e0f3c427a1001f0c and
>> 092aa2fc65b7a35121616aad8f39d47b8f921618.
> Not sure how these relate to the core size, but I've tested upstream
> (ec7a8bf0b8f7dc7288fe8745464ee8217528
Hi
On Mon, Nov 6, 2017 at 12:58 PM, Thomas Huth wrote:
> On 06.11.2017 12:53, Marc-André Lureau wrote:
>> vmcoreinfo is built for all targets. However, it requires fw_cfg with
>> DMA operations support (write operation). Restrict vmcoreinfo exposure
>> to architectures that are supporting FW_CFG_
On 5 November 2017 at 14:56, Paolo Bonzini wrote:
> The following changes since commit b33afc415622e5eb26e0f14fd27eb86e32a5472e:
>
> Merge remote-tracking branch
> 'remotes/stsquad/tags/pull-ci-updates-for-softfreeze-021117-2' into staging
> (2017-11-03 10:08:34 +)
>
> are available in the
On 6 November 2017 at 11:20, Stefan Hajnoczi wrote:
> The following changes since commit b33afc415622e5eb26e0f14fd27eb86e32a5472e:
>
> Merge remote-tracking branch
> 'remotes/stsquad/tags/pull-ci-updates-for-softfreeze-021117-2' into staging
> (2017-11-03 10:08:34 +)
>
> are available in t
Hi. The beaglexm model isn't part of upstream QEMU (it was in a set of
downstream patches for OMAP3 which were never merged upstream and which
are now essentially abandoned.) The root cause of this bug is that
support for pass-through of a host serial port requires specific support
in the device mo
We think we've fixed the multithreading issues in QEMU linux-user (in
particular the test case that started this bug report works). If there
are still problems with a QEMU version later than 2.10, please open
fresh bug reports for specific guest programs that fail, giving detailed
how-to-reproduce
2017-11-06 20:02 GMT+08:00 Paolo Bonzini :
> On 06/11/2017 12:59, Fam Zheng wrote:
Could you point out the patchset for the fix?
>>> Between 447b0d0b9ee8a0ac216c3186e0f3c427a1001f0c and
>>> 092aa2fc65b7a35121616aad8f39d47b8f921618.
>> Not sure how these relate to the core size, but I've tested
On Mon, 6 Nov 2017 11:41:34 +
"Daniel P. Berrange" wrote:
> The Makefile attempts to optimize the handling of submodules by using
> MAKELEVEL
> to only check the submodule status when running from the top level make
> invokation. This causes problems for people who are using a makefile of t
Sorry for the slow response.
Ian Jackson writes:
> This allows the caller to specify a uid and gid to use, even if there
> is no corresponding password entry. This will be useful in certain
> Xen configurations.
>
> Signed-off-by: Ian Jackson
> ---
> v3: Error messages fixed. Thanks to Pe
On 2017-11-03 21:32, Alberto Garcia wrote:
> On Fri 03 Nov 2017 09:22:39 PM CET, Alberto Garcia wrote:
-assert(offset);
>>>
>>> I don't think this assert() was meant as a protection against offset
>>> being 0. :-)
>>
>> After the new check offset is now guaranteed to be 0, so what's th
On 11/06/2017 09:53 AM, Marc-André Lureau wrote:
vmcoreinfo is built for all targets. However, it requires fw_cfg with
DMA operations support (write operation). Restrict vmcoreinfo exposure
to architectures that are supporting FW_CFG_DMA, that is arm-virt and
x86 only atm.
Signed-off-by: Marc-
On 11/6/2017 10:35 AM, Manos Pitsidianakis wrote:
On Fri, Oct 13, 2017 at 09:26:17AM -0500, Eric Blake wrote:
[adding Markus, and block list]
On 10/13/2017 09:16 AM, Alberto Garcia wrote:
On Mon 02 Oct 2017 04:33:28 PM CEST, Pradeep Jagadeesh wrote:
This patch factors out code to use the Thro
On Mon 06 Nov 2017 01:36:01 PM CET, Max Reitz wrote:
> -assert(offset);
I don't think this assert() was meant as a protection against offset
being 0. :-)
>>>
>>> After the new check offset is now guaranteed to be 0, so what's the
>>> point of keeping the assert() ?
>>
>>
On Fri, Nov 03, 2017 at 03:40:41PM +, Stefan Hajnoczi wrote:
> This hunk should not have been merged but I forgot to remove it. Let's
> remove it before it slips into a QEMU release.
>
> ¯\_(ツ)_/¯
>
> Reviewed-by: Thomas Huth
> Signed-off-by: Stefan Hajnoczi
> ---
> util/aio-posix.c | 7 -
Paolo Bonzini writes:
> On 03/11/2017 10:47, Alex Bennée wrote:
>> As deadlocks are easy to introduce a new rule is introduced that the
>> replay_mutex_lock is taken before any BQL locks. Conversely you cannot
>> release the replay_lock while the BQL is still held.
>
> I agree with the for
On Mon, Nov 06, 2017 at 02:12:17AM -0800, no-re...@patchew.org wrote:
> Hi,
>
> This series seems to have some coding style problems. See output below for
> more information:
>
> Subject: [Qemu-devel] [RFC v3 00/27] QMP: out-of-band (OOB) execution support
> Type: series
> Message-id: 20171106094
On 06/11/2017 14:05, Alex Bennée wrote:
>
> Paolo Bonzini writes:
>
>> On 03/11/2017 10:47, Alex Bennée wrote:
>>> As deadlocks are easy to introduce a new rule is introduced that the
>>> replay_mutex_lock is taken before any BQL locks. Conversely you cannot
>>> release the replay_lock whi
This fixes coverity issue CID1005339.
Make sure that saddr is not used uninitialized if the
mcast parameter is NULL.
Cc: qemu-sta...@nongnu.org
Reported-by: Peter Maydell
Signed-off-by: Jens Freimann
---
net/socket.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/net/s
On Fri, 29 Sep 2017 13:13:05 +0200
Michael Fritscher wrote:
> Good day,
>
Hi,
Sorry for the late reply... Since I have only limited bandwidth, I'll only
be able to provide some limited feedback.
A global remark to start with: it is a usual practice to prefix each patch
title with the componen
On 6 November 2017 at 13:28, Jens Freimann wrote:
> This fixes coverity issue CID1005339.
>
> Make sure that saddr is not used uninitialized if the
> mcast parameter is NULL.
>
> Cc: qemu-sta...@nongnu.org
> Reported-by: Peter Maydell
> Signed-off-by: Jens Freimann
> ---
> net/socket.c | 4 ++--
Hi Jan,
On Mon, Nov 06, 2017 at 02:28:05PM +0100, Jens Freimann wrote:
This fixes coverity issue CID1005339.
Make sure that saddr is not used uninitialized if the
mcast parameter is NULL.
Cc: qemu-sta...@nongnu.org
Reported-by: Peter Maydell
Signed-off-by: Jens Freimann
---
net/socket.c | 4
On Fri, 29 Sep 2017 13:13:06 +0200
Michael Fritscher wrote:
> Signed-off-by: Michael Fritscher
> ---
> include/sysemu/os-win32.h | 26 ++
> 1 file changed, 26 insertions(+)
>
> diff --git a/include/sysemu/os-win32.h b/include/sysemu/os-win32.h
> index ff18b23db1..15cc94
On Fri, 29 Sep 2017 13:13:08 +0200
Michael Fritscher wrote:
> Signed-off-by: Michael Fritscher
What's the justification for this patch ?
> ---
> fsdev/qemu-fsdev.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fsdev/qemu-fsdev.c b/fsdev/qemu-fsdev.c
> index 266e442b87..9f6d33365d
On 03/11/2017 09:27, Pavel Dovgalyuk wrote:
>> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
>> On 02/11/2017 12:33, Paolo Bonzini wrote:
>>> On 02/11/2017 12:24, Pavel Dovgalyuk wrote:
> I am not sure about this. I think if instead you should return false
> from here and EXCP_INTERRUPT
On Mon, Nov 06, 2017 at 01:29:42PM +, Peter Maydell wrote:
On 6 November 2017 at 13:28, Jens Freimann wrote:
This fixes coverity issue CID1005339.
Make sure that saddr is not used uninitialized if the
mcast parameter is NULL.
Cc: qemu-sta...@nongnu.org
Reported-by: Peter Maydell
Signed-o
On Mon, Nov 06, 2017 at 01:33:49PM +, Darren Kenny wrote:
Hi Jan,
On Mon, Nov 06, 2017 at 02:28:05PM +0100, Jens Freimann wrote:
This fixes coverity issue CID1005339.
Make sure that saddr is not used uninitialized if the
mcast parameter is NULL.
Cc: qemu-sta...@nongnu.org
Reported-by: Pet
On 6 November 2017 at 13:48, Jens Freimann wrote:
> On Mon, Nov 06, 2017 at 01:29:42PM +, Peter Maydell wrote:
>> Do we really need the initialization here? With the two if()
>> conditions aligned we should be properly initializing it
>> in all the cases we use it, or have I missed one?
>
>
>
Pavel Dovgalyuk writes:
>> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
>> On 02/11/2017 12:33, Paolo Bonzini wrote:
>> > On 02/11/2017 12:24, Pavel Dovgalyuk wrote:
>> >>> I am not sure about this. I think if instead you should return false
>> >>> from here and EXCP_INTERRUPT from cpu_exec
1 - 100 of 383 matches
Mail list logo
