[Qemu-devel] Guest Reboot After Plug HDMI

Hello, Everybody. I encounter a problem when i using my guest. I booting my guest without HDMI primarily, Then i add it, but my guest is be rebooted. To know what cause it, i do it again, especially i check my guest is running normal or not with "ping" before plugging, that's well. What i wa

Re: [Qemu-devel] [PATCH 1/2] colo: compare the packet based on the tcp sequence number

On 12/04/2017 03:24 PM, Zhang Chen wrote: On Mon, Dec 4, 2017 at 3:32 AM, Mao Zhongyi mailto:maozy.f...@cn.fujitsu.com>> wrote: On 12/04/2017 09:41 AM, Zhang Chen wrote: On Tue, Nov 28, 2017 at 8:04 PM, Mao Zhongyi mailto:maozy.f...@cn.fujitsu.com>

Re: [Qemu-devel] [PATCH 17/25] spapr: add a sPAPRXive object to the machine

On 12/04/2017 02:59 AM, David Gibson wrote: > On Fri, Dec 01, 2017 at 09:10:24AM +0100, Cédric Le Goater wrote: >> On 12/01/2017 05:14 AM, David Gibson wrote: >>> On Thu, Nov 30, 2017 at 03:15:09PM +, Cédric Le Goater wrote: On 11/30/2017 05:55 AM, David Gibson wrote: > On Thu, Nov 23,

Re: [Qemu-devel] [PATCH 20/25] spapr: add device tree support for the XIVE interrupt mode

On Thu, Nov 23, 2017 at 02:29:50PM +0100, Cédric Le Goater wrote: > The XIVE interface for the guest is described in the device tree under > the "interrupt-controller" node. A couple of new properties are > specific to XIVE : > > - "reg" > >contains the base address and size of the thread in

Re: [Qemu-devel] [PATCH 21/25] spapr: introduce a helper to map the XIVE memory regions

On Thu, Nov 23, 2017 at 02:29:51PM +0100, Cédric Le Goater wrote: > When the XIVE interrupt mode is activated, the machine needs to expose > to the guest the MMIO regions use by the controller : > > - Event State Buffer (ESB) > - Thread Interrupt Management Area (TIMA) > > Migration will also

Re: [Qemu-devel] [PATCH 23/25] spapr: toggle the ICP depending on the selected interrupt mode

On Thu, Nov 23, 2017 at 02:29:53PM +0100, Cédric Le Goater wrote: > Each interrupt mode has its own specific interrupt presenter object, > that we store under the CPU object, one for XICS and one for XIVE. The > active presenter, corresponding to the current interrupt mode, is > simply selected wit

Re: [Qemu-devel] [PATCH 22/25] spapr: add XIVE support to spapr_irq_get_qirq()

On Thu, Nov 23, 2017 at 02:29:52PM +0100, Cédric Le Goater wrote: > The XIVE object has its own set of qirqs which is to be used when the > XIVE interrupt mode is activated. > > Signed-off-by: Cédric Le Goater > --- > hw/ppc/spapr.c | 8 ++-- > 1 file changed, 6 insertions(+), 2 deletions(-)

Re: [Qemu-devel] [PATCH 17/25] spapr: add a sPAPRXive object to the machine

On Mon, Dec 04, 2017 at 09:32:00AM +0100, Cédric Le Goater wrote: > On 12/04/2017 02:59 AM, David Gibson wrote: > > On Fri, Dec 01, 2017 at 09:10:24AM +0100, Cédric Le Goater wrote: > >> On 12/01/2017 05:14 AM, David Gibson wrote: > >>> On Thu, Nov 30, 2017 at 03:15:09PM +, Cédric Le Goater wro

Re: [Qemu-devel] [PATCH v4 12/20] qed: Switch to .bdrv_co_block_status()

01.12.2017 02:17, Eric Blake wrote: On 11/30/2017 04:27 AM, Vladimir Sementsov-Ogievskiy wrote: 12.10.2017 21:59, Eric Blake wrote: We are gradually moving away from sector-based interfaces, towards byte-based.  Update the qed driver accordingly, taking the opportunity to inline qed_is_allocate

Re: [Qemu-devel] [PATCH RFC 0/2] s390x: cut down on unattached devices

On Fri, 1 Dec 2017 15:41:21 +0100 Halil Pasic wrote: > On 11/28/2017 04:21 PM, Halil Pasic wrote: > [..] > >>> Otherwise at first glance both patches seem sane. > >> > >> Can I count this as an ack, or do you plan to do more review? > >> > > > > Yes I was planning to give it another look. An

Re: [Qemu-devel] [Bug 1735384] Re: OpenJDK JVM segfaults on qemu-sh4 (regression)

Thomas Huth writes: > On 01.12.2017 00:25, John Paul Adrian Glaubitz wrote: >> The offending commit is: >> >> d25f2a72272b9ffe0d06710d6217d1169bc2cc7d is the first bad commit >> commit d25f2a72272b9ffe0d06710d6217d1169bc2cc7d >> Author: Alex Bennée >> Date: Mon Nov 13 13:55:27 2017 + >>

Re: [Qemu-devel] [PATCH 08/17] e500: additional CCSR registers

On Sun, Nov 26, 2017 at 03:59:06PM -0600, Michael Davidsaver wrote: > Add CCSRBAR to allow CCSR region to be relocated. > > Guest memory size introspection via RAM config > registers. > > Dummy RAM error controls. > > Clock introspection via Power on Reset PLL > Status Register. > > Signed-off-

