[Qemu-devel] some ROMs questions

In the recent 2.12-rc1 tarball, there are the following things present: roms/u-boot-sam460ex/tools/updater/stubs.c - it is some strange symlink pointing to a strange place, probably should be removed? When making u-boot-am460ex image, in roms/Makefile, we do a plain copy, while 5 lines above,

Re: [Qemu-devel] [PATCH v2] i386: add KnightsMill cpu model

Ping ;-) Regards, Boqun On Tue, Mar 20, 2018 at 08:08:15AM +0800, Boqun Feng wrote: > A new cpu model called "KnightsMill" is added to model Knights Mill > processors. Compared to "Skylake-Server" cpu model, the following > features are added: > > avx512_4vnniw avx512_4fmaps avx512pf

Re: [Qemu-devel] [PATCH] e1000e: Do not auto-clear ICR bits which aren't set in EIAC

Hi, This series failed docker-mingw@fedora build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. Type: series Message-id: 267f42a5-b7ce-379e-ffd1-f2611393d...@web.de Subject: [Qemu-devel] [PATCH] e1000e: Do not

Re: [Qemu-devel] [PATCH v2 04/10] migration: detect compression and decompression errors

On Fri, Mar 30, 2018 at 11:11:27AM +0800, Xiao Guangrong wrote: > > > On 03/29/2018 12:25 PM, Peter Xu wrote: > > On Thu, Mar 29, 2018 at 11:51:03AM +0800, Xiao Guangrong wrote: > > > > > > > > > On 03/28/2018 05:59 PM, Peter Xu wrote: > > > > On Tue, Mar 27, 2018 at 05:10:37PM +0800,

[Qemu-devel] [PATCH] scsi-block: Handle error from host devices

The callback of blk_aio_ioctl is not sensible to SCSI errors, so werror=stop doesn't work if ioctl returns 0 but the scsi status is error. Peek at the sg_io_hdr_t fields and amend ret to fix that. Signed-off-by: Fam Zheng --- hw/scsi/scsi-disk.c | 20 +++- 1

Re: [Qemu-devel] [RFC] About 9pfs support "O_DIRECT + aio"?

On 30/03/2018 10:53, jiangyiwen wrote: > Currently, I found virtio-9p in VirtFS don't support "O_DIRECT + aio" > mode, both v9fs and qemu. So when user use "O_DIRECT + aio" mode and > increase iodepths, they can't get higher IOPS. > > I want to know why v9fs don't implement this mode? And I will

Re: [Qemu-devel] [qemu-web PATCH] download: Add instructions for MacPorts

On 01/04/2018 18:22, Rainer Müller wrote: > Signed-off-by: Rainer Müller > --- > _download/macos.md | 6 +- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/_download/macos.md b/_download/macos.md > index dbb312c..06aa811 100644 > ---

Re: [Qemu-devel] Debugging on HAXM

On 01/04/2018 17:35, Alexandro Sanchez Bach wrote: > > I've noticed that `gdb_breakpoint_insert` only considers KVM so far. My > question is: Has anyone planned adding debugging support to HAXM? Or is > anyone actively working on QEMU's HAXM frontend at all? If not, I would like > to work on it

Re: [Qemu-devel] [PATCH v4 5/8] migration/ram: ensure write persistence on loading zero pages to PMEM

On 03/29/18 19:59 +0100, Dr. David Alan Gilbert wrote: > * Haozhong Zhang (haozhong.zh...@intel.com) wrote: > > When loading a zero page, check whether it will be loaded to > > persistent memory If yes, load it by libpmem function > > pmem_memset_nodrain(). Combined with a call to pmem_drain() at

Re: [Qemu-devel] [PATCH v4 0/8] nvdimm: guarantee persistence of QEMU writes to persistent memory

On 03/29/18 20:12 +0100, Dr. David Alan Gilbert wrote: > * Haozhong Zhang (haozhong.zh...@intel.com) wrote: > > > > > Post-copy with NVDIMM currently fails with message "Postcopy on shared > > RAM (...) is not yet supported". Is it enough? > > What does it say now that postcopy-shared support

