Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Tue, Aug 16, 2016 at 04:52:30AM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Tuesday, August 16, 2016 12:17 PM > > > > On Tue, Aug 16, 2016 at 03:50:44AM +, Tian, Kevin wrote: > > > > From: Neo Jia [mailto:c...@nvidia.com] > > > > Sent: Tuesday, August 16,

Re: [Qemu-devel] [PATCH 3/3] ppc/pnv: add a PowerNVCPUCore object

On Tue, 2016-08-16 at 12:39 +1000, David Gibson wrote: > On Fri, Aug 05, 2016 at 11:15:37AM +0200, Cédric Le Goater wrote: > > > > This is largy inspired by sPAPRCPUCore with some simplification, no > > hotplug for instance. But the differences are small and the objects > > could possibly be

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

> From: Neo Jia [mailto:c...@nvidia.com] > Sent: Tuesday, August 16, 2016 12:17 PM > > On Tue, Aug 16, 2016 at 03:50:44AM +, Tian, Kevin wrote: > > > From: Neo Jia [mailto:c...@nvidia.com] > > > Sent: Tuesday, August 16, 2016 11:46 AM > > > > > > On Tue, Aug 16, 2016 at 12:30:25AM +,

Re: [Qemu-devel] [PATCH v3 1/5] target-ppc: add vector insert instructions

On Thu, Aug 11, 2016 at 01:06:44PM +0530, Rajalakshmi Srinivasaraghavan wrote: > The following vector insert instructions are added from ISA 3.0. > > vinsertb - Vector Insert Byte > vinserth - Vector Insert Halfword > vinsertw - Vector Insert Word > vinsertd - Vector Insert Doubleword > >

Re: [Qemu-devel] [PATCH v3 3/5] target-ppc: add vector count trailing zeros instructions

On Thu, Aug 11, 2016 at 01:06:46PM +0530, Rajalakshmi Srinivasaraghavan wrote: > The following vector count trailing zeros instructions are > added from ISA 3.0. > > vctzb - Vector Count Trailing Zeros Byte > vctzh - Vector Count Trailing Zeros Halfword > vctzw - Vector Count Trailing Zeros Word

Re: [Qemu-devel] [PATCH v3 2/5] target-ppc: add vector extract instructions

On Thu, Aug 11, 2016 at 01:06:45PM +0530, Rajalakshmi Srinivasaraghavan wrote: > The following vector extract instructions are added from ISA 3.0. > > vextractub - Vector Extract Unsigned Byte > vextractuh - Vector Extract Unsigned Halfword > vextractuw - Vector Extract Unsigned Word > vextractd

Re: [Qemu-devel] [PATCH v3 4/5] target-ppc: add vector bit permute doubleword instruction

On Thu, Aug 11, 2016 at 01:06:47PM +0530, Rajalakshmi Srinivasaraghavan wrote: > Add vbpermd instruction from ISA 3.0. > > Signed-off-by: Rajalakshmi Srinivasaraghavan > --- > target-ppc/helper.h |1 + > target-ppc/int_helper.c | 22

Re: [Qemu-devel] [PATCH v3 5/5] target-ppc: add vector permute right indexed instruction

On Thu, Aug 11, 2016 at 01:06:48PM +0530, Rajalakshmi Srinivasaraghavan wrote: > Add vpermr instruction from ISA 3.0. > > Signed-off-by: Rajalakshmi Srinivasaraghavan > --- > target-ppc/helper.h |1 + > target-ppc/int_helper.c | 23

[Qemu-devel] Virtio interaction with the physical device