Re: [Qemu-devel] [PULL 0/7] pc, pci, virtio: fixes for rc3

On 3 December 2017 at 04:56, Michael S. Tsirkin wrote: > On Fri, Dec 01, 2017 at 06:05:25PM +, Peter Maydell wrote: >> On 1 December 2017 at 17:08, Michael S. Tsirkin wrote: >> > Chao Gao (1): >> > i386/msi: Correct mask of destination ID in MSI address >> > >> > Greg Kurz (1): >> >

Re: [Qemu-devel] Block layer complexity: what to do to keep it under control?

On Fri, Dec 01, 2017 at 01:27:37PM -0600, Eric Blake wrote: > On 12/01/2017 11:03 AM, Paolo Bonzini wrote: > > Just my 2 cents on the language topic, as in general I agree completely > > with Stefan. > > > > > Luckily, several benefits don't require a full rewrite or language switch: > > > > - r

Re: [Qemu-devel] [PULL 0/3] ppc-for-2.11 queue 20171204

qemu.git tags/ppc-for-2.11-20171204 > > for you to fetch changes up to 768a20f3a491ed4afce73ebb65347d55251c0ebd: > > spapr: Include "pre-plugged" DIMMS in ram size calculation at reset > (2017-12-04 11:31:22 +1100) > > -

[Qemu-devel] [PATCH v2] pci: removed the is_express field since a uniform interface was inserted

* according to Eduardo Habkost's commit fd3b02c8896d597dd8b9e053dec579cf0386aee1 * since all PCIEs now implement INTERFACE_PCIE_DEVICE we don't need this field anymore * Devices that where only INTERFACE_PCIE_DEVICE (is_express == 1) or

Re: [Qemu-devel] Block layer complexity: what to do to keep it under control?

On 4 December 2017 at 10:16, Stefan Hajnoczi wrote: > Yes, please! __attribute__((cleanup)) is great and we should use it in > QEMU. > > I haven't looked at compiler support though... :) Looks like it came in in gcc 3.6, which is earlier than our earliest required version. For clang, it's harder

Re: [Qemu-devel] Block layer complexity: what to do to keep it under control?

On Fri, Dec 01, 2017 at 07:03:15PM +, Peter Maydell wrote: > On 1 December 2017 at 17:03, Paolo Bonzini wrote: > > Same here. Just like fixing the C code provides a good foundation for a > > language switch, some more battle-tested code could be converted from > > QEMU to Rust, in order to ge

Re: [Qemu-devel] [PATCH] spapr: fix LSI interrupt specifiers in the device tree

On Sun, 3 Dec 2017 10:37:35 +1100 David Gibson wrote: > On Sat, Dec 02, 2017 at 08:30:11PM +0100, Greg Kurz wrote: > > PAPR 2.7 C.6.9.1.2 describes the "#interrupt-cells" property of the > > PowerPC External Interrupt Source Controller node as follows: > > > > “#interrupt-cells” > > > > Stand

[Qemu-devel] CFP deadline extended for FOSDEM18 Virt & IaaS Devroom

The call for papers for the Virtualization and IaaS Devroom at FOSDEM18 is extended until December 7 midnight UTC. All other dates remain the same as you can read below. On behalf of oVirt and the Xen Project, we are excited to announce that the call for proposals is now open for the Virtualizatio

Re: [Qemu-devel] [PATCH 1/3] s390x/css: unrestrict cssids

On Fri, 1 Dec 2017 15:31:34 +0100 Halil Pasic wrote: > The default css 0xfe is currently restricted to virtual subchannel > devices. The hope when the decision was made was, that non-virtual > subchannel devices will come around when guests can exploit multiple > channel subsystems. Since curren

Re: [Qemu-devel] [PATCH 2/3] s390x/css: advertise unrestricted cssids

On Fri, 1 Dec 2017 15:31:35 +0100 Halil Pasic wrote: > Let us advertise the changes introduced by "s390x/css: unrestrict cssids" > to the management software (so it can tell are cssids unrestricted or > restricted). > > Signed-off-by: Halil Pasic > --- > > Boris says having the property on th

Re: [Qemu-devel] [PATCH 2/3] s390x/css: advertise unrestricted cssids

On 12/01/2017 03:31 PM, Halil Pasic wrote: > Let us advertise the changes introduced by "s390x/css: unrestrict cssids" > to the management software (so it can tell are cssids unrestricted or > restricted). > > Signed-off-by: Halil Pasic > --- > > Boris says having the property on the virtual-c

Re: [Qemu-devel] [qemu-s390x] [PATCH RFC 2/2] s390x: attach autogenerated nics

On 11/28/2017 02:46 PM, Cornelia Huck wrote: > The autogenerated nics should be treated as any other device; use > qdev_set_id() to have them show up under peripheral-anon. > I think this is fine, but then I ask myself how x86 does this. So I tried to find out how the pc-q35 machine does this b

Re: [Qemu-devel] [PATCH 3/3] s390x: deprecate s390-squash-mcss machine prop

On Fri, 1 Dec 2017 15:31:36 +0100 Halil Pasic wrote: > With the cssids unrestricted (commit "s390x/css: unrestrict I won't add the commit id, as I intend to merge this in one go and I don't want to edit this every time I rebase prior to pull. > cssids") the s390-squash-mcss machine property s

