Re: [Qemu-devel] [PATCH] target/m68k: add monitor.c

Le 20/12/2017 à 21:54, Philippe Mathieu-Daudé a écrit : > On Wed, Dec 20, 2017 at 5:35 PM, Laurent Vivier wrote: >> This allows to use registers content in the monitor. >> >> Example: >> >> BEFORE: >> (qemu) print $d0 >> unknown register >> >> AFTER: >> (qemu) print $d0

Re: [Qemu-devel] [PATCH] target/m68k: add monitor.c

Le 20/12/2017 à 22:22, Thomas Huth a écrit : > Am Wed, 20 Dec 2017 21:35:28 +0100 > schrieb Laurent Vivier : > >> This allows to use registers content in the monitor. >> >> Example: >> >> BEFORE: >> (qemu) print $d0 >> unknown register >> >> AFTER: >> (qemu) print $d0

Re: [Qemu-devel] [PATCH V2 0/5] hw/pvrdma: PVRDMA device implementation

> > > > > What happens if guest attempts to register all its memory? > > > > > > > Then we loose, is not different from bare metal, reg_mr will pin all the > > RAM. > > We need to find a way to communicate to guests about amount > of memory they can pin. dev_caps.max_mr_size is the way

Re: [Qemu-devel] [Qemu-block] [PATCH 0/3] block: Deprecated options

On 20.12.2017 22:40, John Snow wrote: > > > On 12/18/2017 12:14 PM, Thomas Huth wrote: >> Remove the deprecated "-drive boot" and "-hdachs" options and properly >> mark some other deprecated options in the deprecation chapter. >> >> Thomas Huth (3): >> block: Remove the obsolete -drive

[Qemu-devel] [PATCH] intel_iommu: a fix to vtd_dev_get_trans_type()

vtd_ce_get_type() returns uin32_t and vtd_dev_get_trans_type() returns the value from vtd_ce_get_type(). However, vtd_dev_get_trans_type() returns int. This patch switchs to return the translation type by parameter. It avoids unsigned to int transfer and also avoid potential reading confusion.

Re: [Qemu-devel] [PATCH V3] vl.c && linux-user/main.c : removed **envp from main() arguments

Hi, This series seems to have some coding style problems. See output below for more information: Type: series Message-id: 20171219101122.31711-1-ybet...@redhat.com Subject: [Qemu-devel] [PATCH V3] vl.c && linux-user/main.c : removed **envp from main() arguments === TEST SCRIPT BEGIN ===

Re: [Qemu-devel] [RFC v6 09/27] monitor: create monitor dedicate iothread

On Tue, 12/19 16:45, Peter Xu wrote: > 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 | 29 + > 1 file changed, 29 insertions(+) >

Re: [Qemu-devel] [PATCH 0/4] cryptodev: add vhost support

On Thu, Dec 21, 2017 at 12:51:12AM +, Gonglei (Arei) wrote: > > > > -Original Message- > > From: Michael S. Tsirkin [mailto:m...@redhat.com] > > Sent: Thursday, December 21, 2017 1:39 AM > > To: Gonglei (Arei) > > Cc: qemu-devel@nongnu.org; pbonz...@redhat.com; Huangweidong (C); > >

Re: [Qemu-devel] [PATCH 0/3] Vhost: no more leak QEMU virtual addresses to user backend

On Wed, Dec 20, 2017 at 04:07:41PM +, Stefan Hajnoczi wrote: > On Tue, Dec 19, 2017 at 07:11:26PM +0100, Maxime Coquelin wrote: > > Before this series, QEMU process virtual addresses are sent to the > > user backend as user addresses. > > > > Passing these virtual addresses aren't useful, as

Re: [Qemu-devel] [PULL 02/46] qemu-thread: fix races on threads that exit very quickly

> -邮件原件- > 发件人: Eric Blake [mailto:ebl...@redhat.com] > 发送时间: 2017年12月21日 11:36 > 收件人: linzhecheng ; Paolo Bonzini > ; qemu-devel@nongnu.org; f...@redhat.com > 抄送: wangxin (U) > 主题: Re: [Qemu-devel] [PULL 02/46]

Re: [Qemu-devel] [PULL 02/46] qemu-thread: fix races on threads that exit very quickly

