[Qemu-devel] [PATCH for-2.11 2/3] qemu-iotests: remove file cleanup from bash tests

All files for a given test are now self-contained in a subdirectory, and therefore the "./check" script can do all file-related cleanup without any help. This removes file cleanups from the bash tests. The only cleanup left is whatever is needed to kill any spawned processes; e.g. _cleanup_qemu.

[Qemu-devel] [PATCH for-2.11 3/3] qemu-iotests: add option to save temp files on error

Now that ./check takes care of cleaning up after each tests, it can also selectively not clean up. Add option to leave all output from tests intact if that test encountered an error. Note: this currently only works for bash tests, as the python tests still clean up after themselves manually.

[Qemu-devel] [PATCH for-2.11 0/3] qemu-iotests: place output in unique dir

This series does 2 things: 1.) Sets TEST_DIR to a unique subdirectory for each test 2.) Has './check' be responsible for removing temporary files 3.) Add option to './check' to retain temporary files in case of error A caveat is #3 is working currently only for Bash tests, as the Python tests

[Qemu-devel] [PATCH for-2.11 1/3] qemu-iotests: set TEST_DIR to a unique dir for each test

Right now, all qemu-iotests output data into the same scratch directory, and so each tests needs to be responsible for cleanup up its own files. Have each test use 'scratch/$seq' as its temp directory, so the check script can do simple cleanup of removing the whole temporary directory.

[Qemu-devel] [PULL 0/2] ppc-for-2.10 queue 20170731

The following changes since commit a588c4985eff363154d65aee8607d0a4601655f7: Merge remote-tracking branch 'remotes/ericb/tags/pull-nbd-2017-07-28' into staging (2017-07-28 18:17:44 +0100) are available in the git repository at: git://github.com/dgibson/qemu.git tags/ppc-for-2.10-20170731

[Qemu-devel] [PULL 2/2] Revert "spapr: populate device tree depending on XIVE_EXPLOIT option"

This reverts commit b87680427e8a3ff682f66514e99a8344e7437247. I thought this was a harmless preliminary for XIVE enablement patches we expect later on. However, due to some subtle interactions between qemu and SLOF (guest firmware) this breaks some things. Revert it for now, we'll work out how

[Qemu-devel] [PULL 1/2] spapr_drc: fix realize and unrealize

From: Greg Kurz If object_property_add_alias() returns an error in realize(), we should propagate it to the caller and certainly not unref the DRC. Same thing goes for unrealize(). Since object_property_del() is the last call, we can even get rid of the intermediate Error *.

Re: [Qemu-devel] [PATCH 3/3] s390x/css: generate channel path initialized CRW for channel path hotplug

* Cornelia Huck [2017-07-27 13:59:10 +0200]: > On Thu, 27 Jul 2017 03:54:18 +0200 > Dong Jia Shi wrote: > > > When a channel path is hot plugged into a CSS, we should generate > > a channel path initialized CRW (channel report word). The current

Re: [Qemu-devel] [for-2.11 PATCH 18/26] spapr: create DR connectors for PHBs

On Fri, Jul 28, 2017 at 12:30:35PM +0200, Greg Kurz wrote: > On Fri, 28 Jul 2017 13:49:25 +1000 > David Gibson wrote: > > > On Tue, Jul 25, 2017 at 08:01:50PM +0200, Greg Kurz wrote: > > > From: Michael Roth > > > > > > Signed-off-by:

Re: [Qemu-devel] [PATCH 3/3] s390x/css: generate channel path initialized CRW for channel path hotplug

* Cornelia Huck [2017-07-28 14:58:19 +0200]: [...] > > > > If I understand you correctly it ain't possible to handle these > > in the host (and let the guest a simple 'non-real' virtual > > channel path whose reliability depends on what the host does), > > or? > > It is

Re: [Qemu-devel] [PATCH v8 3/3] migration: add bitmap for received page

On Fri, Jul 28, 2017 at 06:29:20PM +0300, Alexey Perevalov wrote: > On 07/28/2017 10:06 AM, Alexey Perevalov wrote: > >On 07/28/2017 09:57 AM, Peter Xu wrote: > >>On Fri, Jul 28, 2017 at 09:43:28AM +0300, Alexey Perevalov wrote: > >>>On 07/28/2017 07:27 AM, Peter Xu wrote: > On Thu, Jul 27,