Re: [Qemu-devel] [qemu-s390x] [PATCH RFC 0/2] s390x: cut down on unattached devices

On 28.11.2017 14:46, Cornelia Huck wrote: > info qom-tree shows several devices under unattached that probably > should go somewhere. > > The css bridge should attach to the machine, as it has a similar > purpose as e.g. a pci host bridge. > > The autogenerated network devices should be in the sa

[Qemu-devel] [Bug 1318474] Re: QEMU update causes Windows reactivation

When updating QEMU use specific machine type and this will keep "old" HW. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1318474 Title: QEMU update causes Windows reactivation Status in QEMU: Exp

[Qemu-devel] [Bug 1736042] [NEW] qemu-system-x86_64 does not boot image reliably

You have been subscribed to a public bug: Booting image as root user with following command works randomly. ./qemu-system-x86_64 -enable-kvm -curses -smp cpus=4 -m 8192 /root/ructfe2917_g.qcow2 Most of the time it ends up on "800x600 Graphic mode"(been stuck there even for 4 hours before killed)

Re: [Qemu-devel] [PATCH v3] rcu: reduce more than 7MB heap memory by malloc_trim()

On Fri, Dec 01, 2017 at 01:52:49PM +0100, Paolo Bonzini wrote: > On 01/12/2017 11:56, Yang Zhong wrote: > > This issue should be caused by much times of system call by malloc_trim(), > > Shannon's test script include 60 scsi disks and 31 ioh3420 devices. We > > need > > trade-off between VM

Re: [Qemu-devel] [Bug 1735384] Re: OpenJDK JVM segfaults on qemu-sh4 (regression)

On 12/04/2017 10:29 AM, Alex Bennée wrote: > It's hard to imagine a scenario where taking the tb_lock() for resolving > something that will fail is going to be an improvement. However maybe > there is a subtle difference with sh4's javavm implementation. So, OpenJDK doesn't have a SH-specific impl

Re: [Qemu-devel] [PATCH v3] qemu-img: add the simplest format recognition

Am 02.12.2017 um 00:49 hat Klim Kireev geschrieben: > Now, if you type something like > > qemu-img create disk.qcow2 1G > or > qemu-img dd if=/dev/sda of=disk.qcow2 > > it creates a raw image and if you need you should > manually specify an image format with -f qcow2. It would > be more convenien

Re: [Qemu-devel] [PATCH v3] rcu: reduce more than 7MB heap memory by malloc_trim()

On Mon, Dec 04, 2017 at 08:03:22PM +0800, Yang Zhong wrote: > On Fri, Dec 01, 2017 at 01:52:49PM +0100, Paolo Bonzini wrote: > > On 01/12/2017 11:56, Yang Zhong wrote: > > > This issue should be caused by much times of system call by > > > malloc_trim(), > > > Shannon's test script include 60

[Qemu-devel] [Bug 1736042] Re: qemu-system-x86_64 does not boot image reliably

I want a fix ;) and I do expect qemu to get it faster then Ubuntu. So I set up Ubuntu Zesty(to fullfill dependencies) and build qemu: QEMU emulator version 2.10.1 (v2.10.1-dirty) and... it's still there. Can you tell me how and what logs to provide? ** Package changed: qemu (Ubuntu) => qemu --

[Qemu-devel] [Bug 1736042] Re: qemu-system-x86_64 does not boot image reliably

And it still happens on: QEMU emulator version 2.10.93 (v2.11.0-rc3-dirty) Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/173604

Re: [Qemu-devel] [PATCH v13 00/12] Add ARMv8 RAS virtualization support in QEMU

ping again. thanks On 2017/11/28 2:39, Dongjiu Geng wrote: > From: gengdongjiu > > In the ARMv8 platform, the CPU error type are synchronous external > abort(SEA) and SError Interrupt (SEI). If guest happen exception, > sometimes guest itself do the recovery is better, because host > does n

Re: [Qemu-devel] [PATCH v3] rcu: reduce more than 7MB heap memory by malloc_trim()

On Mon, Dec 04, 2017 at 12:07:05PM +, Daniel P. Berrange wrote: > On Mon, Dec 04, 2017 at 08:03:22PM +0800, Yang Zhong wrote: > > On Fri, Dec 01, 2017 at 01:52:49PM +0100, Paolo Bonzini wrote: > > > On 01/12/2017 11:56, Yang Zhong wrote: > > > > This issue should be caused by much times of sy

Re: [Qemu-devel] [PATCH v3] rcu: reduce more than 7MB heap memory by malloc_trim()

On 04/12/2017 13:07, Daniel P. Berrange wrote: > On Mon, Dec 04, 2017 at 08:03:22PM +0800, Yang Zhong wrote: >> On Fri, Dec 01, 2017 at 01:52:49PM +0100, Paolo Bonzini wrote: >>> On 01/12/2017 11:56, Yang Zhong wrote: This issue should be caused by much times of system call by malloc_t

Re: [Qemu-devel] [PATCH v3] rcu: reduce more than 7MB heap memory by malloc_trim()

Hi Yang, On 2017/12/4 20:03, Yang Zhong wrote: > On Fri, Dec 01, 2017 at 01:52:49PM +0100, Paolo Bonzini wrote: >> > On 01/12/2017 11:56, Yang Zhong wrote: >>> > > This issue should be caused by much times of system call by >>> > > malloc_trim(), >>> > > Shannon's test script include 60 scsi

