Re: [Qemu-devel] [PATCH v2 0/2] hw/i386: Update FADT to Revision 3 (ACPI 2.0)

Hi, This series failed automatic build test. Please find the testing commands and their output below. If you have docker installed, you can probably reproduce it locally. Type: series Subject: [Qemu-devel] [PATCH v2 0/2] hw/i386: Update FADT to Revision 3 (ACPI 2.0) Message-id:

[Qemu-devel] [PATCH v2 2/2] hw/i386: Build-time assertion on pc/q35 reset register being identical.

This adds a clarifying comment and build time assert to the FADT reset register field initialisation: the reset register is the same on both machine types. Signed-off-by: Phil Dennis-Jordan --- hw/i386/acpi-build.c | 3 +++ hw/pci-host/piix.c | 6 --

[Qemu-devel] [PATCH v2 1/2] hw/i386: Use Rev3 FADT (ACPI 2.0) instead of Rev1 to improve guest OS support.

This updates the FADT generated for x86/64 machine types from Revision 1 to 3. (Based on ACPI standard 2.0 instead of 1.0) The intention is to expose the reset register information to guest operating systems which require it, specifically OS X/macOS. Revision 1 FADTs do not contain the fields

[Qemu-devel] [PATCH v2 0/2] hw/i386: Update FADT to Revision 3 (ACPI 2.0)

This updates the FADT generated for x86/64 machine types from Revision 1 to 3. (Based on ACPI standard 2.0 instead of 1.0) As previously, the goal is to make running macOS/OS X guests smoother. With a Rev1 FADT, rebooting such a guest doesn't work, as the OS uses the reset register information

[Qemu-devel] [PATCH Risu v2 0/3] PPC64 Improvements

On Mar 9, 2017, at 3:08 PM, qemu-devel-requ...@nongnu.org wrote: v2: - applied code review This patchset include initial support to PPC64 (Big-Endian), that is pretty much the same: only some fixes in configure and risugen. Also, it adds a better random initialization of VSX registers.

[Qemu-devel] Risu and the PowerPC 970

Does Risu support the PowerPC 970? I tried compiling it but I saw this error: gcc -Wall -D_GNU_SOURCE -DARCH=ppc64 -g -o risu.o -c risu.c In file included from risu.c:29: risu.h:27:30: error: risu_reginfo_ppc64.h: No such file or directory make: *** [Makefile:44: risu.o] Error 1 The PowerPC

[Qemu-devel] [Bug 597362] Re: qemu-system-sparc singlestep not work in gdbstub