Re: [Qemu-devel] [PATCH] 9pfs: include for XATTR_SIZE_MAX

On 30.07.2017 20:23, Peter Maydell wrote: > On 30 July 2017 at 17:51, Kamil Rytarowski wrote: >> On 29.07.2017 21:34, Peter Maydell wrote: >>> On 29 July 2017 at 14:50, Patrick Steinhardt wrote: On Fri, Jul 28, 2017 at 02:20:49PM -0300, Philippe Mathieu-Daudé

Re: [Qemu-devel] How to make ELF headers/symbol sections available for multiboot?

CCing Alex, the original author of load_multiboot(), and Kevin, who touched multiboot code recently. On Fri, Jul 28, 2017 at 02:28:34PM -0700, Anatol Pomozov wrote: > Hi > > I am looking at x86 multiboot code and trying to add "ELF section > header" info feature. This will let target to learn

Re: [Qemu-devel] [PATCH v5 3/6] qemu.py: cleanup message on negative exit code

On Thu, Jul 27, 2017 at 10:21:22AM +0200, Amador Pahim wrote: > On Tue, Jul 25, 2017 at 9:51 PM, Eduardo Habkost wrote: > > On Tue, Jul 25, 2017 at 07:10:11PM +0200, Amador Pahim wrote: > >> The message contains the self._args, which has only part of the > >> options used in

[Qemu-devel] [PATCH v2 2/2] Add more function keys to cocoa.m

Enable the Cocoa front-end to be able to use function keys F16 to F20. Signed-off-by: John Arbuckle --- ui/cocoa.m | 5 + 1 file changed, 5 insertions(+) diff --git a/ui/cocoa.m b/ui/cocoa.m index 93e56d0..edc7a65 100644 --- a/ui/cocoa.m +++ b/ui/cocoa.m @@

[Qemu-devel] [PATCH v2 1/2] Add more function keys to QEMU

There are now keyboards that have 19 function keys. This patch extends QEMU so these function keys can be used. Signed-off-by: John Arbuckle --- qapi-schema.json | 12 +++- ui/input-keymap.c | 9 + 2 files changed, 20 insertions(+), 1 deletion(-)

[Qemu-devel] [PATCH v2 0/2] Add more function keys support

QEMU can only handle up to function key F15. These patches extend QEMU to F24. John Arbuckle (2): Add more function keys to QEMU Add more function keys to cocoa.m qapi-schema.json | 13 - ui/cocoa.m| 5 + ui/input-keymap.c | 9 + 3 files changed, 26

Re: [Qemu-devel] [PATCH] 9pfs: include for XATTR_SIZE_MAX

On 30 July 2017 at 17:51, Kamil Rytarowski wrote: > On 29.07.2017 21:34, Peter Maydell wrote: >> On 29 July 2017 at 14:50, Patrick Steinhardt wrote: >>> On Fri, Jul 28, 2017 at 02:20:49PM -0300, Philippe Mathieu-Daudé wrote: This is likely to break on BSD, but now

Re: [Qemu-devel] [PATCH] 9pfs: include for XATTR_SIZE_MAX

On 29.07.2017 21:34, Peter Maydell wrote: > On 29 July 2017 at 14:50, Patrick Steinhardt wrote: >> On Fri, Jul 28, 2017 at 02:20:49PM -0300, Philippe Mathieu-Daudé wrote: >>> This is likely to break on BSD, but now than patchew has a NetBSD job >>> you can trigger a build RESENDing

Re: [Qemu-devel] [PATCH v12 5/8] virtio-balloon: VIRTIO_BALLOON_F_SG

On Sun, Jul 30, 2017 at 07:18:33PM +0300, Michael S. Tsirkin wrote: > On Sun, Jul 30, 2017 at 05:59:17AM +, Wang, Wei W wrote: > > On Sunday, July 30, 2017 12:23 PM, Michael S. Tsirkin wrote: > > > On Sat, Jul 29, 2017 at 08:47:08PM +0800, Wei Wang wrote: > > > > On 07/29/2017 07:08 AM,