Re: [Qemu-devel] [PATCH 2/2] qmp: add nbd-server-remove

Am 09.11.2017 um 16:40 hat Vladimir Sementsov-Ogievskiy geschrieben: > Add command for export removing. It is needed for cases when we > don't want to keep export after the operation on it was completed. > The other example is temporary node, created with blockdev-add. > If we want to delete it we

Re: [Qemu-devel] [PATCH 2/2] qmp: add nbd-server-remove

04.12.2017 15:32, Kevin Wolf wrote: Am 09.11.2017 um 16:40 hat Vladimir Sementsov-Ogievskiy geschrieben: Add command for export removing. It is needed for cases when we don't want to keep export after the operation on it was completed. The other example is temporary node, created with blockdev-a

[Qemu-devel] [PATCH v1 for-2.12 2/5] s390x/tcg: fix and cleanup mcck injection

The architecture mode indication wasn't stored. The split of certain 64bit fields was unnecessary. Also, the complete clock comparator, not just bit 0-55 (starting at byte 1) was stored. We now generate a proper MCIC via the same helper we use for KVM. While at it, also get rid of two local varia

[Qemu-devel] [PATCH v1 for-2.12 4/5] s390x/tcg: indicate value of TODPR in STCKE

We were not yet using the value of the TOD Programmable Register. Signed-off-by: David Hildenbrand --- target/s390x/translate.c | 5 + 1 file changed, 5 insertions(+) diff --git a/target/s390x/translate.c b/target/s390x/translate.c index 48b031894a..8da8610839 100644 --- a/target/s390x/tran

[Qemu-devel] [PATCH v1 for-2.12 5/5] s390x/tcg: wire up STORE CHANNEL REPORT WORD

We somehow missed that, new kernels require it. Signed-off-by: David Hildenbrand --- target/s390x/helper.h | 1 + target/s390x/insn-data.def | 1 + target/s390x/misc_helper.c | 9 + target/s390x/translate.c | 8 4 files changed, 19 insertions(+) diff --git a/target/s390x

[Qemu-devel] [PATCH v1 for-2.12 0/5] s390x/tcg: CCW hotplug support

Hotplugging a ccw device currently fails due to different reasons. 1. The stored machine check information is partially wrong. 2. The TOD programmable field cannot be restored. 3. STCRW cannot get executed. With these patches, I am able to sucessfully hotplug e.g. virtio-rng by issuing "device_ad

[Qemu-devel] [PATCH v1 for-2.12 1/5] s390x/kvm: factor out build_channel_report_mcic() into cpu.h

We'll need it later on in two places. Refactor it to just indicate the valid bit. While at it, introduce a define for the used CR14 bit (we'll also need later on). Signed-off-by: David Hildenbrand --- target/s390x/cpu.h | 20 target/s390x/kvm.c | 25 ++---

[Qemu-devel] [PATCH v1 for-2.12 3/5] s390x/tcg: implement SET CLOCK PROGRAMMABLE FIELD

Needed for machine check handling inside Linux (when restoring registers). Except for SIGP and machine checks, we don't make use of the register yet. Suficient for now. Signed-off-by: David Hildenbrand --- target/s390x/helper.h | 1 + target/s390x/insn-data.def | 2 ++ target/s390x/misc_

Re: [Qemu-devel] [PATCH v1 for-2.12 0/5] s390x/tcg: CCW hotplug support

On 04.12.2017 14:10, no-re...@patchew.org wrote: > Hi, > > This series failed build test on s390x host. Please find the details below. > > Subject: [Qemu-devel] [PATCH v1 for-2.12 0/5] s390x/tcg: CCW hotplug support > Type: series > Message-id: 20171204125505.29203-1-da...@redhat.com Based on s3

Re: [Qemu-devel] [PATCH 1/3] s390x/css: unrestrict cssids

On 12/04/2017 12:10 PM, Cornelia Huck wrote: [..] > >> >> Signed-off-by: Halil Pasic squashed or non-squashed: Acked-by: Christian Borntraeger

Re: [Qemu-devel] [Bug 1735384] Re: OpenJDK JVM segfaults on qemu-sh4 (regression)

John Paul Adrian Glaubitz writes: > On 12/04/2017 10:29 AM, Alex Bennée wrote: >> It's hard to imagine a scenario where taking the tb_lock() for resolving >> something that will fail is going to be an improvement. However maybe >> there is a subtle difference with sh4's javavm implementation. >

[Qemu-devel] [PATCH v1 for-2.12 0/9] s390x/tcg: facilitites and instructions

Wire up some io instructions and implement new facilitites. Make sure to take care of MTTCG when it comes to atomic operations. As we are now able to install/boot a Fedora 26/27 as well as an upstream kernel compiled for z12, let's bump up the QEMU cpu model to a very stripped down version of a z1

[Qemu-devel] [PATCH v1 for-2.12 2/9] s390x/tcg: implement Interlocked-Access Facility 2

With this facility, OI/OIY, NI/NIY and XI/XIY are atomic. All operate on one byte (MO_UB). Signed-off-by: David Hildenbrand --- target/s390x/cpu_models.c | 1 + target/s390x/insn-data.def | 12 ++-- target/s390x/translate.c | 33 + 3 files changed, 40