Re: [Qemu-devel] [PATCH v2] target/xtensa: linux-user: fix sysv IPC structures

Hi, This series failed docker-quick@centos6 build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. Type: series Message-id: 20180401203640.31617-1-jcmvb...@gmail.com Subject: [Qemu-devel] [PATCH v2]

Re: [Qemu-devel] [RFC 00/18] QEMU validator: A method to specify QEMU crash-test cases

[/var]/tmp full due to some jobs not cleaning well their workspaces? On 03/31/2018 06:04 AM, no-re...@patchew.org wrote: > Hi, > > This series failed docker-build@min-glib build test. Please find the testing > commands and > their output below. If you have Docker installed, you can probably

Re: [Qemu-devel] [PATCH] build: Silence dtc directory creation

On 04/01/2018 08:23 AM, Jan Kiszka wrote: > From: Jan Kiszka > > Align with other mkdir calls. > > Signed-off-by: Jan Kiszka Reviewed-by: Philippe Mathieu-Daudé > --- > Makefile | 2 +- > 1 file changed, 1 insertion(+), 1

Re: [Qemu-devel] [PATCH] target/xtensa: linux-user: fix fadvise64 call

Hi, This series failed docker-quick@centos6 build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. Type: series Message-id: 20180401221253.1382-1-jcmvb...@gmail.com Subject: [Qemu-devel] [PATCH] target/xtensa:

[Qemu-devel] [PATCH] target/xtensa: linux-user: fix fadvise64 call

fadvise64_64 on xtensa passes advice as the second argument and so must be handled similar to PPC. This fixes glibc testsuite tests posix/tst-posix_fadvise and posix/tst-posix_fadvise64. Signed-off-by: Max Filippov --- linux-user/syscall.c | 2 +- 1 file changed, 1

Re: [Qemu-devel] [PATCH] e1000e: Do not auto-clear ICR bits which aren't set in EIAC

Hi, This series failed docker-build@min-glib build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. Type: series Message-id: 267f42a5-b7ce-379e-ffd1-f2611393d...@web.de Subject: [Qemu-devel] [PATCH] e1000e: Do

Re: [Qemu-devel] [PATCH] e1000e: Prevent MSI/MSI-X storms

Hi, This series failed docker-quick@centos6 build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. Type: series Message-id: 79199357-38dc-4a2a-6e67-e80235448...@web.de Subject: [Qemu-devel] [PATCH] e1000e:

[Qemu-devel] Debugging on HAXM

Hello, A bit of context: I'm working on a QEMU fork adding support for PlayStation 4 hardware. It's still in development and debugging kernel drivers has become everyday work. While TCG supports debugging, it cannot handle various extensions like AVX/AVX2 that are extensively used by the guest

[Qemu-devel] [PATCH] target/i386: Fix andn instruction

In commit 7073fbada733c8d10992f00772c9b9299d740e9b, the `andn` instruction was implemented via `tcg_gen_andc` but passes the operands in the wrong order: - X86 defines `andn dest,src1,src2` as: dest = ~src1 & src2 - TCG defines `andc dest,src1,src2` as: dest = src1 & ~src2 I have also attached a

[Qemu-devel] [qemu-web PATCH] download: Add instructions for MacPorts

Signed-off-by: Rainer Müller --- _download/macos.md | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/_download/macos.md b/_download/macos.md index dbb312c..06aa811 100644 --- a/_download/macos.md +++ b/_download/macos.md @@ -1,6 +1,10 @@ -QEMU can be

Re: [Qemu-devel] [PATCH] e1000e: Prevent MSI/MSI-X storms

Hi, This series failed docker-mingw@fedora build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. Type: series Message-id: 79199357-38dc-4a2a-6e67-e80235448...@web.de Subject: [Qemu-devel] [PATCH] e1000e: Prevent

[Qemu-devel] [PATCH] e1000e: Prevent MSI/MSI-X storms

From: Jan Kiszka Only signal MSI/MSI-X events on rising edges. So far we re-triggered the interrupt sources even if the guest did no consumed the pending one, easily causing interrupt storms. Issue was observable with Linux 4.16 e1000e driver when MSI-X was used. Vector

