Re: [Qemu-devel] [PATCH v10 01/19] vfio: Mediated device Core driver

On 10/27/2016 05:29 AM, Kirti Wankhede wrote: > +int mdev_register_device(struct device *dev, const struct parent_ops *ops) > +{ > + int ret; > + struct parent_device *parent; > + > + /* check for mandatory ops */ > + if (!ops || !ops->create || !ops->remove ||

[Qemu-devel] [Bug 1637693] [NEW] QEMU not able to create vm with pflash and UEFI bios

Public bug reported: Running Fedora 24 with the virt-preview repo on QEMU Version 2.7.0 and libvirt version 2.2.0. Tried to install a windows 10 vm with the OVMF bios and this error happens every time, it didnt happen when using the stable version of qemu for fedora 24. libvirtError: internal

Re: [Qemu-devel] [PATCH 1/2] KVM: page track: add a new notifier type: track_flush_slot

On 10/26/2016 10:45 PM, Paolo Bonzini wrote: > On 26/10/2016 15:44, Jike Song wrote: >> On 10/21/2016 01:06 AM, Paolo Bonzini wrote: >>> On 20/10/2016 03:48, Xiao Guangrong wrote: I understood that KVM side is safe, however, vfio side is independent with kvm and the user of usrdata can

[Qemu-devel] [PATCH v4 4/8] qdev: Extract property-default code to qdev_property_set_to_default()

The code that registers qdev properties will be split from the code that initializes default values on instance_init, so move it to a separate function. Reviewed-by: Igor Mammedov Signed-off-by: Eduardo Habkost --- Changes series v1 -> v4: * (none) ---

[Qemu-devel] [PATCH v4 8/8] qdev: Warning about using qdev_property_add_static() in new code

The only remaining user of qdev_property_add_static() is arm_cpu_post_init(), but removing it may take some work. While we don't change it, warn people to not use the function in new code. Cc: Peter Maydell Cc: qemu-...@nongnu.org Signed-off-by: Eduardo Habkost

[Qemu-devel] [PATCH v4 7/8] qmp: Support abstract classes on device-list-properties

When an abstract class is used on device-list-properties, we can simply return the class properties registered for the class. This will be useful if management software needs to query for supported options that apply to all devices of a given type (e.g. options supported by all CPU models,

[Qemu-devel] [PATCH v4 0/8] qdev class properties + abstract class support on device-list-properties

Changes v3 -> v4: * FIx "make check" failures: * Fix e1000e initialization ordering (fixes tests/device-introspect-test failure) * Reported-by: Igor Mammedov * Call prop->info->release on instance_finalize (fixes tests/drive_del-test failure) * See individual

[Qemu-devel] [PATCH v4 6/8] qom: object_class_property_iter_init() function

The new function will allow us to iterate over class properties using the same logic we use for object properties. Unit test included. Signed-off-by: Eduardo Habkost --- Changes series v1 -> v3: * (none) Changes series v3 -> v4: * Trivial whitespace change (removed extra

[Qemu-devel] [PATCH v4 5/8] qdev: Register static properties as class properties

Instead of registering qdev static properties on instance_init, register them as class properties, at qdev_class_set_props(). qdev_property_add_legacy() was replaced by an equivalent qdev_class_property_add_legacy() function. qdev_property_add_static(), on the other hand, can't be eliminated yet

[Qemu-devel] [PATCH v4 1/8] tests: check-qom-proplist: Remove duplicate "bv" property

The object_property_add_bool() call in dummy_init() is always failing because there is an existing "bv" class property. We need to remove either the "bv" class property or the "bv" instance property. Remove the class property so both object properties and class properties are covered by the test

[Qemu-devel] [PATCH v4 2/8] tests: check-qom-proplist: Use _abort to catch errors

Use _abort so we don't ignore any errors on the property registration calls. Signed-off-by: Eduardo Habkost --- Changes series v2 -> v3: * Patch imported from "tests: A few check-qom-proplist fixes" series Changes series v3 -> v4: * Added _abort to more

[Qemu-devel] [PULL 12/13] xen: Rename xen_be_find_xendev

From: Emil Condrea Prepare xen_be_find_xendev to be shared with frontends: * xen_be_find_xendev -> xen_pv_find_xendev Signed-off-by: Emil Condrea Signed-off-by: Stefano Stabellini Signed-off-by: Quan Xu

[Qemu-devel] [PULL 08/13] xen: Rename xen_be_printf to xen_pv_printf

From: Emil Condrea Prepare xen_be_printf to be used by both backend and frontends: * xen_be_printf -> xen_pv_printf Signed-off-by: Emil Condrea Signed-off-by: Stefano Stabellini Signed-off-by: Quan Xu

[Qemu-devel] [PULL 13/13] xen: Rename xen_be_del_xendev

From: Emil Condrea Prepare xen_be_del_xendev to be shared with frontends: * xen_be_del_xendev -> xen_pv_del_xendev Signed-off-by: Emil Condrea Signed-off-by: Stefano Stabellini Signed-off-by: Quan Xu

[Qemu-devel] [PULL 10/13] xen: Rename xen_be_send_notify

From: Emil Condrea Prepare xen_be_send_notify to be shared with frontends: * xen_be_send_notify -> xen_pv_send_notify Signed-off-by: Emil Condrea Signed-off-by: Stefano Stabellini Signed-off-by: Quan Xu

[Qemu-devel] [PULL 11/13] xen: Rename xen_be_evtchn_event

From: Emil Condrea Prepare xen_be_evtchn_event to be shared with frontends: * xen_be_evtchn_event -> xen_pv_evtchn_event Signed-off-by: Emil Condrea Signed-off-by: Stefano Stabellini Signed-off-by: Quan Xu

[Qemu-devel] [PULL 05/13] xen: Move evtchn functions to xen_pvdev.c

From: Emil Condrea The name of the functions moved: * xen_be_evtchn_event * xen_be_unbind_evtchn * xen_be_send_notify Signed-off-by: Emil Condrea Signed-off-by: Stefano Stabellini Signed-off-by: Quan Xu

[Qemu-devel] [PULL 06/13] xen: Prepare xendev qtail to be shared with frontends

From: Emil Condrea * move xendevs qtail to xen_pvdev.c * change xen_be_get_xendev to use a new function: xen_pv_insert_xendev Signed-off-by: Emil Condrea Signed-off-by: Stefano Stabellini Signed-off-by: Quan Xu

[Qemu-devel] [PULL 07/13] xen: Move xenstore cleanup and mkdir functions

From: Emil Condrea The name of the functions moved to xen_pvdev.c: * xenstore_cleanup_dir * xen_config_cleanup * xenstore_mkdir Signed-off-by: Emil Condrea Signed-off-by: Stefano Stabellini Signed-off-by: Quan Xu

[Qemu-devel] [PULL 09/13] xen: Rename xen_be_unbind_evtchn

From: Emil Condrea Prepare xen_be_unbind_evtchn to be shared with frontends: * xen_be_unbind_evtchn -> xen_pv_unbind_evtchn Signed-off-by: Emil Condrea Signed-off-by: Stefano Stabellini Signed-off-by: Quan Xu

[Qemu-devel] [PULL 01/13] xen: Fix coding style errors

From: Emil Condrea Fixes the following errors: * ERROR: line over 90 characters * ERROR: code indent should never use tabs * ERROR: space prohibited after that open square bracket '[' * ERROR: do not initialise statics to 0 or NULL * ERROR: "(foo*)" should be "(foo

[Qemu-devel] [PULL 03/13] xen: Create a new file xen_pvdev.c

From: Emil Condrea The purpose of the new file is to store generic functions shared by frontend and backends such as xenstore operations, xendevs. Signed-off-by: Quan Xu Signed-off-by: Emil Condrea Signed-off-by: Stefano

[Qemu-devel] [PULL 04/13] xen: Move xenstore_update to xen_pvdev.c

From: Emil Condrea * xenstore_update -> xen_pvdev.c Signed-off-by: Emil Condrea Signed-off-by: Stefano Stabellini Signed-off-by: Quan Xu Acked-by: Anthony PERARD ---

[Qemu-devel] [PULL 02/13] xen: Fix coding style warnings

From: Emil Condrea Fixes: * WARNING: line over 80 characters Signed-off-by: Emil Condrea Signed-off-by: Stefano Stabellini Signed-off-by: Quan Xu Acked-by: Anthony PERARD

[Qemu-devel] [PULL 00/13] xen-20161028-tag

The following changes since commit 5b2ecabaeabc17f032197246c4846b9ba95ba8a6: Merge remote-tracking branch 'remotes/kraxel/tags/pull-ui-20161028-1' into staging (2016-10-28 17:59:04 +0100) are available in the git repository at: git://xenbits.xen.org/people/sstabellini/qemu-dm.git tags/xen

Re: [Qemu-devel] [PATCH 1/2] target-m68k: add 64bit mull

On 10/28/2016 03:39 PM, Laurent Vivier wrote: +tcg_gen_movi_i32(QREG_CC_V, 0); +tcg_gen_mov_i32(QREG_CC_C, QREG_CC_V); movi CC, 0 Otherwise, Reviewed-by: Richard Henderson r~

[Qemu-devel] [PATCH v2 2/2] target-m68k: add 680x0 divu/divs variants

Update helper to set the throwing location in case of div-by-0. Cleanup divX.w and add quad word variants of divX.l. Signed-off-by: Laurent Vivier --- linux-user/main.c | 7 +++ target-m68k/cpu.h | 4 -- target-m68k/helper.h| 6 +-

[Qemu-devel] [PATCH v2 1/2] target-m68k: add 64bit mull

Signed-off-by: Laurent Vivier --- target-m68k/translate.c | 60 +++-- 1 file changed, 48 insertions(+), 12 deletions(-) diff --git a/target-m68k/translate.c b/target-m68k/translate.c index c00978d..d612a82 100644 ---

[Qemu-devel] [PATCH v2 0/2] 680x0 mul and div instructions

This series is another subset of the series I sent in May: https://lists.gnu.org/archive/html/qemu-devel/2016-05/msg00501.html It must be applied on top of series: "target-m68k: 680x0 instruction set, part 2" This subset contains reworked patches of mul and div instructions: - "add 64bit mull":

Re: [Qemu-devel] [PATCH 2/2] target-m68k: add 680x0 divu/divs variants

Le 29/10/2016 à 00:39, Laurent Vivier a écrit : > Update helper to set the throwing location in case of div-by-0. > Cleanup divX.w and add quad word variants of divX.l. > > Signed-off-by: Laurent Vivier > --- > linux-user/main.c | 7 +++ > target-m68k/cpu.h |

[Qemu-devel] [PATCH 2/2] target-m68k: add 680x0 divu/divs variants

Update helper to set the throwing location in case of div-by-0. Cleanup divX.w and add quad word variants of divX.l. Signed-off-by: Laurent Vivier --- linux-user/main.c | 7 +++ target-m68k/cpu.h | 4 -- target-m68k/helper.h| 6 +-

[Qemu-devel] [PATCH 0/2] 680x0 mul and div instructions

This series is another subset of the series I sent in May: https://lists.gnu.org/archive/html/qemu-devel/2016-05/msg00501.html It must be applied on top of series: "target-m68k: 680x0 instruction set, part 2" This subset contains reworked patches of mul and div instructions: - "add 64bit mull":

[Qemu-devel] [PATCH 1/2] target-m68k: add 64bit mull

Signed-off-by: Laurent Vivier --- target-m68k/translate.c | 60 +++-- 1 file changed, 48 insertions(+), 12 deletions(-) diff --git a/target-m68k/translate.c b/target-m68k/translate.c index c00978d..d612a82 100644 ---

[Qemu-devel] [PATCH] atapi: classify read_cd as conditionally returning data

For the purposes of byte_count_limit verification, add a new flag that identifies read_cd as sometimes returning data, then check the BCL in its command handler after we know that it will indeed return data. Reported-by: Hervé Poussineau Signed-off-by: John Snow

[Qemu-devel] [PATCH] 9pfs: drop abusive error message from virtfs_reset()

The virtfs_reset() function is called either when the virtio-9p device gets reset, or when the client starts a new 9P session. In both cases, if it finds fids from a previous session, the following is printed in the monitor: 9pfs:virtfs_reset: One or more uncluncked fids found during reset For

Re: [Qemu-devel] [PATCH v3] block/vxhs: Add Veritas HyperScale VxHS block device support

On 10/28/16, 12:03 PM, "Jeff Cody" wrote: >On Fri, Oct 28, 2016 at 12:44:27AM -0700, Ashish Mittal wrote: >> This patch adds support for a new block device type called "vxhs". >> Source code for the qnio library that this code loads can be downloaded >>from: >>

Re: [Qemu-devel] [PATCH v2] block/vxhs: Add Veritas HyperScale VxHS block device support

On Fri, Oct 28, 2016 at 01:26:41AM +, Rakesh Ranjan wrote: > Hi Jeff etc al, > > Thanks a lot for your due diligence to review the code changes throughly > and providing comments, suggestions to improve. We are completely on top > of this and have already started to expedite the overall

Re: [Qemu-devel] [PATCH v3] block/vxhs: Add Veritas HyperScale VxHS block device support

Hi Eric, On Fri, Oct 28, 2016 at 7:44 AM, Eric Blake wrote: > On 10/28/2016 02:44 AM, Ashish Mittal wrote: >> This patch adds support for a new block device type called "vxhs". >> Source code for the qnio library that this code loads can be downloaded from: >>

Re: [Qemu-devel] [PATCH] block-backend: Always notify on blk_eject

On 10/28/2016 05:23 PM, John Snow wrote: blk_eject is only used by scsi-disk and atapi, and in both cases we only attempt to invoke blk_eject if we have a bona-fide change in tray state. The "issue" here is that the tray state does not generate a QMP event unless there is a medium/BDS

[Qemu-devel] [PATCH] block-backend: Always notify on blk_eject

blk_eject is only used by scsi-disk and atapi, and in both cases we only attempt to invoke blk_eject if we have a bona-fide change in tray state. The "issue" here is that the tray state does not generate a QMP event unless there is a medium/BDS attached to the device, so if libvirt et al are

[Qemu-devel] Periodically print the number of dirty pages in KVM-QEMU

Greetings! I am trying to let qemu periodically print how many memory pages get dirtied since the last call. I added some code in qemu in the following way. I first of all create a thread right before main_loop (vl.c). Below is what this this thread does: void* report_dirty_pages(void* arg) {

Re: [Qemu-devel] [PATCH v10 10/19] vfio iommu: Add blocking notifier to notify DMA_UNMAP

On Sat, 29 Oct 2016 01:32:35 +0530 Kirti Wankhede wrote: > On 10/28/2016 6:10 PM, Alex Williamson wrote: > > On Fri, 28 Oct 2016 15:33:58 +0800 > > Jike Song wrote: > > > >> On 10/27/2016 05:29 AM, Kirti Wankhede wrote: > >>> Added blocking

Re: [Qemu-devel] [PATCH v5 2/2] qapi: allow blockdev-add for NFS

On 10/28/2016 12:09 PM, Ashijeet Acharya wrote: > Introduce new object 'BlockdevOptionsNFS' in qapi/block-core.json to > support blockdev-add for NFS network protocol driver. Also make a new > struct NFSServer to support tcp connection. > > Signed-off-by: Ashijeet Acharya

Re: [Qemu-devel] [PATCH v10 10/19] vfio iommu: Add blocking notifier to notify DMA_UNMAP

On 10/28/2016 6:10 PM, Alex Williamson wrote: > On Fri, 28 Oct 2016 15:33:58 +0800 > Jike Song wrote: > >> On 10/27/2016 05:29 AM, Kirti Wankhede wrote: >>> Added blocking notifier to IOMMU TYPE1 driver to notify vendor drivers >>> about DMA_UNMAP. >>> Exported two APIs

Re: [Qemu-devel] [PATCH v2 01/11] qapi: add qapi2texi script

On 10/28/2016 11:44 AM, Markus Armbruster wrote: > Marc-André Lureau writes: > >> As the name suggests, the qapi2texi script converts JSON QAPI >> description into a standalone texi file suitable for different target >> formats. >> >> It parses the following kind of

Re: [Qemu-devel] [QEMU PATCH v9 2/3] migration: migrate QTAILQ

On 10/28/2016 12:06 PM, Dr. David Alan Gilbert wrote: > * Jianjun Duan (du...@linux.vnet.ibm.com) wrote: >> Currently we cannot directly transfer a QTAILQ instance because of the >> limitation in the migration code. Here we introduce an approach to >> transfer such structures. We created

Re: [Qemu-devel] [QEMU PATCH v9 2/3] migration: migrate QTAILQ

* Jianjun Duan (du...@linux.vnet.ibm.com) wrote: > Currently we cannot directly transfer a QTAILQ instance because of the > limitation in the migration code. Here we introduce an approach to > transfer such structures. We created VMStateInfo vmstate_info_qtailq > for QTAILQ. Similar VMStateInfo

Re: [Qemu-devel] [PATCH v3] block/vxhs: Add Veritas HyperScale VxHS block device support

On Fri, Oct 28, 2016 at 12:44:27AM -0700, Ashish Mittal wrote: > This patch adds support for a new block device type called "vxhs". > Source code for the qnio library that this code loads can be downloaded from: > https://github.com/MittalAshish/libqnio.git > > Sample command line using the JSON

Re: [Qemu-devel] [PATCH v2 0/7] blockjobs: preliminary refactoring work, Pt 1

On Thu, Oct 27, 2016 at 12:06:54PM -0400, John Snow wrote: > This is a follow-up to patches 2-6 of: > [PATCH v2 00/11] blockjobs: Fix transactional race condition > > That series started trying to refactor blockjobs with the goal of > internalizing BlockJob state as a side effect of having gone

Re: [Qemu-devel] [PULL 0/6] ui patch queue.

ror in simple backend (2016-10-27 > 19:24:15 +0100) > > are available in the git repository at: > > git://git.kraxel.org/qemu tags/pull-ui-20161028-1 > > for you to fetch changes up to 8ddc5bf9e5de51c2a4842c01dd3a97f5591776fd

[Qemu-devel] [PATCH Risu 3/3] Initial implemention for ppc64le

From: Jose Ricardo Ziviani - This commit adds the initial implementation of ppc64le support (client and server) for Risu. Signed-off-by: Jose Ricardo Ziviani --- configure | 6 ++ risu_ppc64le.c | 92 ++

Re: [Qemu-devel] [PATCH] tcg: correct 32-bit tcg_gen_ld8s_i64 sign-extension

On 10/28/2016 05:42 AM, Peter Maydell wrote: On 28 October 2016 at 00:35, Joseph Myers wrote: The version of tcg_gen_ld8s_i64 for 32-bit systems does a load into the low part of the return value - then attempts a sign extension into the high part, but wrongly sets the

[Qemu-devel] [PATCH Risu 2/3] Isolates Arm specific subroutines out from risugen main file

- In order to make risugen more agnostic to different archs, a new module is created to handle Arm instrunctions. This module, as well as the Power module, is dinamically called based on the .mode directive defined in each risu file. Signed-off-by: Jose Ricardo Ziviani

[Qemu-devel] [PATCH Risu 0/3] Risu support for PPC64LE

From: Jose Ricardo Ziviani This is an initial effort to have RISU working for PPC64LE. I also made some changes to isolate risugen, creating two modules (risugen_arm.pm and risugen_ppc64le.pm) to implement specific instructions in it. Suggestions are welcome! :) TODOS: -

Re: [Qemu-devel] [Xen-devel] [PATCH v2] xenfv: set has_acpi_build to false

On Fri, 28 Oct 2016, Wei Liu wrote: > On Thu, Oct 27, 2016 at 11:58:29AM -0700, Stefano Stabellini wrote: > > On Thu, 27 Oct 2016, Sander Eikelenboom wrote: > > > Thursday, October 27, 2016, 3:51:09 PM, you wrote: > > > > > > > Xen's toolstack is in charge of building ACPI tables. Skip ACPI table

Re: [Qemu-devel] [PATCH v2 3/3] target-m68k: shift ops manage word and byte operands

On 10/27/2016 02:43 PM, Laurent Vivier wrote: +static inline void shift_reg(DisasContext *s, uint16_t insn, int opsize) { -TCGv reg, s32; -TCGv_i64 t64, s64; int logical = insn & 8; +int left = insn & 0x100; +int bits = opsize_bytes(opsize) * 8; +TCGv reg =

Re: [Qemu-devel] [PATCH v3] block: Turn on "unmap" in active commit

On Tue, Sep 27, 2016 at 07:14:52PM +0800, Fam Zheng wrote: > We already specified BDRV_O_UNMAP when opening images in 'qemu-img > commit', but didn't turn on the "unmap" in the active commit job. This > patch fixes that so that zeroed clusters in top image can be discarded > which is desired in

Re: [Qemu-devel] [PATCH v2 1/1] block/gluster: memory usage: use one glfs instance per volume

On Thu, Oct 27, 2016 at 08:54:50PM +0530, Prasanna Kumar Kalever wrote: > Currently, for every drive accessed via gfapi we create a new glfs > instance (call glfs_new() followed by glfs_init()) which could consume > memory in few 100 MB's, from the table below it looks like for each > instance

[Qemu-devel] [PATCH v2 1/4] target-ppc: Implement bcdcfn. instruction

bcdcfn. converts from National numeric format to BCD. National format uses a byte to represent a digit where the most significant nibble is always 0x3 and the least sign. nibbles is the digit itself. Signed-off-by: Jose Ricardo Ziviani --- target-ppc/helper.h

[Qemu-devel] [PATCH v2 0/4] POWER9 TCG enablements - BCD functions part I

v2: - implements all fixes and suggestions This serie contains 4 new instructions for POWER9 ISA3.0 bcdcfn.: Decimal Convert From National bcdctn.: Decimal Convert To National bcdcfz.: Decimal Convert From Zoned bcdctz.: Decimal Convert to Zoned Jose Ricardo Ziviani (4): target-ppc:

[Qemu-devel] [PATCH v2 3/4] target-ppc: Implement bcdcfz. instruction

bcdcfz. converts from Zoned numeric format to BCD. Zoned format uses a byte to represent a digit where the most significant nibble is 0x3 or 0xf, depending on the preferred signal. Signed-off-by: Jose Ricardo Ziviani --- target-ppc/helper.h | 1 +

[Qemu-devel] [PATCH v3 0/2] Qemu: gdbstub: fix vCont

This small patchset fixes the incorrect behaviour of the vCont command in the gdb stub. The first patch, as suggested be Paolo, refactors some code. The most visible change is that it moves vm_start to cpus.c The second one fixes the incorrect behaviour of the vCont command. Previously,

[Qemu-devel] [PATCH v2 2/4] target-ppc: Implement bcdctn. instruction

bcdctn. converts from BCD to National numeric format. National format uses a byte to represent a digit where the most significant nibble is always 0x3 and the least sign. nibbles is the digit itself. Signed-off-by: Jose Ricardo Ziviani --- target-ppc/helper.h

[Qemu-devel] [PATCH v2 4/4] target-ppc: Implement bcdctz. instruction

bcdctz. converts from BCD to Zoned numeric format. Zoned format uses a byte to represent a digit where the most significant nibble is 0x3 or 0xf, depending on the preferred signal. Signed-off-by: Jose Ricardo Ziviani --- target-ppc/helper.h | 1 +

[Qemu-devel] [PATCH v3 1/2] move vm_start to cpus.c

This patch: * moves vm_start to cpus.c . * exports qemu_vmstop_requested, since it's needed by vm_start . * extracts vm_prepare_start from vm_start; it does what vm_start did, except restarting the cpus. vm_start now calls vm_prepare_start. * moves the call to qemu_clock_enable away from

[Qemu-devel] [PATCH v3 2/2] gdbstub: Fix vCont behaviour

When GDB issues a "vCont", QEMU was not handling it correctly when multiple VCPUs are active. For vCont, for each thread (VCPU), it can be specified whether to single step, continue or stop that thread. The default is to stop a thread. However, when (for example) "vCont;s:2" is issued, all VCPUs

[Qemu-devel] [PATCH v5 2/2] qapi: allow blockdev-add for NFS

Introduce new object 'BlockdevOptionsNFS' in qapi/block-core.json to support blockdev-add for NFS network protocol driver. Also make a new struct NFSServer to support tcp connection. Signed-off-by: Ashijeet Acharya --- qapi/block-core.json | 74

[Qemu-devel] [PATCH v5 1/2] block/nfs: Introduce runtime_opts in NFS

Make NFS block driver use various fine grained runtime_opts. Set .bdrv_parse_filename() to nfs_parse_filename() and introduce two new functions nfs_parse_filename() and nfs_parse_uri() to help parsing the URI. Add a new option "server" which then accepts a new struct NFSServer. "host" is supported

[Qemu-devel] [PATCH v5 0/2] allow blockdev-add for NFS

Previously posted series patches: v4: https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg07449.html v3: https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg06903.html v2: https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg05844.html v1:

Re: [Qemu-devel] [libvirt-users] pci-assign fails with read error on config-space file

On Fri, 28 Oct 2016 11:25:55 -0400 Laine Stump wrote: > On 10/28/2016 07:28 AM, Henning Schild wrote: > > Hey, > > > > i am running an unusual setup where i assign pci devices behind the > > back of libvirt. I have two options to do that: > > 1. a wrapper script for qemu that

[Qemu-devel] [PATCH v3 4/4] pc: memhp: enable nvdimm device hotplug

_GPE.E04 is dedicated for nvdimm device hotplug Signed-off-by: Xiao Guangrong --- docs/specs/acpi_mem_hotplug.txt | 3 +++ hw/acpi/memory_hotplug.c | 31 +++ hw/i386/acpi-build.c | 7 +++

[Qemu-devel] [PATCH v3 3/4] nvdimm acpi: introduce _FIT

_FIT is required for hotplug support, guest will inquire the updated device info from it if a hotplug event is received As FIT buffer is not completely mapped into guest address space, so a new function, Read FIT whose UUID is UUID 648B9CF2-CDA1-4312-8AD9-49C4AF32BD62, handle 0x1, function

[Qemu-devel] [PATCH v3 2/4] nvdimm acpi: introduce fit buffer

The buffer is used to save the FIT info for all the presented nvdimm devices which is updated after the nvdimm device is plugged or unplugged. In the later patch, it will be used to construct NVDIMM ACPI _FIT method which reflects the presented nvdimm devices after nvdimm hotplug As FIT buffer

Re: [Qemu-devel] [PATCH v2 1/1] block/gluster: memory usage: use one glfs instance per volume

On Fri, Oct 28, 2016 at 12:44:24PM +0200, Niels de Vos wrote: > On Thu, Oct 27, 2016 at 08:54:50PM +0530, Prasanna Kumar Kalever wrote: > > Currently, for every drive accessed via gfapi we create a new glfs > > instance (call glfs_new() followed by glfs_init()) which could consume > > memory in

[Qemu-devel] [PATCH v3 1/4] nvdimm acpi: prebuild nvdimm devices for available slots

For each NVDIMM present or intended to be supported by platform, platform firmware also exposes an ACPI Namespace Device under the root device So it builds nvdimm devices for all slots to support vNVDIMM hotplug Reviewed-by: Stefan Hajnoczi Signed-off-by: Xiao Guangrong

[Qemu-devel] [PATCH v3 0/4] nvdimm: hotplug support

It is based on my previous patchset, "[PATCH 0/8] nvdimm acpi: bug fix and cleanup", these two patchset are against commit dea651a95af6dad099 (intel-iommu: Check IOAPIC's Trigger Mode against the one in IRTE) on pci branch of Michael's git tree and can be found at:

Re: [Qemu-devel] [PULL 00/18] M68k part2 patches

On 28 October 2016 at 09:48, Laurent Vivier wrote: > The following changes since commit 835f3d24b42fcbeca5c49048994a4e5d0fe905c5: > > Merge remote-tracking branch 'remotes/kraxel/tags/pull-audio-20161027-1' > into staging (2016-10-27 17:24:29 +0100) > > are available in the

[Qemu-devel] [PATCH 5/6] tests/docker/docker.py: expand images command

Modern docker cli commands can filter by repository but as we want to work on all instances do this by hand in python: /tests/docker/docker.py images --repo qemu Will return a space delimited list for the benefit of our Makefile recipes. Signed-off-by: Alex Bennée

[Qemu-devel] [PULL 22/23] clean-up: removed duplicate #includes

From: Anand J Some files contain multiple #includes of the same header file. Removed most of those unnecessary duplicate entries using scripts/clean-includes. Reviewed-by: Thomas Huth Signed-off-by: Anand J Signed-off-by:

Re: [Qemu-devel] [RFC] powernv: CPU compatibility modes don't make sense for powernv

On Fri, 2016-10-28 at 18:40 +0200, Cédric Le Goater wrote: >  > It makes perfect sense. The "cpu-version" property is for PAPR, not > for OPAL. > hostboot and skiboot put SPR_PVR in this property.  > > I will be careful using 'CPU_CORE(pc)->nr_threads' in the ICP patches > also.  No, the

Re: [Qemu-devel] [PATCH v2 3/6] target-ppc: add vrldnmi and vrlwmi instructions

On 10/27/2016 06:30 PM, David Gibson wrote: How about something like this in target-ppc/cpu.h #define FUNC_MASK(name, ret_type, size, max_val) \ static inline ret_type name (uint##size##_t start,\ uint##size##_t end)

Re: [Qemu-devel] [RFC] powernv: CPU compatibility modes don't make sense for powernv

On 10/28/2016 06:46 PM, Benjamin Herrenschmidt wrote: > On Fri, 2016-10-28 at 18:40 +0200, Cédric Le Goater wrote: >> >> It makes perfect sense. The "cpu-version" property is for PAPR, not >> for OPAL. >> hostboot and skiboot put SPR_PVR in this property. >> >> I will be careful using

[Qemu-devel] [PATCH 1/6] tests/docker/Makefile.include: fix diff-index call

The whole thing is wrapped inside a call quiet-command as well as being the actual call taking a --quiet argument so the redirect is superfluous. For reasons I have yet to determine this also seems to be causing the source preparation step to skip stashing work tree stuff. Signed-off-by: Alex

Re: [Qemu-devel] [RFC] powernv: CPU compatibility modes don't make sense for powernv

On 10/28/2016 04:05 AM, David Gibson wrote: > powernv has some code (derived from the spapr equivalent) used in device > tree generation which depends on the CPU's compatibility mode / logical > PVR. However, compatibility modes don't make sense on powernv - at least > not as a property

[Qemu-devel] [PATCH 7/8] acpi nvdimm: rename result_size to dsm_out_buf_siz

Rename it as dsm_out_buf_siz is more descriptive Suggested-by: Igor Mammedov Signed-off-by: Xiao Guangrong --- hw/acpi/nvdimm.c | 15 --- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/hw/acpi/nvdimm.c

[Qemu-devel] [PATCH 4/6] tests/docker/Makefile: Add a rule for Debian user images

This allows you to create Debian images powered by a qemu linux-user binary. Later patches will list these in the help file but for now: make docker-image-debian-stable-arm64 Signed-off-by: Alex Bennée --- tests/docker/Makefile.include | 16 1 file

[Qemu-devel] [PATCH 6/6] tests/docker/Makefile.include: expand docker help text

No we can query what has and hasn't been built we can make this list available in the help text. This is useful as some of the bootstrapped builds can take some time to build. Signed-off-by: Alex Bennée --- tests/docker/Makefile.include | 11 +-- 1 file changed,

Re: [Qemu-devel] [PATCH v2 01/11] qapi: add qapi2texi script

Marc-André Lureau writes: > As the name suggests, the qapi2texi script converts JSON QAPI > description into a standalone texi file suitable for different target > formats. > > It parses the following kind of blocks with some little variations: > > ## > # =

[Qemu-devel] [PATCH 4/8] acpi nvdimm: fix ARG3 conflict

As ARG3 is a reserved name, we rename it to FARG Suggested-by: Igor Mammedov Signed-off-by: Xiao Guangrong --- hw/acpi/nvdimm.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/hw/acpi/nvdimm.c b/hw/acpi/nvdimm.c

[Qemu-devel] [PATCH 0/6] Expand the building of qemu-user docker images

Hi Fam, These are a little bit of a work in progress so maybe not all ready to be taken yet although review would be welcome. This adds some tweaks to allow us to build the cross-arch debian images with direct make invocations and then see which images we can test against from the "make docker"

[Qemu-devel] [PATCH 2/6] tests/docker/test-user: a simple linux-user test

This is useful for checking an appropriately updated cross-arch docker actually starts without having to do a full build. Signed-off-by: Alex Bennée --- tests/docker/test-user | 18 ++ 1 file changed, 18 insertions(+) create mode 100755

[Qemu-devel] [PATCH 2/8] acpi nvdimm: fix device physical address base

According to ACPI 6.0 spec, "Memory Device Physical Address Region Base" in memdev is defined as "This field provides the Device Physical Address base of the region". This field should be zero in our case Signed-off-by: Xiao Guangrong --- hw/acpi/nvdimm.c | 5

[Qemu-devel] [PATCH 3/6] tests/docker: add optional libs to travis.docker

In our .travis.yml we install a bunch of extra libraries which are not part of the packaged QEMU's builddeps. We include them here to make our docker container more closely match the state of the system after docker has installed the rest of the build dependencies. Signed-off-by: Alex Bennée

[Qemu-devel] [PATCH 6/8] nvdimm acpi: compile nvdimm acpi code arch-independently

As the arch dependent info, TARGET_PAGE_SIZE, has been dropped from nvdimm acpi code, it can be compiled arch-independently Signed-off-by: Xiao Guangrong --- hw/acpi/Makefile.objs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[Qemu-devel] [PATCH 8/8] nvdimm acpi: use common macros instead of magic names

There are some names repeatedly used in acpi code, define them as macros to refine the code Suggested-by: Igor Mammedov Signed-off-by: Xiao Guangrong --- hw/acpi/nvdimm.c | 83 +--- 1 file

[Qemu-devel] [PATCH 3/8] acpi nvdimm: fix OperationRegion definition

Based on ACPI spec: RegionOffset := TermArg => Integer However, Named object is not a TermArg. This patch moves OperationRegion to NCAL() and uses localX as its RegionOffset Suggested-by: Igor Mammedov Signed-off-by: Xiao Guangrong ---

[Qemu-devel] [PATCH 5/8] acpi nvdimm: fix Arg6 usage

As the function only has 5 args, we use local7 instead of it Suggested-by: Igor Mammedov Signed-off-by: Xiao Guangrong --- hw/acpi/nvdimm.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/hw/acpi/nvdimm.c

[Qemu-devel] [PATCH 1/8] acpi nvdimm: fix wrong buffer size returned by DSM method

Currently, 'RLEN' is the totally buffer size written by QEMU and it is ACPI internally used only. The buffer size returned to guest should not include 'RLEN' itself Signed-off-by: Xiao Guangrong --- hw/acpi/nvdimm.c | 3 ++- 1 file changed, 2 insertions(+), 1

[Qemu-devel] [PULL 21/23] scripts/clean-includes: added duplicate #include check

From: Anand J Enhance the clean-includes script to optionally check for duplicate #include entries. Script might output false positive entries as well. Such entries should not be removed. So if it finds any duplicate entries script will terminate with an exit status 1.

[Qemu-devel] [PATCH 0/8] nvdimm acpi: bug fix and cleanup

Thanks to Igor's suggestion, this patchset fixes some bugs in NVDIMM ACPI, also it refines the nvdimm code slightly Xiao Guangrong (8): acpi nvdimm: fix wrong buffer size returned by DSM method acpi nvdimm: fix device physical address base acpi nvdimm: fix OperationRegion definition acpi

  1   2   3   >