[Qemu-devel] [PATCH v1 for-2.12 1/9] s390x/tcg: ALSI/ALSGI are atomic with interlocked-acccess facility 1

We can simply reuse our ASI implementation. Only the way CC is calculated differs. Signed-off-by: David Hildenbrand --- target/s390x/insn-data.def | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/target/s390x/insn-data.def b/target/s390x/insn-data.def index 57f2e5133f..166

[Qemu-devel] [PATCH v1 for-2.12 3/9] s390x/tcg: wire up SET ADDRESS LIMIT

Let's handle it just like KVM: Depending on the model, this instruction may not be provided. When this instruction is not provided, it is checked for operand exception and privileged-opera- tion exception, and then is suppressed. Signed-off-by: David Hildenbrand --- target/s390x/

[Qemu-devel] [PATCH v1 for-2.12 8/9] s390x/tcg: we already implement the Set-Program-Parameter facility

The Set-Program-Parameter facility (also known as Load-Program-Parameter faciliy) provides the LPP instruction used to load the program parameter. We already implement that instruction in TCG, so add it to our list. Note: Not documented in the PoP but in "The Load-Program-Parameter and CPU-Measure

[Qemu-devel] [PATCH v1 for-2.12 7/9] s390x/tcg: implement extract-CPU-time facility

It only provies the EXTRACT CPU TIME instruction. We can reuse the stpt helper, which calculates the CPU timer value. As the instruction is not priviledged, but we don't have a CPU timer value in case of linux user, we simply fake the CPU timer to be 0. Signed-off-by: David Hildenbrand --- targ

[Qemu-devel] [PATCH v1 for-2.12 5/9] s390x/tcg: Implement STORE CHANNEL PATH STATUS

Just like KVM does, we should suppress this instruction: When this instruction is not provided, it is checked for privileged operation exception and the instruction is suppressed by the machine Signed-off-by: David Hildenbrand --- target/s390x/insn-data.def | 1 + target/s390x/transl

[Qemu-devel] [PATCH v1 for-2.12 9/9] s390x: change the QEMU cpu model to a stripped down z12

We are good enough to boot upstream Linux kernels / Fedora 26/27. That should be suficient for now. As the QEMU CPU model is migration safe, let's add compatibility code. Generate the feature list to reduce the trouble of messing things up in the future. Signed-off-by: David Hildenbrand --- hw/

[Qemu-devel] [PATCH v1 for-2.12 4/9] s390x/tcg: wire up SET CHANNEL MONITOR

Let's just wire it up like KVM. Signed-off-by: David Hildenbrand --- target/s390x/helper.h | 1 + target/s390x/insn-data.def | 1 + target/s390x/misc_helper.c | 9 + target/s390x/translate.c | 7 +++ 4 files changed, 18 insertions(+) diff --git a/target/s390x/helper.h b/targe

[Qemu-devel] [PATCH v1 for-2.12 01/10] s390x/tcg: ASI/ASGI are atomic with interlocked-acccess facility 1

The semantics of these operations changed. Let's implement them just like LOAD AND ADD, so they are atomic. This fixes random crashes when booting a Linux kernel compiled for z196+ with SMP + MTTCG. Signed-off-by: David Hildenbrand --- Whoops, forgot to include this patch as the first one. ta

[Qemu-devel] [PATCH v1 for-2.12 6/9] s390x/tcg: Implement SIGA instruction