Re: [Qemu-devel] [PATCH v12 5/8] virtio-balloon: VIRTIO_BALLOON_F_SG

On Sun, Jul 30, 2017 at 05:59:17AM +, Wang, Wei W wrote: > On Sunday, July 30, 2017 12:23 PM, Michael S. Tsirkin wrote: > > On Sat, Jul 29, 2017 at 08:47:08PM +0800, Wei Wang wrote: > > > On 07/29/2017 07:08 AM, Michael S. Tsirkin wrote: > > > > On Thu, Jul 27, 2017 at 10:50:11AM +0800, Wei

Re: [Qemu-devel] [PATCH v8 0/5] hypertrace: Lightweight guest-to-QEMU trace channel

Hi, This series seems to have some coding style problems. See output below for more information: Subject: [Qemu-devel] [PATCH v8 0/5] hypertrace: Lightweight guest-to-QEMU trace channel Message-id: 150142369849.12995.11229612194223213120.st...@frigg.lan Type: series === TEST SCRIPT BEGIN ===

[Qemu-devel] [PATCH v8 5/5] hypertrace: Add guest-side user-level library

Provides guest library "libqemu-hypertrace-guest.a" to abstract access to the hypertrace channel. Signed-off-by: Lluís Vilanova --- Makefile |5 + configure |2 hypertrace/guest/Makefile | 30

[Qemu-devel] [PATCH v8 4/5] hypertrace: [softmmu] Add QEMU-side proxy to "guest_hypertrace" event

Uses a virtual device to trigger the hypertrace channel event. Signed-off-by: Lluís Vilanova --- hypertrace/Makefile.objs |4 + hypertrace/softmmu.c | 237 ++ include/hw/pci/pci.h |2 3 files changed, 243

[Qemu-devel] [PATCH v8 3/5] hypertrace: [*-user] Add QEMU-side proxy to "guest_hypertrace" event

QEMU detects when the guest uses 'mmap' on hypertrace's control channel file, and then uses 'mprotect' to detect accesses to it, which are used to trigger tracing event "guest_hypertrace". Signed-off-by: Lluís Vilanova --- Makefile.objs|4 bsd-user/main.c

[Qemu-devel] [PATCH v8 2/5] hypertrace: Add tracing event "guest_hypertrace"

Generates the "guest_hypertrace" event with a user-configurable number of arguments. Signed-off-by: Lluís Vilanova --- Makefile |6 -- Makefile.objs |2 ++ configure | 34 ++ rules.mak |2 +- trace-events |

[Qemu-devel] [PATCH v8 1/5] hypertrace: Add documentation

Signed-off-by: Lluís Vilanova --- docs/devel/tracing.txt |3 + docs/hypertrace.txt| 225 2 files changed, 228 insertions(+) create mode 100644 docs/hypertrace.txt diff --git a/docs/devel/tracing.txt

[Qemu-devel] [PATCH v8 0/5] hypertrace: Lightweight guest-to-QEMU trace channel

The hypertrace channel allows guest code to emit events in QEMU (the host) using its tracing infrastructure (see "docs/trace.txt"). This works in both 'system' and 'user' modes, is architecture-agnostic and introduces minimal noise on the guest. See first commit for a full description, use-cases

Re: [Qemu-devel] [PATCH v7 0/5] hypertrace: Lightweight guest-to-QEMU trace channel

Lluís Vilanova writes: > no-reply writes: >> Hi, >> This series failed build test on FreeBSD host. Please find the details below. >> Subject: [Qemu-devel] [PATCH v7 0/5] hypertrace: Lightweight guest-to-QEMU >> trace channel >> Type: series >> Message-id:

Re: [Qemu-devel] [PATCH v7 0/5] hypertrace: Lightweight guest-to-QEMU trace channel

no-reply writes: > Hi, > This series failed build test on FreeBSD host. Please find the details below. > Subject: [Qemu-devel] [PATCH v7 0/5] hypertrace: Lightweight guest-to-QEMU > trace channel > Type: series > Message-id: 150141363372.9857.9055094189388759132.st...@frigg.lan > === TEST

Re: [Qemu-devel] [PATCH v7 0/5] hypertrace: Lightweight guest-to-QEMU trace channel