On 12/20/2017 09:29 PM, linzhecheng wrote: +} QemuThreadArgs; + +static void *qemu_thread_start(void *args) { +QemuThreadArgs *qemu_thread_args = args; +void *(*start_routine)(void *) = qemu_thread_args->start_routine; +void *arg = qemu_thread_args->arg; + +/* Attempt to set the

Re: [Qemu-devel] [PULL 02/46] qemu-thread: fix races on threads that exit very quickly

> -邮件原件- > 发件人: Paolo Bonzini [mailto:paolo.bonz...@gmail.com] 代表 Paolo Bonzini > 发送时间: 2017年12月21日 1:14 > 收件人: qemu-devel@nongnu.org > 抄送: linzhecheng > 主题: [PULL 02/46] qemu-thread: fix races on threads that exit very quickly > > From: linzhecheng

Re: [Qemu-devel] [Bug 1739304] Re: Passing a directory to (eg.) -cdrom results in misleading error message

On 12/20/2017 05:31 AM, Dr. David Alan Gilbert wrote: > Yep, can repeat it here, it seems pretty random which error it gives: > > [dgilbert@dgilbert-t530 try]$ ./x86_64-softmmu/qemu-system-x86_64 -cdrom /tmp > qemu-system-x86_64: -cdrom /tmp: Could not refresh total sector count: > Invalid

Re: [Qemu-devel] [PATCH v20 0/7] Virtio-balloon Enhancement

On 12/21/2017 01:10 AM, Matthew Wilcox wrote: On Wed, Dec 20, 2017 at 04:13:16PM +, Wang, Wei W wrote: On Wednesday, December 20, 2017 8:26 PM, Matthew Wilcox wrote: unsigned long bit; xb_preload(GFP_KERNEL); xb_set_bit(xb, 700); xb_preload_end();

[Qemu-devel] [PATCH v20 3/7 RESEND] xbitmap: add more operations

This patch adds support to find next 1 or 0 bit in a xbmitmap range and clear a range of bits. More possible optimizations to add in the future: 1) xb_set_bit_range: set a range of bits. 2) when searching a bit, if the bit is not found in the slot, move on to the next slot directly. 3) add tags

[Qemu-devel] [Bug 1738283] Re: 'Less than' (<), 'more than' (>), and 'pipe' (|) can't be typed via VNC

Note: I wondered if specifying a correct model for qemu-keymap to pass to xkb would help. But it doesn't :( That is, these: qemu-keymap -l us qemu-keymap -l us -m pc101 qemu-keymap -l us -m pc104 qemu-keymap -l us -m pc105 all produce the same output except for the commented-out 'model' line at

[Qemu-devel] [PULL 1/2] Revert "docker: Enable features explicitly in test-full"

This reverts commit 5e8a7fe673ca5949bd51939ee36faaf3b1320de8. It's hard to get all images to have all these packages, the usual "FEATURES" and "require" mechanism doesn't scale with so many features. With that change, the test basically only works in ubuntu. Until a better way comes up, leave

[Qemu-devel] [PULL 0/2] Docker and UUID patches for 2.12

The following changes since commit 411ad78115ebeb3411cf4b7622784b93dfabe259: Merge remote-tracking branch 'remotes/stefanberger/tags/pull-tpm-2017-12-15-1' into staging (2017-12-17 15:27:41 +) are available in the Git repository at: git://github.com/famz/qemu.git

[Qemu-devel] [PULL 2/2] util: add is_equal to UUID API

From: Roman Kagan It's going to be useful, in particular, in VMBus code massively using uuids aka GUIDs. Signed-off-by: Roman Kagan Message-Id: <20171127124355.26015-1-rka...@virtuozzo.com> Signed-off-by: Fam Zheng ---

[Qemu-devel] [Bug 1739378] Re: qemu git master snapshot doesn't work

** Description changed: I'm having different issues trying to have QEMU snapshots working using qemu-system-arm with vexpress-a15 board. In this opportunity, I'm trying the git master head version: # git rev-parse HEAD af352675efb7e92a1f5f6461a042a12015ab3d12 - $

[Qemu-devel] [PULL 1/4] nbd/server: Implement sparse reads atop structured reply

The reason that NBD added structured reply in the first place was to allow for efficient reads of sparse files, by allowing the reply to include chunks to quickly communicate holes to the client without sending lots of zeroes over the wire. Time to implement this in the server; our client can

Re: [Qemu-devel] [PATCH 2/5] nbd/server: add nbd_opt_{read, drop} to track client->optlen

On 11/22/2017 02:03 PM, Eric Blake wrote: On 11/22/2017 04:19 AM, Vladimir Sementsov-Ogievskiy wrote: Signed-off-by: Vladimir Sementsov-Ogievskiy --- nbd/server.c | 34 ++ 1 file changed, 22 insertions(+), 12 deletions(-) I

[Qemu-devel] [PULL 2/4] nbd/server: Optimize final chunk of sparse read

If we are careful to handle 0-length read requests correctly, we can optimize our sparse read to send the NBD_REPLY_FLAG_DONE bit on our last OFFSET_DATA or OFFSET_HOLE chunk rather than needing a separate chunk. Signed-off-by: Eric Blake Message-Id:

[Qemu-devel] [PULL 4/4] qmp: add nbd-server-remove

From: Vladimir Sementsov-Ogievskiy 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 should

[Qemu-devel] [PULL 3/4] nbd/server: add additional assert to nbd_export_put

From: Vladimir Sementsov-Ogievskiy This place is not obvious, nbd_export_close may theoretically reduce refcount to 0. It may happen if someone calls nbd_export_put on named export not through nbd_export_set_name when refcount is 1. Signed-off-by: Vladimir

[Qemu-devel] [PULL 0/4] NBD patches through 20 Dec

The following changes since commit 4da5c51cac8363f86ec92dc99c38f9382d617647: Merge remote-tracking branch 'remotes/armbru/tags/pull-qapi-2017-12-20' into staging (2017-12-20 20:38:36 +) are available in the Git repository at: git://repo.or.cz/qemu/ericb.git tags/pull-nbd-2017-12-20

[Qemu-devel] [Bug 1738283] Re: 'Less than' (<), 'more than' (>), and 'pipe' (|) can't be typed via VNC

Confirmed that dropping the offending keycode 86 definition out of keymaps/en-us fixes the problem. Scratch build for Fedora Rawhide was https://koji.fedoraproject.org/koji/taskinfo?taskID=23814932 , I'll probably send this out as an official build so I can get os-autoinst built without hacking up

Re: [Qemu-devel] [PATCH 0/4] cryptodev: add vhost support

> -Original Message- > From: Michael S. Tsirkin [mailto:m...@redhat.com] > Sent: Thursday, December 21, 2017 1:39 AM > To: Gonglei (Arei) > Cc: qemu-devel@nongnu.org; pbonz...@redhat.com; Huangweidong (C); > stefa...@redhat.com; Zhoujian (jay); pa...@linux.vnet.ibm.com; longpeng; >

Re: [Qemu-devel] [PATCH v7 1/4] vhost-user: add new vhost user messages to support virtio config space

On Wed, Dec 20, 2017 at 04:47:13PM +0100, Marc-André Lureau wrote: > Hi > > On Wed, Dec 13, 2017 at 3:29 AM, Changpeng Liu > wrote: > > Add VHOST_USER_GET_CONFIG/VHOST_USER_SET_CONFIG messages which can be > > used for live migration of vhost user devices, also vhost

Re: [Qemu-devel] [PATCH v7 1/4] vhost-user: add new vhost user messages to support virtio config space

On Wed, Dec 20, 2017 at 06:28:04PM +, Marc-André Lureau wrote: > Michael, did you merge that one too? I think the series shouldn't be applied > yet until my concerns are cleared.  Thanks OK I'll drop these for now. > Le mer. 20 déc. 2017 à 16:47, Marc-André Lureau

Re: [Qemu-devel] [PATCH v3 2/2] target/i386: add clflushopt to "Skylake-Server" cpu model

On Tue, Dec 19, 2017 at 02:35:20PM -0200, Eduardo Habkost wrote: > On Tue, Dec 19, 2017 at 11:37:30AM +0800, Haozhong Zhang wrote: > > CPUID_7_0_EBX_CLFLUSHOPT is missed in current "Skylake-Server" cpu > > model. Add it to "Skylake-Server" cpu model on pc-i440fx-2.12 and > > pc-q35-2.12. Keep it

[Qemu-devel] [Bug 1738283] Re: 'Less than' (<), 'more than' (>), and 'pipe' (|) can't be typed via VNC

FWIW, I think this keycode represents the key between the left shift key and the first letter key on the fourth row, if there is one. European keyboards have one, and on e.g. a UK keyboard it types a \ unshifted and a | shifted - this is exactly how it looks in the en-gb keymap file: # evdev 86

Re: [Qemu-devel] [PATCH v2] hw/ide: Emulate SiI3112 SATA controller

On 12/16/2017 05:42 PM, BALATON Zoltan wrote: > This is a common generic PCI SATA controller that is also used in PCs > but more importantly guests running on the Sam460ex board prefer this > card and have a driver for it (unlike for other SATA controllers > already emulated). > >

Re: [Qemu-devel] [PATCH v2 02/19] spapr: introduce a skeleton for the XIVE interrupt controller

On Wed, 2017-12-20 at 16:09 +1100, David Gibson wrote: > > As you've suggested in yourself, I think we might need to more > explicitly model the different components of the XIVE system. As part > of that, I think you need to be clearer in this base skeleton about > exactly what component your

Re: [Qemu-devel] [PATCH net-next 1/2] virtio_net: allow hypervisor to indicate linkspeed and duplex setting

On Wed, Dec 20, 2017 at 04:32:52PM -0500, Jason Baron wrote: > > > On 12/20/2017 12:52 PM, Michael S. Tsirkin wrote: > > On Wed, Dec 20, 2017 at 12:07:55PM -0500, Jason Baron wrote: > >> > >> > >> On 12/20/2017 09:57 AM, Michael S. Tsirkin wrote: > >>> On Thu, Dec 14, 2017 at 02:33:53PM -0500,

Re: [Qemu-devel] [PATCH V2 0/5] hw/pvrdma: PVRDMA device implementation

On Wed, Dec 20, 2017 at 05:07:38PM +0200, Marcel Apfelbaum wrote: > On 19/12/2017 20:05, Michael S. Tsirkin wrote: > > On Sun, Dec 17, 2017 at 02:54:52PM +0200, Marcel Apfelbaum wrote: > > > RFC -> V2: > > > - Full implementation of the pvrdma device > > > - Backend is an ibdevice interface,

[Qemu-devel] [Bug 1738283] Re: 'Less than' (<), 'more than' (>), and 'pipe' (|) can't be typed via VNC

Aha. This looks like my bug! I'm running into this in what I suspect is the same situation as Michal Nowak: openQA. But in Fedora. openQA (well, its test runner, os- autoinst) works by running virtual machines and interacting with them over VNC. It seems that with qemu 2.11, typing certain

[Qemu-devel] [Bug 1738283] Re: 'Less than' (<), 'more than' (>), and 'pipe' (|) can't be typed via VNC

I found something interesting using showkey in the VM. This is all assuming en-US everywhere, note. On a US keyboard, "<" is a shifted comma (shift-,), ">" is a shifted period (shift-.), and "|" is a shifted backslash (shift-\). If I run showkey and try the affected characters in virt-manager,

[Qemu-devel] [Bug 1738283] Re: 'Less than' (<), 'more than' (>), and 'pipe' (|) can't be typed via VNC

I also confirm Michal's observation of virt-manager and tigervnc behaving differently with the same VM: I ran a VM set up with VNC display server in virt-manager and can type < from the virt-manager UI fine, but if I connect to the same VM with tigervnc and try to type < , I get > . This is with

[Qemu-devel] [Bug 1738283] Re: 'Less than' (<), 'more than' (>), and 'pipe' (|) can't be typed via VNC

I note this block in pc-bios/keymaps/en-us with interest: # evdev 86 (0x56), QKeyCode "less", number 0x56 less 0x56 greater 0x56 shift bar 0x56 altgr brokenbar 0x56 shift altgr That block was added in commit a7815faffb2bd594b92aa3542d7b799cc89c5414 , which I am very suspicious was the cause of

[Qemu-devel] [Bug 1738283] Re: 'Less than' (<), 'more than' (>), and 'pipe' (|) can't be typed via VNC

Note, os-autoinst is its own VNC client. Most of the implementation can be found in https://github.com/os-autoinst/os- autoinst/blob/master/consoles/VNC.pm . The functions relevant to sending key events are `shift_keys`, `init_x11_keymap`, `map_and_send_key`, and `_send_key_event`. -- You

Re: [Qemu-devel] [PATCH qemu] RFC: spapr/iommu: Enable in-kernel TCE acceleration via VFIO KVM device

On 20/12/2017 15:13, Alexey Kardashevskiy wrote: > On 20/12/17 20:04, Paolo Bonzini wrote: >> On 20/12/2017 02:47, Alexey Kardashevskiy wrote: - if we foresee having more IOMMU devices in KVM, let's rename KVM_DEV_VFIO_GROUP_SET_SPAPR_TCE to KVM_DEV_VFIO_GROUP_ATTACH_IOMMU and add a

Re: [Qemu-devel] [PATCH v2 0/2] Enable full IPv4/IPv6 dual stack for NBD server

On 21/12/2017 00:16, Eric Blake wrote: > On 12/18/2017 05:48 AM, Paolo Bonzini wrote: >> On 18/12/2017 11:16, Daniel P. Berrange wrote: >>> These patches were previously posted as part of a larger series: >>> >>>    https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02064.html >>> >>> These

Re: [Qemu-devel] [PATCH v2 0/2] Enable full IPv4/IPv6 dual stack for NBD server

On 12/18/2017 05:48 AM, Paolo Bonzini wrote: On 18/12/2017 11:16, Daniel P. Berrange wrote: These patches were previously posted as part of a larger series: https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02064.html These patches port the NBD server to use QIONetListener, which

Re: [Qemu-devel] [PULL 00/14] ppc-for-2.12 queue 20171219

On Wed, Dec 20, 2017 at 11:29:36AM +, Peter Maydell wrote: > On 19 December 2017 at 04:29, David Gibson > wrote: > > The following changes since commit eaefea537b476cb853e2edbdc68e969ec777e4bb: > > > > Merge remote-tracking branch

Re: [Qemu-devel] [PATCH 1/3] input: add missing JIS keys to virtio input

On 12/18/2017 07:24 AM, Miika S wrote: Signed-off-by: Miika S --- hw/input/virtio-input-hid.c | 7 +++ qapi/ui.json| 2 +- ui/keycodemapdb | 2 +- 3 files changed, 9 insertions(+), 2 deletions(-) When sending a multi-patch series,

Re: [Qemu-devel] [PATCH 0/6] spapr: Add optional capabilities

On Mon, 2017-12-18 at 20:20 +1100, David Gibson wrote: > This series is a first draft to add the notion of optional > capabilities to the "pseries" machine type. A default set of > capabilities is selected based on the machine type version and > selected cpu model, but this can be overridden with

Re: [Qemu-devel] [PULL 00/13] QAPI patches for 2017-12-20

On 20 December 2017 at 18:59, Markus Armbruster wrote: > The following changes since commit 200780a3a3ed067dfb2e0d2210b0ed09e748ba26: > > Merge remote-tracking branch > 'remotes/armbru/tags/pull-cmdline-2017-12-18-v2' into staging (2017-12-20 > 13:20:48 +) > > are

Re: [Qemu-devel] [PATCH v6 08/29] hw/i386: Replace fprintf(stderr, "*\n" with error_report()

On Wed, Dec 20, 2017 at 09:23:16AM -0800, Alistair Francis wrote: > Replace a large number of the fprintf(stderr, "*\n" calls with > error_report(). The functions were renamed with these commands and then > compiler issues where manually fixed. > > find ./* -type f -exec sed -i \ >

Re: [Qemu-devel] [PATCH v4 0/5] Add a valid_cpu_types property

On Tue, Dec 19, 2017 at 05:03:59PM -0800, Alistair Francis wrote: > On Tue, Dec 19, 2017 at 4:55 PM, Alistair Francis > wrote: > > On Tue, Dec 19, 2017 at 4:43 PM, Peter Maydell > > wrote: > >> On 20 December 2017 at 00:27, Alistair Francis

Re: [Qemu-devel] [PULL 00/46] First batch of misc patches for QEMU 2.12

On 20/12/2017 20:20, Peter Maydell wrote: > On the x86/sanitizer build, new runtime errors: > GTESTER check-qtest-m68k > /home/petmay01/linaro/qemu-for-merges/target/m68k/translate.c:230:12: > runtime error: index -1 out of bounds for type 'const uint8_t [11]' > > ...and similar fails on one or

Re: [Qemu-devel] [PATCH v3 0/7] Add aarch64_be-linux-user target

Hi, This series seems to have some coding style problems. See output below for more information: Type: series Message-id: 20171220212308.12614-1-michael.wei...@gmx.de Subject: [Qemu-devel] [PATCH v3 0/7] Add aarch64_be-linux-user target === TEST SCRIPT BEGIN === #!/bin/bash BASE=base n=1

Re: [Qemu-devel] [Qemu-block] [PATCH 0/3] block: Deprecated options

On 12/18/2017 12:14 PM, Thomas Huth wrote: > Remove the deprecated "-drive boot" and "-hdachs" options and properly > mark some other deprecated options in the deprecation chapter. > > Thomas Huth (3): > block: Remove the obsolete -drive boot=on|off parameter > block: Remove the deprecated

Re: [Qemu-devel] [RESEND PATCH for-2.12 0/2] ACPI/unit-test: Add a testcase

On Tue, Dec 19, 2017 at 12:01:59PM +0800, Dou Liyang wrote: > Hi Eduardo, > > At 12/19/2017 06:09 AM, Eduardo Habkost wrote: > > On Thu, Dec 14, 2017 at 12:08:53PM +0800, Dou Liyang wrote: > > > These are the patches left over from the pull request: > > > > > >[Qemu-devel] [PULL 0/9] x86 and

Re: [Qemu-devel] [PATCH net-next 1/2] virtio_net: allow hypervisor to indicate linkspeed and duplex setting

On 12/20/2017 12:52 PM, Michael S. Tsirkin wrote: > On Wed, Dec 20, 2017 at 12:07:55PM -0500, Jason Baron wrote: >> >> >> On 12/20/2017 09:57 AM, Michael S. Tsirkin wrote: >>> On Thu, Dec 14, 2017 at 02:33:53PM -0500, Jason Baron wrote: If the hypervisor exports the link and duplex speed,

[Qemu-devel] [PATCH v3 6/7] linux-user: Separate binfmt arm CPU families

Give big-endian arm and aarch64 CPUs their own family in qemu-binfmt-conf.sh to make sure we register qemu-user for binaries of the opposite endianness on arm and aarch64. Apart from the family assignments of the magic vales, qemu_get_family() needs to be able to distinguish the two and recognise

[Qemu-devel] [PATCH v3 5/7] linux-user: Add aarch64_be magic numbers to qemu-binfmt-conf.sh

As we now have a linux-user aarch64_be target, we can add it to the list of supported targets in qemu-binfmt-conf.sh Signed-off-by: Michael Weiser --- scripts/qemu-binfmt-conf.sh | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git

[Qemu-devel] [PATCH v3 2/7] linux-user: Add separate aarch64_be uname

Make big-endian aarch64 systems identify as aarch64_be as expected by big-endian userland and toolchains. Signed-off-by: Michael Weiser Reviewed-by: Richard Henderson --- linux-user/aarch64/target_syscall.h | 4 1 file changed, 4

[Qemu-devel] [PATCH v3 4/7] configure: Add aarch64_be-linux-user target

Add target aarch64_be-linux-user. This allows a qemu-aarch64_be binary to be built that will run big-endian aarch64 binaries. Signed-off-by: Michael Weiser Reviewed-by: Richard Henderson --- configure | 5

[Qemu-devel] [PATCH v3 0/7] Add aarch64_be-linux-user target

Hello, below patches add support for big-endian aarch64 to linux-user. Almost everything is already in place. The patches just set up the CPU flags as required for big-endianness, add a distinction in uname and make sure the instructions for the signal trampoline end up in memory little-endian.

[Qemu-devel] [PATCH v3 1/7] linux-user: Add support for big-endian aarch64

Enable big-endian mode for data accesses on aarch64 for big-endian linux user mode. Activate it for all exception levels as documented by ARM: Set the SCTLR EE bit for ELs 1 through 3. Additionally set bit E0E in EL1 to enable it in EL0 as well. Signed-off-by: Michael Weiser

[Qemu-devel] [PATCH v3 3/7] linux-user: Fix endianess of aarch64 signal trampoline

Since for aarch64 the signal trampoline is synthesized directly into the signal frame we need to make sure the instructions end up little-endian. Otherwise the wrong endianness will cause a SIGILL upon return from the signal handler on big-endian targets. Signed-off-by: Michael Weiser

[Qemu-devel] [PATCH v3 7/7] linux-user: Activate armeb handler registration

armeb is missing from the target list in qemu-binfmt-conf.sh. Add it so the handler for those binaries gets registered by the script. Signed-off-by: Michael Weiser --- scripts/qemu-binfmt-conf.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [Qemu-devel] [Bug 1739371] Re: qemu-system-arm snapshot loadvm core dumped

Thanks Peter for your prompt response. I wonder if you have any plan of fixing it. Also if there is any workaround. Is the bug limited to arm? Is there any main ticket where I can follow the progress of this issue? On Thu., 21 Dec. 2017, 2:50 am Peter Maydell, wrote:

Re: [Qemu-devel] [PATCH v2 0/2] mux chardev events regression fix

On 20/12/2017 16:11, Paolo Bonzini wrote: > On 03/11/2017 16:28, Marc-André Lureau wrote: >> Hi, >> >> The following patches fix and test the behaviour of mux chardev >> events, after a regression introduced in qemu 2.8.0. >> >> v1->v2: >> - fix incompatible pointer type warning spotted by patchew

Re: [Qemu-devel] [PATCH] target/m68k: add monitor.c

Am Wed, 20 Dec 2017 21:35:28 +0100 schrieb Laurent Vivier : > This allows to use registers content in the monitor. > > Example: > > BEFORE: > (qemu) print $d0 > unknown register > > AFTER: > (qemu) print $d0 > 0 > (qemu) print $sr > 0x2000 > (qemu) x/10i $pc

Re: [Qemu-devel] [PATCH] target/m68k: add monitor.c

On 12/20/2017 12:35 PM, Laurent Vivier wrote: > +const MonitorDef monitor_defs[] = { static. Otherwise, Reviewed-by: Richard Henderson r~

Re: [Qemu-devel] [PATCH] target/m68k: add monitor.c

On Wed, Dec 20, 2017 at 5:35 PM, Laurent Vivier wrote: > This allows to use registers content in the monitor. > > Example: > > BEFORE: > (qemu) print $d0 > unknown register > > AFTER: > (qemu) print $d0 > 0 > (qemu) print $sr > 0x2000 > (qemu) x/10i $pc >

Re: [Qemu-devel] [PATCH 0/4] Add aarch64_be-linux-user target

Hi, This series seems to have some coding style problems. See output below for more information: Type: series Message-id: 20171219151636.5162-1-michael.wei...@gmx.de Subject: [Qemu-devel] [PATCH 0/4] Add aarch64_be-linux-user target === TEST SCRIPT BEGIN === #!/bin/bash BASE=base n=1

[Qemu-devel] [PATCH] target/m68k: add monitor.c

This allows to use registers content in the monitor. Example: BEFORE: (qemu) print $d0 unknown register AFTER: (qemu) print $d0 0 (qemu) print $sr 0x2000 (qemu) x/10i $pc 0x40010a2a: movew %sr,%d0 0x40010a2c: oril #1792,%d0 0x40010a32: movew %d0,%sr 0x40010a34: movel

Re: [Qemu-devel] [PULL 00/19] Initial support for Hypervisor.framework

On 20 December 2017 at 18:03, Paolo Bonzini wrote: > The following changes since commit f1faf2d59c91a8f1f59a0fc6339154efb749b55d: > > Merge remote-tracking branch 'remotes/stefanha/tags/block-pull-request' > into staging (2017-12-20 11:30:55 +) > > are available in the

Re: [Qemu-devel] [PATCH v2 5/5] linux-user: Add aarch64_be magic numbers to qemu-binfmt-conf.sh

Hi Laurent, On Wed, Dec 20, 2017 at 05:43:34PM +0100, Laurent Vivier wrote: > >> So it's not like on intel/AMD where we can execute a 32bit binary on a > >> 64bit kernel? > > > > An aarch64 CPU is capable of running arm (i.e. aarch32) code. And I > > think this is supported as a multilib setup

Re: [Qemu-devel] [PULL 00/46] First batch of misc patches for QEMU 2.12

Hi, This series seems to have some coding style problems. See output below for more information: Type: series Message-id: 1513790098-9815-1-git-send-email-pbonz...@redhat.com Subject: [Qemu-devel] [PULL 00/46] First batch of misc patches for QEMU 2.12 === TEST SCRIPT BEGIN === #!/bin/bash

Re: [Qemu-devel] [PULL 00/19] Initial support for Hypervisor.framework

Hi, This series seems to have some coding style problems. See output below for more information: Type: series Message-id: 20171220180358.29316-1-pbonz...@redhat.com Subject: [Qemu-devel] [PULL 00/19] Initial support for Hypervisor.framework === TEST SCRIPT BEGIN === #!/bin/bash BASE=base n=1

[Qemu-devel] [PATCH] 9pfs: drop v9fs_register_transport()

No good reasons to do this outside of v9fs_device_realize_common(). Signed-off-by: Greg Kurz --- hw/9pfs/9p.c |6 +- hw/9pfs/9p.h | 10 ++ hw/9pfs/virtio-9p-device.c |8 ++-- hw/9pfs/xen-9p-backend.c |3 +-- 4 files

Re: [Qemu-devel] [PULL 00/46] First batch of misc patches for QEMU 2.12

On 20 December 2017 at 17:14, Paolo Bonzini wrote: > The following changes since commit 200780a3a3ed067dfb2e0d2210b0ed09e748ba26: > > Merge remote-tracking branch > 'remotes/armbru/tags/pull-cmdline-2017-12-18-v2' into staging (2017-12-20 > 13:20:48 +) > > are

Re: [Qemu-devel] [PATCH] 9pfs: make pdu_marshal() and pdu_unmarshal() static functions

On 12/15/2017 04:20 PM, Greg Kurz wrote: They're only used by the 9p core code. Signed-off-by: Greg Kurz --- hw/9pfs/9p.c |4 ++-- hw/9pfs/9p.h |2 -- 2 files changed, 2 insertions(+), 4 deletions(-) Reviewed-by: Eric Blake -- Eric Blake,

Re: [Qemu-devel] [PATCH v1 1/1] qmp: remove qmp_cpu

On 12/20/2017 04:23 AM, Daniel Henrique Barboza wrote: 'qmp_cpu' was implemented in commit 755f196898 ("qapi: Convert the cpu command") as a functional no-op, a QMP call that does nothing and return success. The idea, apparently, was to provide a counterpart for the HMP 'hmp_cpu' command,

[Qemu-devel] [PULL 08/13] qapi: Simplify representation of QAPIDoc section text

Use a string instead of a list of strings. This makes qapi2texi.py generate additional blank lines. They're harmless, and the next commit will get rid of them again. Signed-off-by: Markus Armbruster Message-Id: <20171002141341.24616-9-arm...@redhat.com> Reviewed-by:

[Qemu-devel] [PULL 10/13] qapi: Rename QAPIDoc.parser, .section to ._parser, ._section

Signed-off-by: Markus Armbruster Message-Id: <20171002141341.24616-11-arm...@redhat.com> Reviewed-by: Marc-André Lureau --- scripts/qapi.py | 52 ++-- 1 file changed, 26 insertions(+), 26

[Qemu-devel] [PULL 13/13] qmp: remove qmp_cpu

From: Daniel Henrique Barboza 'qmp_cpu' was implemented in commit 755f196898 ("qapi: Convert the cpu command") as a functional no-op, a QMP call that does nothing and return success. The idea, apparently, was to provide a counterpart for the HMP 'hmp_cpu' command,

[Qemu-devel] [PULL 07/13] qapi: Unify representation of doc section without name

We have two representations of sections without a name: the main section uses name=None, the others name=''. Standardize on name=None. Signed-off-by: Markus Armbruster Message-Id: <20171002141341.24616-8-arm...@redhat.com> Reviewed-by: Marc-André Lureau

[Qemu-devel] [PULL 09/13] qapi2texi: Simplify representation of section text

Use a string instead of a list of strings. While there, generate fewer superfluous blank lines. Signed-off-by: Markus Armbruster Message-Id: <20171002141341.24616-10-arm...@redhat.com> Reviewed-by: Marc-André Lureau --- scripts/qapi2texi.py

[Qemu-devel] [PULL 11/13] qapi2texi: De-duplicate code to add blank line before symbol

Signed-off-by: Markus Armbruster Message-Id: <20171002141341.24616-12-arm...@redhat.com> Reviewed-by: Marc-André Lureau --- scripts/qapi2texi.py | 12 ++-- 1 file changed, 2 insertions(+), 10 deletions(-) diff --git a/scripts/qapi2texi.py

Re: [Qemu-devel] [PATCH] 9pfs: fix error path in pdu_submit()

On 12/15/2017 10:42 AM, Greg Kurz wrote: If we receive an unsupported request id, we first decide to return -ENOTSUPP to the client, but since the request id causes is_read_only_op() to return false, we change the error to be -EROFS if the fsdev is read-only. This doesn't make sense since we

[Qemu-devel] [PULL 05/13] tests/qapi-schema/doc-bad-section: New, factored out of doc-good

A negative test case crept into doc-good.json: invalid use of section markup we currently fail to reject. Move this into its own doc-bad-section.json. Signed-off-by: Markus Armbruster Message-Id: <20171002141341.24616-6-arm...@redhat.com> Reviewed-by: Marc-André Lureau

[Qemu-devel] [PULL 02/13] qapi: Stop rejecting #optional

Commit 1d8bda1 got rid of #optional tags, and added a check to keep them from getting added back, to make sure patches then in flight don't add them back. It's been six months, time to drop that check. Signed-off-by: Markus Armbruster Message-Id:

[Qemu-devel] [PULL 03/13] qapi: Eliminate QAPISchemaParser.__init__()'s local fname

Signed-off-by: Markus Armbruster Message-Id: <20171002141341.24616-4-arm...@redhat.com> Reviewed-by: Marc-André Lureau --- scripts/qapi.py | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/scripts/qapi.py b/scripts/qapi.py

[Qemu-devel] [PULL 12/13] qapi-docs: fix a comment typo

From: Chen Hanxiao s/Subection/Subsection Signed-off-by: Chen Hanxiao Message-Id: <20171012064448.20276-1-chen_han_x...@126.com> Reviewed-by: Marc-André Lureau Signed-off-by: Markus Armbruster ---

[Qemu-devel] [PULL 01/13] qapi-schema: Fix query-vm-generation-id's doc comment markup

Reported-by: Daniel P. Berrange Signed-off-by: Markus Armbruster Message-Id: <20171002141341.24616-2-arm...@redhat.com> Reviewed-by: Marc-André Lureau --- qapi-schema.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[Qemu-devel] [PULL 04/13] qapi: Make cur_doc local to QAPISchemaParser.__init__()

QAPISchemaParser.cur_doc is used only by .__init__() and its helper .reject_expr_doc(). Make it local to __init__() and pass it to .reject_expr_doc() explicitly. Signed-off-by: Markus Armbruster Message-Id: <20171002141341.24616-5-arm...@redhat.com> Reviewed-by: Marc-André

[Qemu-devel] [PULL 06/13] qapi2texi: Clean up texi_sections()

Repurposing the function parameter doc for stepping through doc.sections.__str__() is not nice. Use new variable @text instead. While there, eliminate variables name and func. Signed-off-by: Markus Armbruster Message-Id: <20171002141341.24616-7-arm...@redhat.com>

Re: [Qemu-devel] Raw notes from a small block layer/QAPI/something pre-christmas meeting

"Daniel P. Berrange" writes: > On Fri, Dec 15, 2017 at 05:38:00PM +0100, Max Reitz wrote: > >> Image creation in qemu-system-* vs. qemu-img: >> In order to get proper introspection for qemu-img create, we need a >> QAPI schema. If we have a QAPI schema, we might as well

[Qemu-devel] [PULL 00/13] QAPI patches for 2017-12-20

The following changes since commit 200780a3a3ed067dfb2e0d2210b0ed09e748ba26: Merge remote-tracking branch 'remotes/armbru/tags/pull-cmdline-2017-12-18-v2' into staging (2017-12-20 13:20:48 +) are available in the git repository at: git://repo.or.cz/qemu/armbru.git

[Qemu-devel] [PULL 17/19] i386: hvf: remove addr_t

Use target_ulong for virtual addresses and uint64_t for physical addresses. Signed-off-by: Paolo Bonzini --- target/i386/hvf/hvf.c| 4 ++-- target/i386/hvf/x86.c| 15 +++-- target/i386/hvf/x86.h| 12 +- target/i386/hvf/x86_decode.c |

[Qemu-devel] [Bug 1739378] Re: qemu git master snapshot doesn't work

>From a quick look my guess would be the wpgrps_size in sd_vmstate is different >on the source and destination for some reason - it's the only thing that seems >to be variable. (It could also be whether the subsection is transmitted or not, but that's supposed to sort itself out automatically).

Re: [Qemu-devel] [PATCH v1 1/1] qmp: remove qmp_cpu

Daniel Henrique Barboza writes: > 'qmp_cpu' was implemented in commit 755f196898 ("qapi: Convert the cpu > command") as a functional no-op, a QMP call that does nothing and > return success. The idea, apparently, was to provide a counterpart > for the HMP 'hmp_cpu'

[Qemu-devel] [PULL 12/19] i386: hvf: unify register enums between HVF and the rest

Signed-off-by: Paolo Bonzini --- target/i386/cpu.h| 62 +++--- target/i386/hvf/vmx.h| 10 +-- target/i386/hvf/x86.c| 10 +-- target/i386/hvf/x86.h| 145 +--

Re: [Qemu-devel] [PATCH v2 0/5] target/m68k: implement 680x0 FPU (part 3)

Le 23/11/2017 à 17:35, Laurent Vivier a écrit : > Implement fmod, frem, fscale, fgetman and fgetexp. > > Instead of using functions of libm (v1 of this series) > and converting between host long double and floatx80 type > the new version (v2) adds new floatx80 functions in softfloat. > > All the

[Qemu-devel] [PULL 16/19] i386: hvf: simplify flag handling

Remove much indirection and duplicate code, and provide a cleaner interface out of x86_flags.c. Signed-off-by: Paolo Bonzini --- target/i386/hvf/x86_emu.c | 93 +- target/i386/hvf/x86_flags.c | 235 +---

  1   2   3   4   5   >