I have no idea what that instruction does, but KVM seems to suppress it, setting cc=3 (and as it seems to be an io instruction, it should be protected). Let's do the same for TCG, so we're at least equal. (it is used in the kernel for qdio, I wasn't even able to find the real name of that instruc

[Qemu-devel] [PATCH] linux-user: Fix locking order in fork_start()

Our locking order is that the tb lock should be taken inside the mmap_lock, but fork_start() grabs locks the other way around. This means that if a heavily multithreaded guest process (such as Java) calls fork() it can deadlock, with the thread that called fork() stuck in fork_start() with the tb l

Re: [Qemu-devel] [PULL 0/3] ppc-for-2.11 queue 20171204

>> are available in the Git repository at: >> >> git://github.com/dgibson/qemu.git tags/ppc-for-2.11-20171204 >> >> for you to fetch changes up to 768a20f3a491ed4afce73ebb65347d55251c0ebd: >> >> spapr: Include "pre-plug

[Qemu-devel] [PATCH v2] spapr: fix LSI interrupt specifiers in the device tree

PAPR 2.7 C.6.9.1.2 describes the "#interrupt-cells" property of the PowerPC External Interrupt Source Controller node as follows: “#interrupt-cells” Standard property name to define the number of cells in an interrupt- specifier within an interrupt domain. prop-encoded-array: An integer, e

Re: [Qemu-devel] [PATCH RFC 0/2] s390x: cut down on unattached devices

On 12/04/2017 10:22 AM, Cornelia Huck wrote: > On Fri, 1 Dec 2017 15:41:21 +0100 > Halil Pasic wrote: > >> On 11/28/2017 04:21 PM, Halil Pasic wrote: >> [..] > Otherwise at first glance both patches seem sane. Can I count this as an ack, or do you plan to do more review?

Re: [Qemu-devel] [PATCH v3 2/2] tests/qemu-iotests: adding savevm/loadvm with postcopy flag test

On 2017-12-03 21:13, Daniel Henrique Barboza wrote: > Hi Max, > > On 12/01/2017 06:13 PM, Max Reitz wrote: >> On 2017-11-16 23:35, Daniel Henrique Barboza wrote: >>> This patch implements a test case for the scenario that was failing >>> prior to the patch "migration/ram.c: do not set 'postcopy_ru

Re: [Qemu-devel] [PATCH v7 for-2.12 10/25] block: Fix bdrv_find_backing_image()

On Mon 20 Nov 2017 09:09:49 PM CET, Max Reitz wrote: > bdrv_find_backing_image() should use bdrv_get_full_backing_filename() or > bdrv_make_absolute_filename() instead of trying to do what those > functions do by itself. > > path_combine_deprecated() can now be dropped, so let's do that. > > Signed

Re: [Qemu-devel] [PATCH v7 for-2.12 14/25] block/nbd: Make bdrv_dirname() return NULL

On Mon 20 Nov 2017 09:09:53 PM CET, Max Reitz wrote: > The generic bdrv_dirname() implementation would be able to generate some > form of directory name for many NBD nodes, but it would be always wrong. > Therefore, we have to explicitly make it an error (until NBD has some > form of specification

Re: [Qemu-devel] [PATCH 1/3] s390x/css: unrestrict cssids

On 12/04/2017 12:10 PM, Cornelia Huck wrote: > On Fri, 1 Dec 2017 15:31:34 +0100 > Halil Pasic wrote: > >> The default css 0xfe is currently restricted to virtual subchannel >> devices. The hope when the decision was made was, that non-virtual >> subchannel devices will come around when guests

Re: [Qemu-devel] [PATCH v3 2/2] tests/qemu-iotests: adding savevm/loadvm with postcopy flag test

On 2017-12-04 16:01, Daniel Henrique Barboza wrote: > > > On 12/04/2017 12:50 PM, Max Reitz wrote: >> On 2017-12-03 21:13, Daniel Henrique Barboza wrote: >>> Hi Max, >>> >>> On 12/01/2017 06:13 PM, Max Reitz wrote: On 2017-11-16 23:35, Daniel Henrique Barboza wrote: > This patch implemen

Re: [Qemu-devel] [PATCH 2/3] s390x/css: advertise unrestricted cssids

On 12/04/2017 12:15 PM, Cornelia Huck wrote: > On Fri, 1 Dec 2017 15:31:35 +0100 > Halil Pasic wrote: > >> Let us advertise the changes introduced by "s390x/css: unrestrict cssids" >> to the management software (so it can tell are cssids unrestricted or >> restricted). >> >> Signed-off-by: Hal

Re: [Qemu-devel] [PATCH v7 for-2.12 17/25] iotests: Add quorum case to test 110

On Mon 20 Nov 2017 09:09:56 PM CET, Max Reitz wrote: > Test 110 tests relative backing filenames for complex BDS trees. Now > that the originally supposedly failing test passes, let us add a new > failing test: Quorum can never work automatically (without detecting > whether all child nodes have t

Re: [Qemu-devel] [PATCH v3 2/2] tests/qemu-iotests: adding savevm/loadvm with postcopy flag test

On 12/04/2017 12:50 PM, Max Reitz wrote: On 2017-12-03 21:13, Daniel Henrique Barboza wrote: Hi Max, On 12/01/2017 06:13 PM, Max Reitz wrote: On 2017-11-16 23:35, Daniel Henrique Barboza wrote: This patch implements a test case for the scenario that was failing prior to the patch "migration

Re: [Qemu-devel] [PATCH v3 2/2] tests/qemu-iotests: adding savevm/loadvm with postcopy flag test

On 12/04/2017 01:06 PM, Max Reitz wrote: On 2017-12-04 16:01, Daniel Henrique Barboza wrote: On 12/04/2017 12:50 PM, Max Reitz wrote: On 2017-12-03 21:13, Daniel Henrique Barboza wrote: Hi Max, On 12/01/2017 06:13 PM, Max Reitz wrote: On 2017-11-16 23:35, Daniel Henrique Barboza wrote: T

[Qemu-devel] [PULL 0/1] baum braille device update

warning: redirection vers https://people.debian.org/~sthibault/qemu.git/ The following changes since commit 7edaf99759017d3e175e37cffc3536e86a3bd380: Merge remote-tracking branch 'remotes/thibault/tags/samuel-thibault' into staging (2017-11-13 13:54:59 +) are available in the Git repositor

[Qemu-devel] [PULL 1/1] baum: Truncate braille device size to 84x1

Baum device bigger than 84 do not actually exist, some guest drivers would be upset by such sizes. Signed-off-by: Samuel Thibault --- chardev/baum.c | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/chardev/baum.c b/chardev/baum.c index 67fd783a59..78b0c87625 100644 ---

[Qemu-devel] [PATCH v4 0/1] savevm/loadvm with postcopy flag qemu-iotest

Changes from v3: - rebased with master - file name changed from 198 to 201 - removed Creator/owner information (it can be retrieved with git) - added a migration successful check before executing savevm - removed a trailing double comma in the snapshot name Daniel Henrique Barboza (1): tests/qe

[Qemu-devel] [PATCH v4 1/1] tests/qemu-iotests: adding savevm/loadvm with postcopy flag test

This patch implements a test case for the scenario that was failing prior to the patch "migration/ram.c: do not set 'postcopy_running' in POSTCOPY_INCOMING_END", commit acab30b85d. This new test file 201 was derived from the test file 181 authored by Kevin Wolf. CC: Kevin Wolf CC: Max Reitz CC:

Re: [Qemu-devel] [PULL 0/1] baum braille device update

On 4 December 2017 at 15:17, Samuel Thibault wrote: > warning: redirection vers https://people.debian.org/~sthibault/qemu.git/ > The following changes since commit 7edaf99759017d3e175e37cffc3536e86a3bd380: > > Merge remote-tracking branch 'remotes/thibault/tags/samuel-thibault' into > staging (

Re: [Qemu-devel] [PULL 0/1] baum braille device update

Hello, Peter Maydell, on lun. 04 déc. 2017 15:21:48 +, wrote: > On 4 December 2017 at 15:17, Samuel Thibault > wrote: > > warning: redirection vers https://people.debian.org/~sthibault/qemu.git/ > > The following changes since commit 7edaf99759017d3e175e37cffc3536e86a3bd380: > > > > Merge r

Re: [Qemu-devel] [PATCH 21/25] spapr: introduce a helper to map the XIVE memory regions

On 12/04/2017 08:52 AM, David Gibson wrote: > On Thu, Nov 23, 2017 at 02:29:51PM +0100, Cédric Le Goater wrote: >> When the XIVE interrupt mode is activated, the machine needs to expose >> to the guest the MMIO regions use by the controller : >> >> - Event State Buffer (ESB) >> - Thread Interru

Re: [Qemu-devel] [PATCH 3/3] s390x: deprecate s390-squash-mcss machine prop

On 12/04/2017 12:28 PM, Cornelia Huck wrote: > On Fri, 1 Dec 2017 15:31:36 +0100 > Halil Pasic wrote: > >> With the cssids unrestricted (commit "s390x/css: unrestrict > > I won't add the commit id, as I intend to merge this in one go and I > don't want to edit this every time I rebase prior

Re: [Qemu-devel] [PULL 0/1] baum braille device update

On 4 December 2017 at 15:26, Samuel Thibault wrote: > Hello, > > Peter Maydell, on lun. 04 déc. 2017 15:21:48 +, wrote: >> On 4 December 2017 at 15:17, Samuel Thibault >> wrote: >> > >> > Samuel Thibault (1): >> > baum: Tr

Re: [Qemu-devel] [PATCH] qemu-img: Fixed grammatical error in dump_human_image_check

On Sat, 12/02 14:37, Shravan Rajinikanth wrote: > Signed-off-by: Shravan Rajinikanth > --- > qemu-img.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/qemu-img.c b/qemu-img.c > index 68b375f..bea9268 100644 > --- a/qemu-img.c > +++ b/qemu-img.c > @@ -580,7 +580,7 @@ sta

Re: [Qemu-devel] [PATCH] qemu-img: Fixed grammatical error in dump_human_image_check

On 2017-12-02 23:37, Shravan Rajinikanth wrote: > Signed-off-by: Shravan Rajinikanth > --- > qemu-img.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/qemu-img.c b/qemu-img.c > index 68b375f..bea9268 100644 > --- a/qemu-img.c > +++ b/qemu-img.c > @@ -580,7 +580,7 @@ sta

Re: [Qemu-devel] [PATCH] qemu-img: Fixed grammatical error in dump_human_image_check

On 4 December 2017 at 15:51, Max Reitz wrote: > On 2017-12-02 23:37, Shravan Rajinikanth wrote: >> Signed-off-by: Shravan Rajinikanth >> --- >> qemu-img.c | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/qemu-img.c b/qemu-img.c >> index 68b375f..bea9268 100644 >> --- a

Re: [Qemu-devel] [PATCH 1/3] s390x/css: unrestrict cssids

On Mon, 4 Dec 2017 16:02:14 +0100 Halil Pasic wrote: > On 12/04/2017 12:10 PM, Cornelia Huck wrote: > > On Fri, 1 Dec 2017 15:31:34 +0100 > > Halil Pasic wrote: > > > >> The default css 0xfe is currently restricted to virtual subchannel > >> devices. The hope when the decision was made was,

Re: [Qemu-devel] [PATCH 2/3] s390x/css: advertise unrestricted cssids

On Mon, 4 Dec 2017 16:07:27 +0100 Halil Pasic wrote: > On 12/04/2017 12:15 PM, Cornelia Huck wrote: > > On Fri, 1 Dec 2017 15:31:35 +0100 > > Halil Pasic wrote: > > > >> Let us advertise the changes introduced by "s390x/css: unrestrict cssids" > >> to the management software (so it can tell

Re: [Qemu-devel] [PATCH 15/25] spapr: notify the CPU when the XIVE interrupt priority is more privileged

On Mon, 2017-12-04 at 12:17 +1100, David Gibson wrote: > On Sat, Dec 02, 2017 at 08:40:58AM -0600, Benjamin Herrenschmidt wrote: > > On Thu, 2017-11-30 at 16:00 +1100, David Gibson wrote: > > > > > > > static uint64_t spapr_xive_icp_accept(sPAPRXiveICP *icp) > > > > { > > > > -return 0; > >

Re: [Qemu-devel] [PULL 0/1] baum braille device update

Peter Maydell, on lun. 04 déc. 2017 15:36:32 +, wrote: > On 4 December 2017 at 15:26, Samuel Thibault wrote: > > Peter Maydell, on lun. 04 déc. 2017 15:21:48 +, wrote: > >> On 4 December 2017 at 15:17, Samuel Thibault > >> wrote: > >> >

Re: [Qemu-devel] [PATCH 3/3] s390x: deprecate s390-squash-mcss machine prop

On Mon, 4 Dec 2017 16:32:16 +0100 Halil Pasic wrote: > On 12/04/2017 12:28 PM, Cornelia Huck wrote: > > On Fri, 1 Dec 2017 15:31:36 +0100 > > Halil Pasic wrote: > >> diff --git a/hw/s390x/s390-virtio-ccw.c b/hw/s390x/s390-virtio-ccw.c > >> index 4d65a50334..3796f666e6 100644 > >> --- a/hw/s390

Re: [Qemu-devel] [PATCH 2/3] s390x/css: advertise unrestricted cssids

On 12/04/2017 05:07 PM, Cornelia Huck wrote: > On Mon, 4 Dec 2017 16:07:27 +0100 > Halil Pasic wrote: > >> On 12/04/2017 12:15 PM, Cornelia Huck wrote: >>> On Fri, 1 Dec 2017 15:31:35 +0100 >>> Halil Pasic wrote: >>> Let us advertise the changes introduced by "s390x/css: unrestrict cs

Re: [Qemu-devel] [PATCH 20/25] spapr: add device tree support for the XIVE interrupt mode

On 12/04/2017 08:49 AM, David Gibson wrote: > On Thu, Nov 23, 2017 at 02:29:50PM +0100, Cédric Le Goater wrote: >> The XIVE interface for the guest is described in the device tree under >> the "interrupt-controller" node. A couple of new properties are >> specific to XIVE : >> >> - "reg" >> >>

Re: [Qemu-devel] [PATCH 13/25] spapr: introduce the XIVE Event Queues

On 12/04/2017 02:09 AM, David Gibson wrote: > On Fri, Dec 01, 2017 at 05:36:39PM +0100, Cédric Le Goater wrote: >> On 12/01/2017 12:35 AM, David Gibson wrote: >>> On Thu, Nov 30, 2017 at 02:06:27PM +, Cédric Le Goater wrote: On 11/30/2017 04:38 AM, David Gibson wrote: > On Thu, Nov 23,

Re: [Qemu-devel] [PATCH v7 for-2.12 21/25] block: Purify .bdrv_refresh_filename()

On Mon 20 Nov 2017 09:10:00 PM CET, Max Reitz wrote: > -static void blkdebug_refresh_filename(BlockDriverState *bs, QDict *options) > +static void blkdebug_refresh_filename(BlockDriverState *bs) > { > BDRVBlkdebugState *s = bs->opaque; > -QDict *opts; > const QDictEntry *e; > -bo

Re: [Qemu-devel] [PATCH v7 for-2.12 22/25] block: Do not copy exact_filename from format file

On Mon 20 Nov 2017 09:10:01 PM CET, Max Reitz wrote: > If the a format BDS's file BDS is in turn a format BDS, we cannot simply > use the same filename, because when opening a BDS tree based on a > filename alone, qemu will create only one format node on top of one > protocol node (disregarding a p

Re: [Qemu-devel] [qemu-s390x] [PATCH RFC 2/2] s390x: attach autogenerated nics

On Mon, 4 Dec 2017 12:17:06 +0100 Christian Borntraeger wrote: > On 11/28/2017 02:46 PM, Cornelia Huck wrote: > > The autogenerated nics should be treated as any other device; use > > qdev_set_id() to have them show up under peripheral-anon. > > > I think this is fine, but then I ask myself ho

Re: [Qemu-devel] [PATCH v7 for-2.12 25/25] block/null: Generate filename even with latency-ns

On Mon 20 Nov 2017 09:10:04 PM CET, Max Reitz wrote: > While we cannot represent the latency-ns option in a filename, it is not > a significant option so not being able to should not stop us from > generating a filename nonetheless. > > Signed-off-by: Max Reitz Reviewed-by: Alberto Garcia Berto

Re: [Qemu-devel] [PATCH RFC 0/2] s390x: cut down on unattached devices

On Mon, 4 Dec 2017 15:47:37 +0100 Halil Pasic wrote: > On 12/04/2017 10:22 AM, Cornelia Huck wrote: > > On Fri, 1 Dec 2017 15:41:21 +0100 > > Halil Pasic wrote: > > > >> On 11/28/2017 04:21 PM, Halil Pasic wrote: > >> [..] > > Otherwise at first glance both patches seem sane. >

Re: [Qemu-devel] [PATCH v7 for-2.12 24/25] block/curl: Implement bdrv_refresh_filename()

On Mon 20 Nov 2017 09:10:03 PM CET, Max Reitz wrote: > Signed-off-by: Max Reitz > --- > block/curl.c | 18 ++ > 1 file changed, 18 insertions(+) > > diff --git a/block/curl.c b/block/curl.c > index 11318a9a29..fe57223fda 100644 > --- a/block/curl.c > +++ b/block/curl.c > @@ -957,6

Re: [Qemu-devel] [PATCH v7 for-2.12 20/25] block: Generically refresh runtime options

On Mon 20 Nov 2017 09:09:59 PM CET, Max Reitz wrote: > Instead of having every block driver which implements > bdrv_refresh_filename() copy all of the significant runtime options over > to bs->full_open_options, implement this process generically in > bdrv_refresh_filename(). > > This patch only ad

  1   2   3   >