no-reply writes: > Hi, > This series seems to have some coding style problems. See output below for > more information: > Subject: [Qemu-devel] [PATCH v7 0/5] hypertrace: Lightweight guest-to-QEMU > trace channel > Message-id: 150141363372.9857.9055094189388759132.st...@frigg.lan > Type:

Re: [Qemu-devel] [PATCH] target-i386 : fix a race condition result to lost INIT

2017-07-31 4:01 GMT+08:00 Peng Hao : > when SMP VM start, AP may lost INIT because of receiving INIT between > kvm_vcpu_ioctl_x86_get/set_vcpu_events. > >vcpu 0 vcpu 1 >kvm_vcpu_ioctl_x86_get_vcpu_events >

Re: [Qemu-devel] [PATCH v7 0/5] hypertrace: Lightweight guest-to-QEMU trace channel

Hi, This series seems to have some coding style problems. See output below for more information: Subject: [Qemu-devel] [PATCH v7 0/5] hypertrace: Lightweight guest-to-QEMU trace channel Message-id: 150141363372.9857.9055094189388759132.st...@frigg.lan Type: series === TEST SCRIPT BEGIN ===

Re: [Qemu-devel] [PATCH v7 0/5] hypertrace: Lightweight guest-to-QEMU trace channel

Hi, This series failed build test on FreeBSD host. Please find the details below. Subject: [Qemu-devel] [PATCH v7 0/5] hypertrace: Lightweight guest-to-QEMU trace channel Type: series Message-id: 150141363372.9857.9055094189388759132.st...@frigg.lan === TEST SCRIPT BEGIN === #!/bin/sh #

[Qemu-devel] [PATCH] target-i386 : fix a race condition result to lost INIT

when SMP VM start, AP may lost INIT because of receiving INIT between kvm_vcpu_ioctl_x86_get/set_vcpu_events. vcpu 0 vcpu 1 kvm_vcpu_ioctl_x86_get_vcpu_events events->smi.latched_init=0 send INIT

[Qemu-devel] [PATCH v7 5/5] hypertrace: Add guest-side user-level library

Provides guest library "libqemu-hypertrace-guest.a" to abstract access to the hypertrace channel. Signed-off-by: Lluís Vilanova --- Makefile |5 + configure |2 hypertrace/guest/Makefile | 30

[Qemu-devel] [PATCH v7 4/5] hypertrace: [softmmu] Add QEMU-side proxy to "guest_hypertrace" event

Uses a virtual device to trigger the hypertrace channel event. Signed-off-by: Lluís Vilanova --- hypertrace/Makefile.objs |4 + hypertrace/softmmu.c | 237 ++ include/hw/pci/pci.h |2 3 files changed, 243

[Qemu-devel] [PATCH v7 3/5] hypertrace: [*-user] Add QEMU-side proxy to "guest_hypertrace" event

QEMU detects when the guest uses 'mmap' on hypertrace's control channel file, and then uses 'mprotect' to detect accesses to it, which are used to trigger tracing event "guest_hypertrace". Signed-off-by: Lluís Vilanova --- Makefile.objs|4 bsd-user/main.c

[Qemu-devel] [PATCH v7 2/5] hypertrace: Add tracing event "guest_hypertrace"

Generates the "guest_hypertrace" event with a user-configurable number of arguments. Signed-off-by: Lluís Vilanova --- Makefile |6 -- Makefile.objs |2 ++ configure | 34 ++ rules.mak |2 +- trace-events |

[Qemu-devel] [PATCH v7 1/5] hypertrace: Add documentation

Signed-off-by: Lluís Vilanova --- docs/devel/tracing.txt |3 + docs/hypertrace.txt| 225 2 files changed, 228 insertions(+) create mode 100644 docs/hypertrace.txt diff --git a/docs/devel/tracing.txt

[Qemu-devel] [PATCH v7 0/5] hypertrace: Lightweight guest-to-QEMU trace channel

The hypertrace channel allows guest code to emit events in QEMU (the host) using its tracing infrastructure (see "docs/trace.txt"). This works in both 'system' and 'user' modes, is architecture-agnostic and introduces minimal noise on the guest. See first commit for a full description, use-cases