[Qemu-devel] [PATCH] e1000e: Do not auto-clear ICR bits which aren't set in EIAC

From: Jan Kiszka The spec does not justify clearing of any E1000_ICR_OTHER_CAUSES when E1000_ICR_OTHER is set in EIAC. In fact, removing this code fixes the issue the Linux driver runs into since 4aea7a5c5e94 ("e1000e: Avoid receiver overrun interrupt bursts") and was

Re: [Qemu-devel] [PATCH] linux-user: fix error propagation in clock_gettime

Le 01/04/2018 à 23:05, Laurent Vivier a écrit : > Le 01/04/2018 à 22:37, Max Filippov a écrit : >> host_to_target_timespec may return error if target address could not be >> locked, but it is ignored. >> Propagate return value of host_to_target_timespec to the caller of >> clock_gettime. >> >>

Re: [Qemu-devel] [PATCH] linux-user: fix alpha signal emulation

Hi, This series failed docker-build@min-glib build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. Type: series Message-id: 20180401204653.14211-1-laur...@vivier.eu Subject: [Qemu-devel] [PATCH] linux-user: fix

Re: [Qemu-devel] [PATCH] linux-user: fix alpha signal emulation

Hi, This series failed docker-quick@centos6 build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. Type: series Message-id: 20180401204653.14211-1-laur...@vivier.eu Subject: [Qemu-devel] [PATCH] linux-user: fix

Re: [Qemu-devel] [PATCH] linux-user: implement clock_settime

Hi, This series failed docker-build@min-glib build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. Type: series Message-id: 20180401203811.31714-1-jcmvb...@gmail.com Subject: [Qemu-devel] [PATCH] linux-user:

Re: [Qemu-devel] [PATCH] linux-user: fix error propagation in clock_gettime

Le 01/04/2018 à 22:37, Max Filippov a écrit : > host_to_target_timespec may return error if target address could not be > locked, but it is ignored. > Propagate return value of host_to_target_timespec to the caller of > clock_gettime. > > Signed-off-by: Max Filippov > --- >

Re: [Qemu-devel] [PATCH] linux-user: fix alpha signal emulation

Hi, This series failed docker-mingw@fedora build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. Type: series Message-id: 20180401204653.14211-1-laur...@vivier.eu Subject: [Qemu-devel] [PATCH] linux-user: fix

Re: [Qemu-devel] [PATCH v2] target/xtensa: linux-user: fix sysv IPC structures

Le 01/04/2018 à 22:36, Max Filippov a écrit : > - make target_ipc_perm fields match kernel definitions for xtensa; > - add target_semid64_ds with proper order of times and reserved fields > for little/big endian specific for xtensa; > - add missing reserved fields after time fields to the

Re: [Qemu-devel] [PATCH] linux-user: implement clock_settime

Hi, This series failed docker-mingw@fedora build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. Type: series Message-id: 20180401203811.31714-1-jcmvb...@gmail.com Subject: [Qemu-devel] [PATCH] linux-user:

Re: [Qemu-devel] [PATCH] linux-user: fix error propagation in clock_gettime

Hi, This series failed docker-mingw@fedora build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. Type: series Message-id: 20180401203739.31670-1-jcmvb...@gmail.com Subject: [Qemu-devel] [PATCH] linux-user: fix

[Qemu-devel] [PATCH] linux-user: fix alpha signal emulation

setup_frame() doesn't set correctly the address of the trampoline code. The offset of retcode array must be added to the stack frame address. Signed-off-by: Laurent Vivier --- linux-user/signal.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[Qemu-devel] [PATCH] linux-user: implement clock_settime

This fixes glibc testsuite test rt/tst-clock2. Signed-off-by: Max Filippov --- linux-user/syscall.c | 12 1 file changed, 12 insertions(+) diff --git a/linux-user/syscall.c b/linux-user/syscall.c index 52e2f9c16479..924fd68efcdd 100644 ---

[Qemu-devel] [PATCH] linux-user: fix error propagation in clock_gettime