Hi, I was trying to understand the flow of packets from the Guest OS to my NIC card, while using the Virtio paravirtualized drivers. (Qemu is not emulating the NIC) THis is as far as I have understood: { THe guest OS starts with a virtio nic: -net nic,model=virtio -net user -redir tcp:::22

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Tue, Aug 16, 2016 at 03:50:44AM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Tuesday, August 16, 2016 11:46 AM > > > > On Tue, Aug 16, 2016 at 12:30:25AM +, Tian, Kevin wrote: > > > > From: Neo Jia [mailto:c...@nvidia.com] > > > > Sent: Tuesday, August 16,

Re: [Qemu-devel] [PATCH for-2.7] slirp: Rename "struct arphdr" to "struct slirp_arphdr"

On 08/15/16 04:24, Thomas Huth wrote: struct arphdr is already used by the system headers on OpenBSD and thus QEMU does not compile here anymore. Fix it by renaming our struct to slirp_arphdr instead. Reported-by: Brad Smith Buglink: https://bugs.launchpad.net/qemu/+bug/1613133 Signed-off-by:

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

> From: Neo Jia [mailto:c...@nvidia.com] > Sent: Tuesday, August 16, 2016 11:46 AM > > On Tue, Aug 16, 2016 at 12:30:25AM +, Tian, Kevin wrote: > > > From: Neo Jia [mailto:c...@nvidia.com] > > > Sent: Tuesday, August 16, 2016 3:59 AM > > > > > > > > > > > For NVIDIA vGPU solution we need to

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Tue, Aug 16, 2016 at 12:30:25AM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Tuesday, August 16, 2016 3:59 AM > > > > > > > > For NVIDIA vGPU solution we need to know all devices assigned to a VM in > > > > one shot to commit resources of all vGPUs assigned to

Re: [Qemu-devel] [PATCH v4] docs: add cpu-hotplug.txt

Hi Bharata, At 08/16/2016 11:31 AM, Bharata B Rao wrote: On Tue, Aug 16, 2016 at 11:07:41AM +0800, Dou Liyang wrote: This document describes how to use cpu hotplug in QEMU. Signed-off-by: Andrew Jones Signed-off-by: Dou Liyang --- Change log v3

Re: [Qemu-devel] [PATCH v4] docs: add cpu-hotplug.txt

On Tue, Aug 16, 2016 at 11:07:41AM +0800, Dou Liyang wrote: > This document describes how to use cpu hotplug in QEMU. > > Signed-off-by: Andrew Jones > Signed-off-by: Dou Liyang > --- > Change log v3 -> v4 > From David's advice > 1. add spapr

[Qemu-devel] [PATCH v4] docs: add cpu-hotplug.txt

This document describes how to use cpu hotplug in QEMU. Signed-off-by: Andrew Jones Signed-off-by: Dou Liyang --- Change log v3 -> v4 From David's advice 1. add spapr examples 2. Fix some comment From drew's advice 1. Fix some

[Qemu-devel] enhancements to the open firmware video driver

I thought of a way for the video driver you made to be expandable without having to be recompiled. The user can specify additions resolutions like this: -prom-env "resolutions=1200x700,1280x600,1440x700" The video driver can then look in the /options node and use its resolutions property to

Re: [Qemu-devel] [PATCH 3/3] ppc/pnv: add a PowerNVCPUCore object

On Fri, Aug 05, 2016 at 11:15:37AM +0200, Cédric Le Goater wrote: > This is largy inspired by sPAPRCPUCore with some simplification, no > hotplug for instance. But the differences are small and the objects > could possibly be merged. > > A set of PowerNVCPUCore objects is added to the PnvChip and

Re: [Qemu-devel] [PATCH 2/3] ppc/pnv: add a PnvChip object

On Fri, Aug 05, 2016 at 11:15:36AM +0200, Cédric Le Goater wrote: > This is is an abstraction of a P8 chip which is a set of cores plus > other 'units', like the pervasive unit, the interrupt controller, the > memory controller, the on-chip microcontroller, etc. The whole can be > seen as a

Re: [Qemu-devel] [PATCH 2/3] ppc/pnv: add a PnvChip object

On Sat, Aug 06, 2016 at 08:43:21AM +1000, Benjamin Herrenschmidt wrote: > On Fri, 2016-08-05 at 18:48 +0200, Cédric Le Goater wrote: > > The core initialization should be ok but building the device  > > tree might be a bit of a burden if we have to 'cast' in the chip  > > type we need. We will

[Qemu-devel] [PATCH v4] ui/cocoa.m: Make a better about dialog

The about dialog in QEMU on Mac OS X is very plain and unhelpful. This patch makes the about dialog look a lot better and have some descriptive information on what version of QEMU the user is running. Signed-off-by: John Arbuckle --- version 4 changes: Moved

Re: [Qemu-devel] [PATCH 1/3] ppc/pnv: add skeleton PowerNV platform

On Fri, Aug 05, 2016 at 11:15:35AM +0200, Cédric Le Goater wrote: > From: Benjamin Herrenschmidt > > The goal is to emulate a PowerNV system at the level of the skiboot > firmware, which loads the OS and provides some runtime services. Power > Systems have a lower

Re: [Qemu-devel] [PATCH v9 00/11] Provide a QOM-based authorization API

On Mon, 08/15 14:07, Daniel P. Berrange wrote: > > [snip] > > This and all the other errors reported here are all *pre-existing* > problems. It seems this bot does not have git rename detection turned > on so is reporting all these problems in file-renames my patches did. > > The bot needs to

Re: [Qemu-devel] [PATCH v10 00/11] Provide a QOM-based authorization API

On Mon, 08/15 07:46, no-re...@ec2-52-6-146-230.compute-1.amazonaws.com wrote: > /tmp/qemu-test/src/util/authz-pam.c:26:32: warning: security/pam_appl.h: No > such file or directory Hi Daniel, I think there is an unfortunate CONFIG_ var collision you probably want to avoid: $ git grep

Re: [Qemu-devel] ARM MCU Target Structure Question

On Mon, Aug 15, 2016 at 3:18 AM, Peter Maydell wrote: > This broadly matches the directory arrangement principles used > by the Linux kernel sources, which is where we've borrowed it from. > Ok - I'll pursue the current directory structure. ​Thanks,​ ​~C​

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

> From: Neo Jia [mailto:c...@nvidia.com] > Sent: Tuesday, August 16, 2016 7:24 AM > > > > > > > > > > > > > > > > > For NVIDIA vGPU solution we need to know all devices assigned to a > > > > > > VM in > > > > > > one shot to commit resources of all vGPUs assigned to a VM along > > > > > > with

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

> From: Neo Jia [mailto:c...@nvidia.com] > Sent: Tuesday, August 16, 2016 3:59 AM > > On Mon, Aug 15, 2016 at 09:38:52AM +, Tian, Kevin wrote: > > > From: Kirti Wankhede [mailto:kwankh...@nvidia.com] > > > Sent: Saturday, August 13, 2016 8:37 AM > > > > > > > > > > > > On 8/13/2016 2:46 AM,

[Qemu-devel] [PATCH 0/2] Bitmap for recovery of postcopy migration from n/w failure

A new bitmap to keep in track the pages that were lost in case there was a network failure during postcopy. The bitmap is used to req for those lost pages towards the end of migration. Md Haris Iqbal (2): Migration: New bitmap for postcopy migration failure Migration: Request lost pages (due

[Qemu-devel] [PATCH 2/2] Migration: Request lost pages (due to n/w failure) from source

Signed-off-by: Md Haris Iqbal --- include/migration/migration.h | 7 +++ migration/migration.c | 2 ++ migration/ram.c | 35 +++ migration/savevm.c| 19 +++ 4 files changed, 63

[Qemu-devel] [PATCH 1/2] Migration: New bitmap for postcopy migration failure

Signed-off-by: Md Haris Iqbal --- include/migration/migration.h | 3 +++ migration/migration.c | 8 -- migration/postcopy-ram.c | 2 +- migration/ram.c | 63 ++- 4 files changed, 72 insertions(+), 4

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

> From: Alex Williamson [mailto:alex.william...@redhat.com] > Sent: Tuesday, August 16, 2016 6:48 AM > > On Mon, 15 Aug 2016 12:59:08 -0700 > Neo Jia wrote: > > > On Mon, Aug 15, 2016 at 09:38:52AM +, Tian, Kevin wrote: > > > > From: Kirti Wankhede

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Mon, Aug 15, 2016 at 04:47:41PM -0600, Alex Williamson wrote: > On Mon, 15 Aug 2016 12:59:08 -0700 > Neo Jia wrote: > > > On Mon, Aug 15, 2016 at 09:38:52AM +, Tian, Kevin wrote: > > > > From: Kirti Wankhede [mailto:kwankh...@nvidia.com] > > > > Sent: Saturday, August 13,

Re: [Qemu-devel] [PATCH COLO-Frame v18 00/34] COarse-grain LOck-stepping(COLO) Virtual Machines for Non-stop Service (FT)

On 08/03/2016 08:25 PM, zhanghailiang wrote: It is based on '[PATCH v24 00/12] Block replication for continuous checkpoints' series. The complete codes can be found from the link: https://github.com/coloft/qemu/commits/colo-v3.1-periodic-mode 404 NOT FOUND. Would you like to upload it again

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Mon, Aug 15, 2016 at 04:52:39PM -0600, Alex Williamson wrote: > On Mon, 15 Aug 2016 15:09:30 -0700 > Neo Jia wrote: > > > On Mon, Aug 15, 2016 at 09:59:26AM -0600, Alex Williamson wrote: > > > On Mon, 15 Aug 2016 09:38:52 + > > > "Tian, Kevin"

Re: [Qemu-devel] [PATCH v3] balloon: Fix failure of updating guest memory status

On Fri, Aug 05, 2016 at 01:36:32PM +0200, Ladi Prosek wrote: > The stats_vq_elem field keeps track of the state of the balloon stats > virtqueue protocol but it wasn't preserved across migrations, resulting > in losing guest memory status updates on the receiving VM. > > This commit adds a new VM

[Qemu-devel] [PATCH] virtio-balloon: stats vq migration spec compliance

virtio spec says that devices must not touch VQs before DRIVER_OK is set. Additionally, balloon must not touch stats VQ unless the stats feature bit has been negotiated. Cc: Ladi Prosek Signed-off-by: Michael S. Tsirkin --- hw/virtio/virtio-balloon.c | 4

Re: [Qemu-devel] [PATCH V1 1/1] arm64: Add an option to turn on/off host-backed vPMU support

On 8/15/16 11:13, Peter Maydell wrote: > On 13 August 2016 at 06:52, Wei Huang wrote: >> This patch adds a pmu=[on/off] option to enable/disable host vPMU >> support in guest VM. There are several reasons to justify this option. >> First, host-backed vPMU can be problematic for

Re: [Qemu-devel] [PATCH for-2.7 0/4] virtio-balloon: fix stats vq migration

On Mon, Aug 15, 2016 at 09:51:21PM +0200, Gaudenz Steinlin wrote: > Stefan Hajnoczi writes: > > > Gaudenz Steinlin reported that virtqueue_pop() > > terminates > > QEMU because the virtqueue size is exceeded following the CVE-2016-5403 > > fix. I > >

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Mon, 15 Aug 2016 15:09:30 -0700 Neo Jia wrote: > On Mon, Aug 15, 2016 at 09:59:26AM -0600, Alex Williamson wrote: > > On Mon, 15 Aug 2016 09:38:52 + > > "Tian, Kevin" wrote: > > > > > > From: Kirti Wankhede [mailto:kwankh...@nvidia.com] > > > >

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Mon, 15 Aug 2016 12:59:08 -0700 Neo Jia wrote: > On Mon, Aug 15, 2016 at 09:38:52AM +, Tian, Kevin wrote: > > > From: Kirti Wankhede [mailto:kwankh...@nvidia.com] > > > Sent: Saturday, August 13, 2016 8:37 AM > > > > > > > > > > > > On 8/13/2016 2:46 AM, Alex

[Qemu-devel] [PATCH v4] fpu: add mechanism to check for invalid long double formats

All operations that take a floatx80 as an operand need to have their inputs checked for malformed encodings. In all of these cases, use the function floatx80_invalid_encoding to perform the check. If an invalid operand is found, raise an invalid operation exception, and then return either NaN (for

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Mon, Aug 15, 2016 at 09:59:26AM -0600, Alex Williamson wrote: > On Mon, 15 Aug 2016 09:38:52 + > "Tian, Kevin" wrote: > > > > From: Kirti Wankhede [mailto:kwankh...@nvidia.com] > > > Sent: Saturday, August 13, 2016 8:37 AM > > > > > > > > > > > > On 8/13/2016 2:46

Re: [Qemu-devel] [PATCH v3] fpu: add mechanism to check for invalid long double formats

Hi, Your series seems to have some coding style problems. See output below for more information: Message-id: 1471298004-5959-1-git-send-email-and...@andrewdutcher.com Subject: [Qemu-devel] [PATCH v3] fpu: add mechanism to check for invalid long double formats Type: series === TEST SCRIPT BEGIN

[Qemu-devel] [PATCH v3] fpu: add mechanism to check for invalid long double formats

All operations that take a floatx80 as an operand need to have their inputs checked for malformed encodings. In all of these cases, use the function floatx80_invalid_encoding to perform the check. If an invalid operand is found, raise an invalid operation exception, and then return either NaN (for

Re: [Qemu-devel] [PATCH v3] ui/cocoa.m: Make a better about dialog

On 29 July 2016 at 16:16, Programmingkid wrote: > The about dialog in QEMU on Mac OS X is very plain and unhelpful. This patch > makes the about dialog look a lot better and have some descriptive information > on what version of QEMU the user is running. > >

Re: [Qemu-devel] [PATCH] Revert "vhost-user: Attempt to fix a race with set_mem_table."

On Mon, Aug 15, 2016 at 04:15:08PM +0100, Peter Maydell wrote: > On 15 August 2016 at 14:35, Michael S. Tsirkin wrote: > > This reverts commit 28ed5ef16384f12500abd3647973ee21b03cbe23. > > > > I still think it's the right thing to do, but > > tests have been failing sporadically.

Re: [Qemu-devel] [PATCH V1 1/1] arm64: Add an option to turn on/off host-backed vPMU support

On 08/15/2016 05:09 AM, Andrew Jones wrote: > On Sat, Aug 13, 2016 at 12:52:50AM -0500, Wei Huang wrote: >> This patch adds a pmu=[on/off] option to enable/disable host vPMU >> support in guest VM. There are several reasons to justify this option. >> First, host-backed vPMU can be problematic

Re: [Qemu-devel] [PULL 0/2] xen-20160812-tag-2

On 13 August 2016 at 00:42, Stefano Stabellini wrote: > The following changes since commit 28b874429ba16e71e0caa46453f3a3e31efb3c51: > > Merge remote-tracking branch > 'remotes/amit-migration/tags/migration-for-2.7-7' into staging (2016-08-11 > 17:53:35 +0100) > > are

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Mon, Aug 15, 2016 at 09:38:52AM +, Tian, Kevin wrote: > > From: Kirti Wankhede [mailto:kwankh...@nvidia.com] > > Sent: Saturday, August 13, 2016 8:37 AM > > > > > > > > On 8/13/2016 2:46 AM, Alex Williamson wrote: > > > On Sat, 13 Aug 2016 00:14:39 +0530 > > > Kirti Wankhede

Re: [Qemu-devel] [PATCH for-2.7 0/4] virtio-balloon: fix stats vq migration

Stefan Hajnoczi writes: > Gaudenz Steinlin reported that virtqueue_pop() terminates > QEMU because the virtqueue size is exceeded following the CVE-2016-5403 fix. > I > have been unable to reproduce this or understand the root cause by code >

Re: [Qemu-devel] [PATCH for-2.7] pc-bios/optionrom: Fix OpenBSD build with better detection of linker emulation

On 8/15/2016 1:26 PM, Peter Maydell wrote: On 8 August 2016 at 17:11, Peter Maydell wrote: The various host OSes are irritatingly variable about the name of the linker emulation we need to pass to ld's -m option to build the i386 option ROMs. Instead of doing this

Re: [Qemu-devel] [PATCH] test-logging: don't hard-code paths in /tmp

Dear Peter, Peter Maydell writes: > On 15 July 2016 at 17:24, Sascha Silbe wrote: [...] >> Instead of hard-coding the paths, create a temporary directory using >> g_dir_make_tmp() and clean it up afterwards. >> >> Fixes: f6880b7f ("qemu-log:

Re: [Qemu-devel] [PATCH] target-arm: Fix lpae bit in FSR on an alignment fault

On 15 August 2016 at 18:48, Sergey Sorokin wrote: > If an alignment fault occurred and target EL is using AArch32, > then DFSR/IFSR bit LPAE[9] must be set correctly. > > Signed-off-by: Sergey Sorokin > --- > target-arm/op_helper.c | 2 +- > 1 file

Re: [Qemu-devel] [PULL for-2.7 0/1] Tracing patches

On 12 August 2016 at 11:48, Stefan Hajnoczi wrote: > The following changes since commit 28b874429ba16e71e0caa46453f3a3e31efb3c51: > > Merge remote-tracking branch > 'remotes/amit-migration/tags/migration-for-2.7-7' into staging (2016-08-11 > 17:53:35 +0100) > > are

[Qemu-devel] [PATCH] target-arm: Fix lpae bit in FSR on an alignment fault

If an alignment fault occurred and target EL is using AArch32, then DFSR/IFSR bit LPAE[9] must be set correctly. Signed-off-by: Sergey Sorokin --- target-arm/op_helper.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target-arm/op_helper.c

Re: [Qemu-devel] [Xen-devel] [RFC for 2.8 0/3] Drop support for 64 bit guests on 32 bit hosts

On Wed, 10 Aug 2016, Gerd Hoffmann wrote: > On Di, 2016-08-09 at 16:55 +0100, Alex Bennée wrote: > > Hi, > > > > I'm proposing for the 2.8 cycle we officially drop supporting 64 bit > > guests on 32 bit hosts. For most of the KVM targets it doesn't make > > any sense anyway and for TCG it makes

Re: [Qemu-devel] [Qemu-arm] [PATCH v2] hw/vfio/platform: Add Qualcomm Technologies, Inc HIDMA device support

On 8/15/2016 12:03 PM, Peter Maydell wrote: > Just cc'ing Eric on his new email address... > > thanks > -- PMM > > On 14 August 2016 at 16:42, Shanker Donthineni > wrote: >> This patch introduces the Qualcomm Technologies, Inc HIDMA device and >> allows passthrough the

Re: [Qemu-devel] [PATCH for-2.7] pc-bios/optionrom: Fix OpenBSD build with better detection of linker emulation

On 8 August 2016 at 17:11, Peter Maydell wrote: > The various host OSes are irritatingly variable about the name > of the linker emulation we need to pass to ld's -m option to > build the i386 option ROMs. Instead of doing this via a > CONFIG ifdef, check in configure

Re: [Qemu-devel] [PATCH V1 1/1] arm64: Add an option to turn on/off host-backed vPMU support

On Mon, 2016-08-15 at 11:12 -0500, Wei Huang wrote: > > Did you already try driving this with libvirt? It should work > > out of the box. > >  > > If you haven't, I will do it :) >  > No, I haven't. All tests were done based on command line to QEMU. :-) Fair enough :) I did some testing on my

Re: [Qemu-devel] [PATCH V1 1/1] arm64: Add an option to turn on/off host-backed vPMU support

On Mon, 2016-08-15 at 12:09 +0200, Andrew Jones wrote: > Hmm... so now if the user doesn't specify pmu=on (off by default) then we > silently disable it (I think that's a 2.6 compat issue), and if they do > specify pmu=on, but KVM doesn't support it, then it's silently disabled, > which isn't

Re: [Qemu-devel] [V2 0/6] AMD IOMMU interrupt remapping

On Mon, Aug 15, 2016 at 7:32 PM, David Kiarie wrote: > Hello all, > > The following patchset implements AMD-Vi interrupt remapping logic and > hooks it onto existing IR infrastucture. > > I have bundled this patchset together with the "Explicit SID for > IOAPIC"."Explicit

[Qemu-devel] [V2 4/6] hw/iommu: AMD IOMMU interrupt remapping

Introduce AMD IOMMU interrupt remapping and hook it onto the existing interrupt remapping infrastructure Signed-off-by: David Kiarie --- hw/i386/amd_iommu.c | 244 +++- hw/i386/amd_iommu.h | 4 +- 2 files changed, 243

[Qemu-devel] [V2 5/6] hw/acpi: report IOAPIC on IVRS

Report IOAPIC via IVRS which effectively allows linux AMD-Vi driver to enable interrupt remapping Signed-off-by: David Kiarie --- hw/i386/acpi-build.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c index 49bd183..c2559ff

[Qemu-devel] [V2 2/6] hw/i386: enforce SID verification

Platform device are now able to make interrupt request with explicit SIDs hence we can safely expect triggered AddressSpace ID to match the requesting ID Signed-off-by: David Kiarie --- hw/i386/intel_iommu.c | 77 ++- 1

[Qemu-devel] [V2 6/6] hw/iommu: share common code between IOMMUs

Enabling interrupt remapping with kernel_irqchip=on should result in an error for both VT-d and AMD-Vi Signed-off-by: David Kiarie --- hw/i386/intel_iommu.c | 9 - hw/i386/x86-iommu.c | 8 2 files changed, 8 insertions(+), 9 deletions(-) diff --git

[Qemu-devel] [V2 0/6] AMD IOMMU interrupt remapping

Hello all, The following patchset implements AMD-Vi interrupt remapping logic and hooks it onto existing IR infrastucture. I have bundled this patchset together with the "Explicit SID for IOAPIC"."Explicit SID for IOAPIC" functions to affiliate MSI routes with a requester ID and a PCI device

[Qemu-devel] [V2 1/6] hw/msi: Allow platform devices to use explicit SID

When using IOMMU platform devices like IOAPIC are required to make interrupt remapping requests using explicit SID.We affiliate an MSI route with a requester ID and a PCI device if present which ensures that platform devices can call IOMMU interrupt remapping code with explicit SID while

[Qemu-devel] [V2 3/6] hw/iommu: Prepare for AMD IOMMU interrupt remapping

Introduce macros and trace events for use in AMD IOMMU interrupt remapping Signed-off-by: David Kiarie --- hw/i386/amd_iommu.h | 38 -- 1 file changed, 16 insertions(+), 22 deletions(-) diff --git a/hw/i386/amd_iommu.h

Re: [Qemu-devel] [PATCH v3 RFC] block/vxhs: Initial commit to add Veritas HyperScale VxHS block device support

>> +/* >> + * Convert the json formatted command line into qapi. >> +*/ >> + >> +static int vxhs_parse_json(BlockdevOptionsVxHS *conf, >> + QDict *options, Error **errp) >> +{ ... >> +errno = EINVAL; >> +return -errno; >> +} > > Ewww this is really horrible

Re: [Qemu-devel] [PATCH] softfloat: Fix warn about implicit conversion from int to int8_t

On 10 August 2016 at 20:00, Aurelien Jarno wrote: > On 2016-08-10 14:55, Pranith Kumar wrote: >> Change the flag type to 'uint8_t' to fix the implicit conversion error. >> >> Signed-off-by: Pranith Kumar > Reviewed-by: Aurelien Jarno

Re: [Qemu-devel] [PATCH V1 1/1] arm64: Add an option to turn on/off host-backed vPMU support

On 13 August 2016 at 06:52, Wei Huang wrote: > This patch adds a pmu=[on/off] option to enable/disable host vPMU > support in guest VM. There are several reasons to justify this option. > First, host-backed vPMU can be problematic for cross-migration between > different SoC as

Re: [Qemu-devel] [PATCH V1 1/1] arm64: Add an option to turn on/off host-backed vPMU support

On 8/15/16 04:31, Andrea Bolognani wrote: > > On Sat, 2016-08-13 at 00:52 -0500, Wei Huang wrote: >> This patch adds a pmu=[on/off] option to enable/disable host vPMU >> support in guest VM. There are several reasons to justify this option. >> First, host-backed vPMU can be problematic for

Re: [Qemu-devel] [PATCH v2] hw/vfio/platform: Add Qualcomm Technologies, Inc HIDMA device support

Just cc'ing Eric on his new email address... thanks -- PMM On 14 August 2016 at 16:42, Shanker Donthineni wrote: > This patch introduces the Qualcomm Technologies, Inc HIDMA device and > allows passthrough the host HIDMA device to a guest machine using the >

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Mon, 15 Aug 2016 09:38:52 + "Tian, Kevin" wrote: > > From: Kirti Wankhede [mailto:kwankh...@nvidia.com] > > Sent: Saturday, August 13, 2016 8:37 AM > > > > > > > > On 8/13/2016 2:46 AM, Alex Williamson wrote: > > > On Sat, 13 Aug 2016 00:14:39 +0530 > > > Kirti

Re: [Qemu-devel] MTTCG status updates, benchmark results and KVM forum plans

On Mon, Aug 15, 2016 at 11:46:32 +0100, Alex Bennée wrote: > As far as I'm aware the following work is still ongoing: > > Emilo: cmpxchg atomics > Alvise: LL/SC modelling I've been tinkering with an experimental patch to do proper LL/SC. The idea is to rely on hardware transactional memory, so

Re: [Qemu-devel] [PATCH v14 1/9] target-avr: AVR cores support is added.

I definitely fixed ask your comments from previous review. But as it seems I have done a terrible mistake sending wrong patches. Sorry. On Mon, Aug 15, 2016, 6:46 PM Peter Maydell wrote: > On 15 August 2016 at 16:31, Michael Rolnik wrote: > > I

Re: [Qemu-devel] [PATCH v14 1/9] target-avr: AVR cores support is added.

On 15 August 2016 at 16:31, Michael Rolnik wrote: > I remember I did it. So it seems to be a wrong review. Well, it's definitely still in the wrong place in the v14 patchset you sent out: http://patchwork.ozlabs.org/patch/654143/ Did you send out the wrong patchset by mistake?

[Qemu-devel] [PATCH] aarch64: use TSX for ldrex/strex

Configure with --extra-cflags="-mrtm" Signed-off-by: Emilio G. Cota --- linux-user/main.c | 5 +++-- target-arm/helper-a64.c| 42 ++ target-arm/helper-a64.h| 4 target-arm/translate-a64.c | 15 +-- 4

Re: [Qemu-devel] [PATCH v14 9/9] target-avr: adding instruction decoder

On 29 July 2016 at 16:32, Michael Rolnik wrote: > Signed-off-by: Michael Rolnik > --- > target-avr/Makefile.objs |1 + > target-avr/cpugen/src/.cpugen.cpp.swp | Bin 0 -> 24576 bytes What is this binary ? It looks from the filename like

Re: [Qemu-devel] [PATCH v14 0/9] 8bit AVR cores

On 29 July 2016 at 16:32, Michael Rolnik wrote: > This series of patches adds 8bit AVR cores to QEMU. > All instruction, except BREAK/DES/SPM/SPMX, are implemented. Not fully tested > yet. > However I was able to execute simple code with functions. e.g fibonacci >

Re: [Qemu-devel] [PATCH v14 3/9] target-avr: adding a sample AVR board

On 29 July 2016 at 16:32, Michael Rolnik wrote: > Signed-off-by: Michael Rolnik > --- > MAINTAINERS | 6 +++ > hw/avr/Makefile.objs | 21 + > hw/avr/sample.c | 117 > +++ > 3 files

Re: [Qemu-devel] [PATCH v14 1/9] target-avr: AVR cores support is added.

I remember I did it. So it seems to be a wrong review. On Mon, Aug 15, 2016, 6:28 PM Peter Maydell wrote: > On 29 July 2016 at 16:32, Michael Rolnik wrote: > > 1. basic CPU structure > > 2. registers > > 3. no instructions > > 4.

Re: [Qemu-devel] [PATCH v14 2/9] target-avr: adding AVR CPU features/flavors

Richard. Please stop reviewing it. It seems to be a wrong review. On Mon, Aug 15, 2016, 6:31 PM Peter Maydell wrote: > On 29 July 2016 at 16:32, Michael Rolnik wrote: > > Signed-off-by: Michael Rolnik > > --- > >

Re: [Qemu-devel] [PATCH v14 2/9] target-avr: adding AVR CPU features/flavors

On 29 July 2016 at 16:32, Michael Rolnik wrote: > Signed-off-by: Michael Rolnik > --- > target-avr/cpu.c | 319 > +-- > target-avr/cpu.h | 52 - > target-avr/machine.c | 28 ++--- > 3 files

Re: [Qemu-devel] [PATCH v14 1/9] target-avr: AVR cores support is added.

On 29 July 2016 at 16:32, Michael Rolnik wrote: > 1. basic CPU structure > 2. registers > 3. no instructions > 4. saving sreg, rampD, rampX, rampY, rampD, eind in HW representation > > Signed-off-by: Michael Rolnik > diff --git a/configure

Re: [Qemu-devel] [PATCH] Revert "vhost-user: Attempt to fix a race with set_mem_table."

On 15 August 2016 at 14:35, Michael S. Tsirkin wrote: > This reverts commit 28ed5ef16384f12500abd3647973ee21b03cbe23. > > I still think it's the right thing to do, but > tests have been failing sporadically. > > Revert for now, and hope to fix it before the release. > > Cc:

Re: [Qemu-devel] [PATCH v2] fpu: add mechanism to check for invalid long double formats

On 14 August 2016 at 01:33, Andrew Dutcher wrote: > The macro require_valid_floatx80(value, status) will check for malformed > extended precision encodings, and if one is found, generate an > invalid-operation exception and return NaN. This check has been added to > the

[Qemu-devel] virnet: page allocation failure: order:0

Hello, this Sunday one of our virtual servers running linux-4.1.16 inside OpenStack using qemu "crashed" while doing a backup using rsync to a slow NFS server. Crash here means that the server became unresponsive to network traffic: - it was no longer able to contact the two LDAP servers - no ssh

Re: [Qemu-devel] [Patch v2 00/29] s390x CPU models: exposing features

On Mon, 15 Aug 2016 16:03:04 +0200 Christian Borntraeger wrote: > On 08/15/2016 04:00 PM, David Hildenbrand wrote: > > > > I'll wait a bit until sending out another series that fixes two minor style > > problems. > > > > What about > 80 chars per line. Is it okay for

Re: [Qemu-devel] [PATCH v10 00/11] Provide a QOM-based authorization API

Hi, Your 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. Message-id: 1471270945-19975-1-git-send-email-berra...@redhat.com Subject: [Qemu-devel] [PATCH v10 00/11] Provide a QOM-based

Re: [Qemu-devel] [PATCH v10 00/11] Provide a QOM-based authorization API

Hi, Your series seems to have some coding style problems. See output below for more information: Message-id: 1471270945-19975-1-git-send-email-berra...@redhat.com Subject: [Qemu-devel] [PATCH v10 00/11] Provide a QOM-based authorization API Type: series === TEST SCRIPT BEGIN === #!/bin/bash

[Qemu-devel] [PATCH v10 10/11] util: add QAuthZPAM object type for authorizing using PAM

Add an authorization backend that talks to PAM to check whether the user identity is allowed. This only uses the PAM account validation facility, which is essentially just a check to see if the provided username is permitted access. It doesn't use the authentication or session parts of PAM, since

[Qemu-devel] [PATCH v10 08/11] util: add QAuthZSimple object type for a simple access control list

Add a QAuthZSimple object type that implements the QAuthZ interface. This simple built-in implementation maintains a trivial access control list with a sequence of match rules and a final default policy. This replicates the functionality currently provided by the qemu_acl module. To create an

Re: [Qemu-devel] [PATCH v3] help: Update help to remove misleading display information

Colin Lord writes: > Updates the help messages to remove misleading information about SDL > being the normal display used. > > Signed-off-by: Colin Lord Reviewed-by: Markus Armbruster

[Qemu-devel] [PATCH v10 06/11] qom: support arbitrary non-scalar properties with -object

The current -object command line syntax only allows for creation of objects with scalar properties, or a list with a fixed scalar element type. Objects which have properties that are represented as structs in the QAPI schema cannot be created using -object. This is a design limitation of the way

[Qemu-devel] [PATCH v10 07/11] util: add QAuthZ object as an authorization base class

The current qemu_acl module provides a simple access control list facility inside QEMU, which is used via a set of monitor commands acl_show, acl_policy, acl_add, acl_remove & acl_reset. Note there is no ability to create ACLs - the network services (eg VNC server) were expected to create ACLs

[Qemu-devel] [PATCH v10 05/11] qapi: add a QmpInputVisitor that does string conversion

Currently the QmpInputVisitor assumes that all scalar values are directly represented as their final types. ie it assumes an 'int' is using QInt, and a 'bool' is using QBool. This adds an alternative constructor for QmpInputVisitor that will set it up such that it expects a QString for all scalar

[Qemu-devel] [PATCH v10 03/11] qapi: rename QmpInputVisitor to QObjectInputVisitor

The QmpInputVisitor has no direct dependancy on QMP. It is valid to use it anywhere that one has a QObject. Rename it to better reflect its functionality as a generic QObject to QAPI convertor. Signed-off-by: Daniel P. Berrange --- docs/qapi-code-gen.txt

[Qemu-devel] [PATCH v10 11/11] qmp: add support for mixed typed input visitor

Add a qmp_mixed_input_visitor_new() method which returns a QMP input visitor that accepts either strings or the native data types. Signed-off-by: Daniel P. Berrange --- include/qapi/qobject-input-visitor.h | 22 qapi/qobject-input-visitor.c | 98

Re: [Qemu-devel] [PATCH v7 04/16] qcow2: add qcow2_co_pwritev_compressed

On 08.08.2016 16:44, Kevin Wolf wrote: Am 22.07.2016 um 10:17 hat Denis V. Lunev geschrieben: From: Pavel Butsykin Added implementation of the qcow2_co_pwritev_compressed function that will allow us to safely use compressed writes for the qcow2 from running VMs.

  1   2   3   >