[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/597362 Title:

Re: [Qemu-devel] [PATCH v7 kernel 3/5] virtio-balloon: implementation of VIRTIO_BALLOON_F_CHUNK_TRANSFER

On Sun, Mar 12, 2017 at 01:59:54AM +, Wang, Wei W wrote: > On 03/11/2017 10:10 PM, Matthew Wilcox wrote: > > On Sat, Mar 11, 2017 at 07:59:31PM +0800, Wei Wang wrote: > > > I'm thinking what if the guest needs to transfer these much physically > > > continuous memory to host:

Re: [Qemu-devel] Incorrect memory region address with large 64-bit PCI BARs

On Sun, Mar 12, 2017 at 03:46:57AM +0200, Michael S. Tsirkin wrote: > On Sat, Mar 11, 2017 at 10:37:09AM +, Mark Cave-Ayland wrote: > > I've been looking at an issue with virtio BARs being mapped incorrectly > > on qemu-system-sparc64, and as part of this investigation found that > > some

Re: [Qemu-devel] [PATCH v7 kernel 3/5] virtio-balloon: implementation of VIRTIO_BALLOON_F_CHUNK_TRANSFER

On 03/11/2017 10:10 PM, Matthew Wilcox wrote: > On Sat, Mar 11, 2017 at 07:59:31PM +0800, Wei Wang wrote: > > I'm thinking what if the guest needs to transfer these much physically > > continuous memory to host: 1GB+2MB+64KB+32KB+16KB+4KB. > > Is it going to use Six 64-bit chunks? Would it be

Re: [Qemu-devel] Incorrect memory region address with large 64-bit PCI BARs

On Sat, Mar 11, 2017 at 10:37:09AM +, Mark Cave-Ayland wrote: > I've been looking at an issue with virtio BARs being mapped incorrectly > on qemu-system-sparc64, and as part of this investigation found that > some 64-bit PCI BAR memory regions don't appear correctly in "info mtree". > > The

Re: [Qemu-devel] [PATCH v7 kernel 3/5] virtio-balloon: implementation of VIRTIO_BALLOON_F_CHUNK_TRANSFER

On Sat, Mar 11, 2017 at 07:59:31PM +0800, Wei Wang wrote: > On 03/11/2017 01:11 AM, Matthew Wilcox wrote: > > On Fri, Mar 10, 2017 at 05:58:28PM +0200, Michael S. Tsirkin wrote: > > > One of the issues of current balloon is the 4k page size > > > assumption. For example if you free a huge page you

Re: [Qemu-devel] [PATCH v7 kernel 3/5] virtio-balloon: implementation of VIRTIO_BALLOON_F_CHUNK_TRANSFER

On Fri, Mar 10, 2017 at 01:25:41PM -0800, Matthew Wilcox wrote: > On Fri, Mar 10, 2017 at 09:35:21PM +0200, Michael S. Tsirkin wrote: > > > bit 0 clear => bits 1-11 encode a page count, bits 12-63 encode a PFN, > > > page size 4k. > > > bit 0 set, bit 1 clear => bits 2-12 encode a page count,

[Qemu-devel] [PATCH] target/xtensa: fix semihosting argc/argv implementation

So far xtensa provides fixed dummy argc/argv for the corresponding semihosting calls. Now that there are semihosting_get_argc and semihosting_get_arg, use them to pass actual command line arguments to guest. Signed-off-by: Max Filippov --- target/xtensa/xtensa-semi.c | 49

[Qemu-devel] [PATCH] target/xtensa: xtfpga: load DTB only when FDT support is enabled

xtensa linux can use DTB but does not require it, so FDT support is not a requirement for target/xtensa. Don't try to load DTB when FDT support is not configured. Signed-off-by: Max Filippov --- hw/xtensa/xtfpga.c | 9 + 1 file changed, 9 insertions(+) diff --git

Re: [Qemu-devel] [PATCH 1/3] linux-user: Restrict usage of sa_restorer

On 03/12/2017 07:02 AM, Richard Henderson wrote: TARGET_ALPHA has KA_RESTORER, not sa_restorer. The restorer value is passed to sigaction in a 5th register argument. Less than handy that qemu doesn't distinguish the two structs... I beg your pardon, we do -- they're just named confusingly.

Re: [Qemu-devel] [PATCH] linux-user: Fix TARGET_MAP* and TARGET_F_??LCK for hppa arch

On 03/12/2017 03:50 AM, Helge Deller wrote: TARGET_MAP_TYPE needs to be 0x03 instead of 0x0f on the hppa architecture, otherwise it conflicts with MAP_FIXED which is 0x04. Add missing TARGET_MAP_STACK and TARGET_MAP_HUGETLB values. Fix TARGET_F_RDLCK, TARGET_F_WRLCK and TARGET_F_UNLCK.

Re: [Qemu-devel] [PATCH] linux-user: Add TARGET_MAP_STACK and TARGET_MAP_HUGETLB for all remaining architectures

On 03/12/2017 04:30 AM, Helge Deller wrote: Add the missing defines and for TARGET_MAP_STACK and TARGET_MAP_HUGETLB for alpha, mips, ppc and x86, and fix the mmap_flags translation table to translate those flags between host and target architecture. Signed-off-by: Helge Deller

Re: [Qemu-devel] [PATCH 1/3] linux-user: Restrict usage of sa_restorer

On 03/12/2017 04:28 AM, Laurent Vivier wrote: Le 11/03/2017 à 04:42, Richard Henderson a écrit : Reading and writing to an sa_restorer member that isn't supposed to exist corrupts user memory. Introduce TARGET_ARCH_HAS_SA_RESTORER, similar to the kernel's __ARCH_HAS_SA_RESTORER. Reported-by:

Re: [Qemu-devel] [PATCH V2] nios2: iic: Convert CPU prop to qom link

On 02/27/2017 08:38 PM, Marek Vasut wrote: > Add a const qom link between the CPU and the IIC instead > of passing the CPU link through a qom property. > > Signed-off-by: Marek Vasut > Cc: Alexander Graf > Cc: Chris Wulff > Cc: Igor Mammedov

Re: [Qemu-devel] [PATCH 04/21] qobject: add quint type

On 03/11/2017 07:22 AM, Marc-André Lureau wrote: > The type is not used at all yet. Add some tests to exercice it. s/exercice/exercise/ I wonder if we need this patch at all. I've been thinking about a possible alternative representation, such that a single QInt type can cover _both_ signed and

Re: [Qemu-devel] [PATCH 12/21] test-qga: drop everything until guest-sync

On 03/11/2017 07:22 AM, Marc-André Lureau wrote: > In the following commits, qemu-ga will emit an event on connect that > a real client should treat or ignore and test-qga can skip. > By the way, I still have a patch pending to fix test-qga:

[Qemu-devel] [PATCH] linux-user: Add missing IP_TOS, IPV6_TCLASS and IPV6_RECVTCLASS sockopts

When running the nslookup or dig command with IPv6, the following qemu warnings will be shown: Unsupported ancillary data: 0/1 Unsupported setsockopt level=41 optname=67 Unsupported setsockopt level=41 optname=66 Unsupported ancillary data: 41/67 This patch adds the missing code to quiet those

Re: [Qemu-devel] [PATCH] linux-user: Add TARGET_MAP_STACK and TARGET_MAP_HUGETLB for all remaining architectures

Hi, This series seems to have some coding style problems. See output below for more information: Type: series Subject: [Qemu-devel] [PATCH] linux-user: Add TARGET_MAP_STACK and TARGET_MAP_HUGETLB for all remaining architectures Message-id: 20170311183016.ga20...@ls3530.fritz.box === TEST

[Qemu-devel] [PATCH] linux-user: Add TARGET_MAP_STACK and TARGET_MAP_HUGETLB for all remaining architectures

Add the missing defines and for TARGET_MAP_STACK and TARGET_MAP_HUGETLB for alpha, mips, ppc and x86, and fix the mmap_flags translation table to translate those flags between host and target architecture. Signed-off-by: Helge Deller diff --git a/linux-user/syscall.c

Re: [Qemu-devel] [PATCH 1/3] linux-user: Restrict usage of sa_restorer

Le 11/03/2017 à 04:42, Richard Henderson a écrit : > Reading and writing to an sa_restorer member that isn't supposed to > exist corrupts user memory. Introduce TARGET_ARCH_HAS_SA_RESTORER, > similar to the kernel's __ARCH_HAS_SA_RESTORER. > > Reported-by: Helge Deller >

[Qemu-devel] [PATCH] linux-user: Fix TARGET_MAP* and TARGET_F_??LCK for hppa arch

TARGET_MAP_TYPE needs to be 0x03 instead of 0x0f on the hppa architecture, otherwise it conflicts with MAP_FIXED which is 0x04. Add missing TARGET_MAP_STACK and TARGET_MAP_HUGETLB values. Fix TARGET_F_RDLCK, TARGET_F_WRLCK and TARGET_F_UNLCK. Signed-off-by: Helge Deller diff

[Qemu-devel] Qemu socket address

Sorry if I'm asking a silly question but why doesn't Qemu support *socket address reuse *when we use remote debugging with gdb with options "-S -s"? Is there a support in the upstream version? I am using Qemu version 2.7.0. Thanks Ashish -- Ashish Kumar Gahlot III year, UG Govt. Engg. College,

Re: [Qemu-devel] [PATCH v1 2/2] reduce qemu's heap Rss size from 12252kB to 2752KB

> > Subpages never have subregions, so the loop never runs. The begin/commit > > pair then becomes: > > > > ++memory_region_transaction_depth; > > --memory_region_transaction_depth; > > if (!memory_region_transaction_depth) { > > if (memory_region_update_pending) { > >

Re: [Qemu-devel] [PATCH v1 1/2] reduce qemu's heap Rss size from 12252kB to 2752KB

- Original Message - > From: "Anthony Xu" > To: "Paolo Bonzini" , "Yang Zhong" > , qemu-devel@nongnu.org > Cc: "Chao P Peng" > Sent: Friday, March 10, 2017 8:30:06 PM > Subject: RE: [PATCH v1 1/2]

Re: [Qemu-devel] Benchmarking linux-user performance

On 11 March 2017 at 03:25, Emilio G. Cota wrote: > On Fri, Mar 10, 2017 at 12:48:31 +0100, Peter Maydell wrote: >> Given the scale on the LHS is from 1.74 to 1.88 my guess is that the >> variation is in large part noise and the major thing is "our fp >> performance is bounded by

Re: [Qemu-devel] [PATCH 00/21] WIP: dump: add kaslr support (for after 2.9)

- Original Message - > Hi, > > Latest linux kernel enabled kaslr to randomize phys/virt memory > addresses. There has been some effort to support kexec/kdump so that > crash utility can still works in case crashed kernel has kaslr > enabled. > > This series aims to provide enough

Re: [Qemu-devel] [PATCH 2/3] linux-user: Fix TARGET_SA_* defines for HPPA

Le 11/03/2017 à 04:42, Richard Henderson a écrit : > From: Helge Deller > > Reported-by: Helge Deller > Signed-off-by: Richard Henderson Reviewed-by: Laurent Vivier > --- > linux-user/syscall_defs.h | 8 > 1 file

Re: [Qemu-devel] [PATCH v7 kernel 3/5] virtio-balloon: implementation of VIRTIO_BALLOON_F_CHUNK_TRANSFER

On Sat, Mar 11, 2017 at 07:59:31PM +0800, Wei Wang wrote: > I'm thinking what if the guest needs to transfer these much physically > continuous > memory to host: 1GB+2MB+64KB+32KB+16KB+4KB. > Is it going to use Six 64-bit chunks? Would it be simpler if we just > use the 128-bit chunk format (we

Re: [Qemu-devel] [PATCH] linux-user/hppa: Fix typo for TARGET_NR_epoll_wait

Le 11/03/2017 à 11:05, Helge Deller a écrit : > This fixes running a dynamically linked nslookup binary on hppa with > LD_BIND_NOW=1. > > Signed-off-by: Helge Deller Reviewed-by: Laurent Vivier > > diff --git a/linux-user/hppa/syscall_nr.h

Re: [Qemu-devel] [PATCH 00/21] WIP: dump: add kaslr support (for after 2.9)

Hi, This series failed automatic build test. Please find the testing commands and their output below. If you have docker installed, you can probably reproduce it locally. Type: series Subject: [Qemu-devel] [PATCH 00/21] WIP: dump: add kaslr support (for after 2.9) Message-id:

[Qemu-devel] [PATCH 15/21] qga: register event emit function

Signed-off-by: Marc-André Lureau --- qga/main.c | 8 1 file changed, 8 insertions(+) diff --git a/qga/main.c b/qga/main.c index 1c39895baa..8e852bd556 100644 --- a/qga/main.c +++ b/qga/main.c @@ -39,6 +39,7 @@ #define CONFIG_FSFREEZE #endif #endif

[Qemu-devel] [PATCH 14/21] qga: add and populate VMDumpInfo

Get various addresses and informations that can be useful for qemu to generate dumps, and provide enough details for KASLR kernels to be exploitable by tools like crash. phys-base: the physical address where the kernel is loaded vmcoreinfo: can be used to read the guest vmcoreinfo ELF note _text:

[Qemu-devel] [PATCH 21/21] scripts/dump-guest-memory.py: add VMCOREINFO

Signed-off-by: Marc-André Lureau --- scripts/dump-guest-memory.py | 52 1 file changed, 52 insertions(+) diff --git a/scripts/dump-guest-memory.py b/scripts/dump-guest-memory.py index f7c6635f15..0ce32b2a3f 100644 ---

[Qemu-devel] [PATCH 18/21] dump: use qga VMDUMP_INFO for ELF dump

Add vmcoreinfo ELF note. NUMBRE(phys_base) in vmcoreinfo has only been recently introduced in Linux 4.10 ("kexec: export the value of phys_base instead of symbol address"). To accomadate for older kernels, modify the vmcoreinfo to add the new fields and help newer crash that will use it.

[Qemu-devel] [PATCH 12/21] test-qga: drop everything until guest-sync

In the following commits, qemu-ga will emit an event on connect that a real client should treat or ignore and test-qga can skip. Signed-off-by: Marc-André Lureau --- tests/test-qga.c | 27 --- 1 file changed, 20 insertions(+), 7 deletions(-)

[Qemu-devel] [PATCH 20/21] scripts/dump-guest-memory.py: fix int128_get64 on recent gcc

The Int128 is no longer a struct, reaching a python exception: Python Exception Attempt to extract a component of a value that is not a (null).: Replace struct access with a cast to uint64 instead. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1427466 Signed-off-by: Marc-André Lureau

[Qemu-devel] [PATCH 17/21] virtio-channel: parse qga stream for VMDUMP_INFO event

On virtio channel "org.qemu.guest_agent.0", parse the json stream until the VMDUMP_INFO is received and retrieve the dump details. Signed-off-by: Marc-André Lureau --- include/sysemu/dump-info.h | 15 + dump.c | 3 +++

[Qemu-devel] [PATCH 16/21] qga: emit VMDUMP_INFO event

When client connects, emit the VMDUMP_INFO. Signed-off-by: Marc-André Lureau --- qga/guest-agent-core.h | 2 ++ qga/channel-posix.c| 11 +++ qga/main.c | 13 + Makefile | 7 ++- qga/Makefile.objs | 1 +

[Qemu-devel] [PATCH 09/21] qdev: use appropriate type

Signed-off-by: Marc-André Lureau --- hw/i386/acpi-build.c | 15 --- hw/pci-host/gpex.c| 2 +- hw/pci-host/q35.c | 2 +- hw/pci-host/xilinx-pcie.c | 2 +- target/i386/cpu.c | 2 +- 5 files changed, 12 insertions(+), 11

[Qemu-devel] [PATCH 19/21] kdump: write vmcoreinfo in header

Signed-off-by: Marc-André Lureau --- dump.c | 48 1 file changed, 44 insertions(+), 4 deletions(-) diff --git a/dump.c b/dump.c index 0ebfb5471a..bf88cb362b 100644 --- a/dump.c +++ b/dump.c @@ -785,8 +785,9 @@ static

[Qemu-devel] [PATCH 11/21] qdict: learn to lookup quint

Since a number may be parsed as an integer if it fits, learn to deal with this situtation and fallback on QInt if QUint failed. There is no need for exact type getters in qemu yet. Signed-off-by: Marc-André Lureau --- include/qapi/qmp/qdict.h | 2 ++

[Qemu-devel] [PATCH 10/21] Use uint property getter/setter where appropriate

All those property usages are associated with unsigned integers, so use appropriate getter/setter. Signed-off-by: Marc-André Lureau --- include/hw/isa/isa.h | 2 +- hw/acpi/memory_hotplug.c | 10 hw/acpi/nvdimm.c | 10

[Qemu-devel] [PATCH 05/21] qapi: update the qobject visitor to use QUInt

Signed-off-by: Marc-André Lureau --- scripts/qapi-visit.py | 3 ++- qapi/qobject-input-visitor.c| 30 -- qapi/qobject-output-visitor.c | 3 +-- tests/test-qobject-input-visitor.c | 15 +++

[Qemu-devel] [PATCH 07/21] object: add uint property setter/getter

Signed-off-by: Marc-André Lureau --- include/qom/object.h | 23 +++ qom/object.c | 32 2 files changed, 55 insertions(+) diff --git a/include/qom/object.h b/include/qom/object.h index

[Qemu-devel] [PATCH 13/21] qga: report error on keyfile dump error

Signed-off-by: Marc-André Lureau Cc:qemu-triv...@nongnu.org --- qga/main.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/qga/main.c b/qga/main.c index 92658bc0e2..beff041340 100644 --- a/qga/main.c +++ b/qga/main.c @@ -1082,7 +1082,12 @@

[Qemu-devel] [PATCH 04/21] qobject: add quint type

The type is not used at all yet. Add some tests to exercice it. Signed-off-by: Marc-André Lureau --- qapi/introspect.json | 2 +- scripts/qapi.py | 28 --- include/qapi/qmp/quint.h | 25

[Qemu-devel] [PATCH 06/21] json: learn to parse uint64 numbers

If the parsed number doesn't fit in a int64, try with a uint64 before falling back to double. Switch strtoll() usage to qemu_strtoi64() helper while at it. Add a few tests for large numbers. Signed-off-by: Marc-André Lureau --- qobject/json-lexer.c | 4

[Qemu-devel] [PATCH 03/21] object: fix potential leak in getters

If the property is not of the requested type, the getters will leak a QObject. Signed-off-by: Marc-André Lureau Cc: qemu-triv...@nongnu.org --- qom/object.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/qom/object.c b/qom/object.c index

[Qemu-devel] [PATCH 08/21] qdev: use int and uint properties

So the correct QObject type is used. Signed-off-by: Marc-André Lureau --- include/hw/qdev-core.h | 5 +++- include/hw/qdev-properties.h | 59 ++-- hw/block/fdc.c | 54

[Qemu-devel] [PATCH 00/21] WIP: dump: add kaslr support (for after 2.9)

Hi, Latest linux kernel enabled kaslr to randomize phys/virt memory addresses. There has been some effort to support kexec/kdump so that crash utility can still works in case crashed kernel has kaslr enabled. This series aims to provide enough information in qemu dumps so that crash utility can

[Qemu-devel] [PATCH 02/21] pci-host: use more specific type names

Use the actual unsigned integer type name (this should't break since property type aren't directly accessed from outside). Signed-off-by: Marc-André Lureau --- hw/pci-host/piix.c | 8 hw/pci-host/q35.c | 10 +- 2 files changed, 9 insertions(+), 9

[Qemu-devel] [PATCH 01/21] qapi: add info comment for generated types

This may help to find where the origin of the type was declared in the json (when greping isn't easy enough). Signed-off-by: Marc-André Lureau Cc: qemu-triv...@nongnu.org --- scripts/qapi.py | 11 +-- scripts/qapi-event.py | 4 +++-

Re: [Qemu-devel] [PATCH v7 kernel 3/5] virtio-balloon: implementation of VIRTIO_BALLOON_F_CHUNK_TRANSFER

On 03/11/2017 01:11 AM, Matthew Wilcox wrote: On Fri, Mar 10, 2017 at 05:58:28PM +0200, Michael S. Tsirkin wrote: One of the issues of current balloon is the 4k page size assumption. For example if you free a huge page you have to split it up and pass 4k chunks to host. Quite often host can't

[Qemu-devel] [PATCH 2/2] vmdk: Update metadata for multiple clusters

Include a next pointer in VmdkMetaData struct to point to the previous allocated L2 table. Modify vmdk_L2update to start updating metadata for allocation of multiple clusters at once. Signed-off-by: Ashijeet Acharya --- block/vmdk.c | 131

[Qemu-devel] [PATCH 0/2] Allocate mutiple clusters for VMDK I/O

This series optimizes the I/O performance of VMDK driver. Patch 1 makes the VMDK driver to allocate multiple clusters at once. Earlier it used to allocate cluster by cluster which slowed down its performance to a great extent. Patch 2 changes the metadata update code to update the L2 tables for

[Qemu-devel] [PATCH 1/2] vmdk: Optimize I/O by allocating multiple clusters

The vmdk driver in block/vmdk.c used to allocate cluster by cluster which slowed down its I/O performance. Make vmdk driver allocate multiple clusters at once to reduce the overhead costs of multiple separate cluster allocation calls. The number of clusters allocated at once depends on the L2

[Qemu-devel] Incorrect memory region address with large 64-bit PCI BARs

I've been looking at an issue with virtio BARs being mapped incorrectly on qemu-system-sparc64, and as part of this investigation found that some 64-bit PCI BAR memory regions don't appear correctly in "info mtree". The easiest way to see this is to launch QEMU as below and then check the output

[Qemu-devel] [PATCH] linux-user/hppa: Fix typo for TARGET_NR_epoll_wait

This fixes running a dynamically linked nslookup binary on hppa with LD_BIND_NOW=1. Signed-off-by: Helge Deller diff --git a/linux-user/hppa/syscall_nr.h b/linux-user/hppa/syscall_nr.h index 0f396fa..55bdf71 100644 --- a/linux-user/hppa/syscall_nr.h +++

Re: [Qemu-devel] [PATCH 2/3] linux-user: Fix TARGET_SA_* defines for HPPA

On 11.03.2017 04:42, Richard Henderson wrote: > From: Helge Deller > > Reported-by: Helge Deller > Signed-off-by: Richard Henderson Signed-off-by: Helge Deller > --- > linux-user/syscall_defs.h | 8 > 1 file changed,