host_to_target_timespec may return error if target address could not be locked, but it is ignored. Propagate return value of host_to_target_timespec to the caller of clock_gettime. Signed-off-by: Max Filippov --- linux-user/syscall.c | 2 +- 1 file changed, 1 insertion(+), 1

[Qemu-devel] [PATCH v2] target/xtensa: linux-user: fix sysv IPC structures

- make target_ipc_perm fields match kernel definitions for xtensa; - add target_semid64_ds with proper order of times and reserved fields for little/big endian specific for xtensa; - add missing reserved fields after time fields to the target_shmid_ds; - fix types of shm_cpid, shm_lpid and

Re: [Qemu-devel] [PATCH] target/xtensa: linux-user: fix sysv IPC structures

On Sun, Apr 1, 2018 at 12:57 PM, Laurent Vivier wrote: > Le 01/04/2018 à 21:24, Max Filippov a écrit : >> struct target_shmid_ds { >> struct target_ipc_perm shm_perm;/* operation permission struct */ >> -abi_int shm_segsz; /* size of segment in

Re: [Qemu-devel] [PATCH] target/xtensa: linux-user: fix sysv IPC structures

Le 01/04/2018 à 21:24, Max Filippov a écrit : > - make target_ipc_perm fields match kernel definitions for xtensa; > - add target_semid64_ds with proper order of times and reserved fields > for little/big endian specific for xtensa; > - fix order of times and reserved fields of target_shmid_ds

Re: [Qemu-devel] [PATCH] target/xtensa: linux-user: fix sysv IPC structures

Hi, This series failed docker-mingw@fedora build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. Type: series Message-id: 20180401192421.29712-1-jcmvb...@gmail.com Subject: [Qemu-devel] [PATCH] target/xtensa:

[Qemu-devel] [PATCH] target/xtensa: linux-user: fix sysv IPC structures

- make target_ipc_perm fields match kernel definitions for xtensa; - add target_semid64_ds with proper order of times and reserved fields for little/big endian specific for xtensa; - fix order of times and reserved fields of target_shmid_ds for little/big endian; - fix types of shm_cpid,

Re: [Qemu-devel] [PULL 0/1] RISC-V: Critical fixes for QEMU 2.12

On Fri, Mar 30, 2018 at 10:08:23AM -0700, Michael Clark wrote: > Hi Peter, > > I had tested Richard's proper fix but we didn't have a PR or the required > Reviewed-by and Signed-off-by so I made the PR for the conservative fix, "Richard" is me or Richard Henderson? Anyway if you meant Stefan

[Qemu-devel] [PATCH] build: Silence dtc directory creation

From: Jan Kiszka Align with other mkdir calls. Signed-off-by: Jan Kiszka --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 727ef118f3..fc6f21001f 100644 --- a/Makefile +++ b/Makefile @@

Re: [Qemu-devel] [PATCH V3] migration: add capability to bypass the shared memory

Hi, This series seems to have some coding style problems. See output below for more information: Type: series Message-id: 20180401084848.36725-1-jiangshan...@gmail.com Subject: [Qemu-devel] [PATCH V3] migration: add capability to bypass the shared memory === TEST SCRIPT BEGIN === #!/bin/bash

Re: [Qemu-devel] [PATCH V3] migration: add capability to bypass the shared memory

Hi, This series failed docker-mingw@fedora build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. Type: series Message-id: 20180401084848.36725-1-jiangshan...@gmail.com Subject: [Qemu-devel] [PATCH V3] migration:

[Qemu-devel] [PATCH V3] migration: add capability to bypass the shared memory

1) What's this When the migration capability 'bypass-shared-memory' is set, the shared memory will be bypassed when migration. It is the key feature to enable several excellent features for the qemu, such as qemu-local-migration, qemu-live-update, extremely-fast-save-restore, vm-template,

[Qemu-devel] [PATCH] migration: calculate expected_downtime with ram_bytes_remaining()

expected_downtime value is not accurate with dirty_pages_rate * page_size, using ram_bytes_remaining would yeild it correct. Signed-off-by: Balamuruhan S --- migration/migration.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git