Re: [Qemu-devel] [PATCH v10 29/30] cpu: Convert CpuInfo into flat union

Eric Blake writes: > On 11/09/2015 08:22 AM, Markus Armbruster wrote: >> Eric Blake writes: >> >>> When qapi type CpuInfo was originally created for 0.14, we had >>> no notion of a flat union, and instead just listed a bunch of >>> optional fields with

Re: [Qemu-devel] [PATCH v5 0/8] e1000: Various fixes and registers' implementation

On 11/11/2015 04:06 PM, Leonid Bloch wrote: > On Wed, Nov 11, 2015 at 5:22 AM, Jason Wang wrote: >> > >> > >> > On 11/10/2015 09:19 PM, Leonid Bloch wrote: >>> >> On Tue, Nov 10, 2015 at 3:01 PM, Jason Wang wrote: >>> >>> On 11/10/2015 07:39

Re: [Qemu-devel] [PULL 0/4] ppc-next queue 20151111

-10 17:49:39 +) > > are available in the git repository at: > > git://github.com/dgibson/qemu.git tags/ppc-next-2015 > > for you to fetch changes up to b41d320fef705289d2b73f4949731eb2e189161d: > > spapr: Handle failure of KVM_PPC_ALLOCATE_HTAB ioctl (2015-11-11 13:29:04 >

Re: [Qemu-devel] [PATCH v2 2/5] target-i386/kvm: Hyper-V SynIC MSR's support

On 11/10/2015 04:14 PM, Paolo Bonzini wrote: On 10/11/2015 13:52, Andrey Smetanin wrote: This patch does Hyper-V Synthetic interrupt controller(Hyper-V SynIC) MSR's support and migration. Hyper-V SynIC is enabled by cpu's 'hv-synic' option. This patch does not allow cpu creation if

Re: [Qemu-devel] [PATCH v10 23/30] qapi: Check for qapi collisions of flat union branches

Eric Blake writes: > On 11/09/2015 10:16 PM, Eric Blake wrote: > >>> We have tests covering attempts to do the former >>> (struct-cycle-direct.json, struct-cycle-indirect.json). As far as I can >>> see, we don't have tests covering the latter. Do we catch it? >> >> Yes, at

Re: [Qemu-devel] [PATCH V3 3/6] KVM: add support for any length io eventfd

On 06/11/2015 09:02, Jason Wang wrote: > Signed-off-by: Jason Wang > --- > include/sysemu/kvm.h | 8 > kvm-all.c| 4 > kvm-stub.c | 1 + > 3 files changed, 13 insertions(+) > > diff --git a/include/sysemu/kvm.h b/include/sysemu/kvm.h >

Re: [Qemu-devel] [PATCH 3/4] hw/s390x: Remove superfluous return statements

On Tue, 10 Nov 2015 21:16:10 +0100 Thomas Huth wrote: > The "return;" statements at the end of functions do not make > much sense, so let's remove them. > > Cc: Cornelia Huck > Cc: Christian Borntraeger > Cc: Alexander Graf

Re: [Qemu-devel] [PATCH] include/hw: field 'offset' in struct Property should be ptrdiff_t as int causes overflow

Peter Maydell writes: > On 25 August 2015 at 15:17, Markus Armbruster wrote: >> Stumbled over this while throwing away old mail. Andreas, what do you >> think? > > Seems right to me -- I suspect the original properties code was > written with the

Re: [Qemu-devel] SMM error in 2.4 changelog

On 10/11/2015 21:32, William Dauchy wrote: > On Tue, Nov 3, 2015 at 10:01 AM, Paolo Bonzini wrote: >> Yes, this is correct. Thanks! > > The mistake seems to be still present in changelog. Fixed now, thanks for reminding. Paolo

[Qemu-devel] [PATCH v13 08/13] vfio: add check host bus reset is support or not

From: Chen Fan when init vfio devices done, we should test all the devices supported aer whether conflict with others. For each one, get the hot reset info for the affected device list. For each affected device, all should attach to the VM and on/below the same

[Qemu-devel] [PATCH v13 12/13] vfio-pci: pass the aer error to guest

From: Chen Fan when the vfio device encounters an uncorrectable error in host, the vfio_pci driver will signal the eventfd registered by this vfio device, the results in the qemu eventfd handler getting invoked. this patch is to pass the error to guest and have the

[Qemu-devel] [PATCH v13 03/13] pcie: modify the capability size assert

From: Chen Fan Device's Offset and size can reach PCIE_CONFIG_SPACE_SIZE, fix the corresponding assert. Signed-off-by: Chen Fan Reviewed-by: Marcel Apfelbaum --- hw/pci/pcie.c | 2 +- 1 file changed, 1

[Qemu-devel] [PATCH v13 05/13] vfio: add pcie extanded capability support

From: Chen Fan For vfio pcie device, we could expose the extended capability on PCIE bus. in order to avoid config space broken, we introduce a copy config for parsing extended caps. and rebuild the pcie extended config space. Signed-off-by: Chen Fan

[Qemu-devel] [PATCH v13 04/13] vfio: make the 4 bytes aligned for capability size

From: Chen Fan this function search the capability from the end, the last size should 0x100 - pos, not 0xff - pos. Signed-off-by: Chen Fan --- hw/vfio/pci.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[Qemu-devel] [PATCH v13 06/13] aer: impove pcie_aer_init to support vfio device

From: Chen Fan pcie_aer_init was used to emulate an aer capability for pcie device, but for vfio device, the aer config space size is mutable and is not always equal to PCI_ERR_SIZEOF(0x48). it depends on where the TLP Prefix register required, so here we add a size

Re: [Qemu-devel] [PULL 33/44] block: New option to define the intervals for collecting I/O statistics

On Tue 10 Nov 2015 06:23:36 PM CET, Eric Blake wrote: >> +# @stats-intervals: #optional colon-separated list of intervals for >> +# collecting I/O statistics, in seconds (default: none) >> +# (Since 2.5) > > Eww. Sorry for not noticing this

[Qemu-devel] [PATCH v13 02/13] vfio: squeeze out vfio_pci_do_hot_reset for support bus reset

From: Chen Fan squeeze out vfio_pci_do_hot_reset to do host bus reset when AER recovery. Signed-off-by: Chen Fan --- hw/vfio/pci.c | 75 +++ 1 file changed, 44 insertions(+), 31

[Qemu-devel] [PATCH v13 01/13] vfio: extract vfio_get_hot_reset_info as a single function

From: Chen Fan the function is used to get affected devices by bus reset. so here extract it, and can used for aer soon. Signed-off-by: Chen Fan --- hw/vfio/pci.c | 66 +++ 1

[Qemu-devel] [PATCH v13 00/13] vfio-pci: pass the aer error to guest

From: Chen Fan For now, for vfio pci passthough devices when qemu receives an error from host aer report, currentlly just terminate the guest, but usually user want to know what error occurred but stopping the guest, so this patches add aer capability support for

Re: [Qemu-devel] ARM NEON function call tracing

Peter Maydell writes: > On 11 November 2015 at 07:51, Junaid Shuja > wrote: >> Hi, >> I am working on ARM/NEON instructions. I want to know which neon helper >> function corresponds to the neon instructions. As a test case, I have a >>

Re: [Qemu-devel] [PATCH v3 2/5] target-i386/kvm: Hyper-V SynIC MSR's support

On 11/11/2015 11:18, Andrey Smetanin wrote: > This patch does Hyper-V Synthetic interrupt > controller(Hyper-V SynIC) MSR's support and > migration. Hyper-V SynIC is enabled by cpu's > 'hv-synic' option. > > This patch does not allow cpu creation if > 'hv-synic' option specified but kernel >

Re: [Qemu-devel] [PATCH v2 0/8] Add system_powerdown support on ARM for ACPI and DT

On 11 November 2015 at 01:29, Shannon Zhao wrote: > On 2015/11/11 4:56, Wei Huang wrote: >> I found this was caused by the change of "_HID" name for GPIO device. It >> was changed from "LNRO0009" (v1) to "ARMH0061" (v2), which doesn't match >> with my stock guest kernel

Re: [Qemu-devel] [PATCH v2 2/5] target-i386/kvm: Hyper-V SynIC MSR's support

On 11/11/2015 10:25, Andrey Smetanin wrote: > In this case I'll remove migration of msr_hv_synic_version and make > first time initialization inside kvm_arch_init_vcpu() - inside section > where SynIC availability cpuid bit is set. Thanks! Paolo

Re: [Qemu-devel] ARM NEON function call tracing

On 11 November 2015 at 07:51, Junaid Shuja wrote: > Hi, > I am working on ARM/NEON instructions. I want to know which neon helper > function corresponds to the neon instructions. As a test case, I have a > source file with loads of vadd.i32 instructions. I want to

[Qemu-devel] [PATCH v3 2/5] target-i386/kvm: Hyper-V SynIC MSR's support

This patch does Hyper-V Synthetic interrupt controller(Hyper-V SynIC) MSR's support and migration. Hyper-V SynIC is enabled by cpu's 'hv-synic' option. This patch does not allow cpu creation if 'hv-synic' option specified but kernel doesn't support Hyper-V SynIC. Changes v3: * removed

[Qemu-devel] ARM NEON function call tracing

Hi, I am working on ARM/NEON instructions. I want to know which neon helper function corresponds to the neon instructions. As a test case, I have a source file with loads of vadd.i32 instructions. I want to trace which neon helper functions is called. I used a very crude approach: printf in

Re: [Qemu-devel] [PULL 04/05] seccomp: add setuid, setgid, chroot and setgroups to whitelist

On Mon, Nov 02, 2015 at 08=51=26AM +0100, Paolo Bonzini wrote: > > > On 30/10/2015 14:44, Eduardo Otubo wrote: > > From: Namsun Ch'o > > > > The seccomp sandbox doesn't whitelist setuid, setgid, or setgroups, which > > are > > needed for -runas to work. It also doesn't

Re: [Qemu-devel] [PATCH v2 7/8] hw/arm/virt: Add QEMU powerdown notifier and hook it to GPIO Pin 3

On 11 November 2015 at 06:57, Wei Huang wrote: > > > On 10/29/2015 09:27 AM, Shannon Zhao wrote: >> Currently mach-virt model doesn't support powerdown request. Guest VM >> doesn't react to system_powerdown from monitor console (or QMP) because >> there is no communication

Re: [Qemu-devel] [POC]colo-proxy in qemu

* Jason Wang (jasow...@redhat.com) wrote: > > > On 11/10/2015 05:41 PM, Dr. David Alan Gilbert wrote: > > * Jason Wang (jasow...@redhat.com) wrote: > >> > >> On 11/10/2015 01:26 PM, Tkid wrote: > >>> Hi,all > >>> > >>> We are planning to reimplement colo proxy in userspace (Here is in > >>>

Re: [Qemu-devel] [PATCH v2 0/8] Add system_powerdown support on ARM for ACPI and DT

On 2015/11/11 16:36, Peter Maydell wrote: > On 11 November 2015 at 01:29, Shannon Zhao wrote: >> On 2015/11/11 4:56, Wei Huang wrote: >>> I found this was caused by the change of "_HID" name for GPIO device. It >>> was changed from "LNRO0009" (v1) to "ARMH0061" (v2),

Re: [Qemu-devel] [PULL 0/2] VFIO updates 2015-11-10

On 10 November 2015 at 20:08, Alex Williamson wrote: > The following changes since commit a1a88589dc982f9f8b6c717c2ac98dd71dd4353d: > > Merge remote-tracking branch > 'remotes/pmaydell/tags/pull-target-arm-20151110' into staging (2015-11-10 > 13:55:07 +) > >

Re: [Qemu-devel] [PATCH qemu v4] monitor/target-ppc: Define target_get_monitor_def

On 11/11/2015 03:27, David Gibson wrote: > Meaning one which adds the hook to the monitor, and another which > implements it for ppc? Maybe. > > I'd like to take this, but I'm not sure whether it's reasonable for > the small generic monitor change to go through the ppc tree. Peter, > Paolo,

[Qemu-devel] [PATCH v13 13/13] vfio: add 'aer' property to expose aercap

From: Chen Fan add 'aer' property to let user able to decide whether expose the aer capability. by default we should disable aer feature, because it needs configuration restrictions. Signed-off-by: Chen Fan --- hw/vfio/pci.c | 2 ++

[Qemu-devel] [PATCH v13 10/13] pci: add pci device pre-post reset callbacks for host bus reset

From: Chen Fan Particularly, For vfio devices, Once need to recovery devices by bus reset such as AER, we always need to reset the host bus to recovery the devices under the bus, so we need to add pci device callbacks to specify to do host bus reset. Signed-off-by:

[Qemu-devel] [PATCH v13 11/13] pcie_aer: expose pcie_aer_msg() interface

From: Chen Fan For vfio device, we need to propagate the aer error to Guest OS. we use the pcie_aer_msg() to send aer error to guest. Signed-off-by: Chen Fan --- hw/pci/pcie_aer.c | 2 +- include/hw/pci/pcie_aer.h | 1 + 2

[Qemu-devel] [PATCH v13 07/13] vfio: add aer support for vfio device

From: Chen Fan Calling pcie_aer_init to initilize aer related registers for vfio device, then reload physical related registers to expose device capability. Signed-off-by: Chen Fan --- hw/vfio/pci.c | 82

Re: [Qemu-devel] [PULL v2 00/15] Tracing patches

On 11 November 2015 at 07:34, Stefan Hajnoczi wrote: > v2: > * Fixed missing log.py file when merging "trace: convert stderr backend to > log" [Peter] > > The following changes since commit a77067f6ac9b17beefea506ce5f514072fe3fcf4: > > Merge remote-tracking branch

Re: [Qemu-devel] [PATCH for-2.5 00/15] s390x patches for 2.5

Am 09.11.2015 um 16:56 schrieb Cornelia Huck: > Hopefully last big batch of s390x patches, including: > - bugfixes for LE host and for pci translation > - MAINTAINERS update > - hugetlbfs enablement (kernel patches pending) > - boot from El Torito iso images on virtio-blk > (boot from scsi

[Qemu-devel] [PATCH 1/3] Finish non-postcopiable iterative devices before package

From: "Dr. David Alan Gilbert" Where we have iterable, but non-postcopiable devices (e.g. htab or block migration), complete them before forming the 'package' but with the CPUs stopped. This stops them filling up the package. Signed-off-by: Dr. David Alan Gilbert

[Qemu-devel] [PATCH 3/3] migrate-start-postcopy: Improve text

From: "Dr. David Alan Gilbert" Improve the text in both the qapi-schema and hmp help to point out you need to set the postcopy-ram capability prior to issuing migrate-start-postcopy. Signed-off-by: Dr. David Alan Gilbert --- hmp-commands.hx | 4 +++-

Re: [Qemu-devel] [PATCH v11 18/28] qerror: more error_setg() usage

Eric Blake writes: > A few uses of error_set(ERROR_CLASS_GENERIC_ERROR) have snuck in > since c6bd8c706. Nuke them. Doesn't really belong to this series, but that's okay. > Signed-off-by: Eric Blake > > --- > v11: new patch > --- > block.c

Re: [Qemu-devel] [PATCH v13 10/13] pci: add pci device pre-post reset callbacks for host bus reset

On Wed, Nov 11, 2015 at 06:34:28PM +0800, Cao jin wrote: > From: Chen Fan > > Particularly, For vfio devices, Once need to recovery devices > by bus reset such as AER, we always need to reset the host bus > to recovery the devices under the bus, so we need to add

[Qemu-devel] [PULL for-2.5 01/15] s390x/css: sense data endianness

We keep the device's sense data in a byte array (following the architecture), but the ecws are an array of 32 bit values. If we just blindly copy the values, the sense data will change from de-facto BE data to de-facto cpu-endian data, which means we end up doing an incorrect conversion on LE

[Qemu-devel] [PULL for-2.5 04/15] MAINTAINERS: update virtio-ccw/s390 git tree

Let's reference the git branch I actually use, and add Christian's git tree. Acked-by: Christian Borntraeger Signed-off-by: Cornelia Huck --- MAINTAINERS | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/MAINTAINERS

[Qemu-devel] [PULL for-2.5 06/15] s390x/kvm: don't enable CMMA when hugetlbfs will be used

From: Dominik Dingel On hugetlbfs CMMA will not be useful as every ESSA instruction will trap. So don't offer CMMA to guests with a hugepages backing. Signed-off-by: Dominik Dingel Acked-by: Christian Borntraeger

[Qemu-devel] [PULL for-2.5 05/15] s390x: switch to memory_region_allocate_system_memory

From: Dominik Dingel By replacing memory_region_init_ram with memory_region_allocate_system_memory we gain goodies like mem-path backends. This will allow us to use hugetlbfs once the kernel supports it. Signed-off-by: Dominik Dingel

[Qemu-devel] [PULL for-2.5 15/15] s390: deprecate the non-ccw machine in 2.5

From: Christian Borntraeger The non-ccw machine for s390 (s390-virtio) is not very well maintained and caused several issues in the past: - aliases like virtio-blk did not work for s390 - virtio refactoring failed due to long standing bugs (e.g.see commit cb927b8a

[Qemu-devel] [PULL for-2.5 14/15] s390x/ipl: switch error reporting to error_setg

From: David Hildenbrand Now that we can report errors in the realize function, let's replace the fprintf's and hw_error's with error_setg. Signed-off-by: David Hildenbrand Signed-off-by: Cornelia Huck ---

Re: [Qemu-devel] [PATCH for-2.5] qapi: Document introspection stability considerations

Eric Blake writes: > We are not ready (and might never be ready) to declare > introspection stable between releases. Clients written to > control multiple versions of qemu, and desiring to know > whether a particular member is supported for a given > command, must be prepared

Re: [Qemu-devel] [PATCH v11 19/28] qapi: Change munging of CamelCase enum values

Eric Blake writes: > [hmm, wonder why scripts/get-maintainer.pl didn't loop in Gerd to the > patch itself] > > On 11/11/2015 07:50 AM, Markus Armbruster wrote: >> Eric Blake writes: >> >>> When munging enum values, the fact that we were passing the entire

[Qemu-devel] [PATCH 2/4] spapr: Register and handle HCALL to receive updated RTAS region

Receive updates from SLOF about the updated rtas-base. A separate patch for SLOF [1] adds functionality to invoke a private HCALL whenever OS issues instantiate-rtas with a new rtas-base. This is required as QEMU needs to know the updated rtas-base as it allocates error reporting structure in

[Qemu-devel] [PULL 0/1] error: More error_setg() usage

The following changes since commit 3c07587d49458341510360557c849e93e9afaf59: Merge remote-tracking branch 'remotes/dgibson/tags/ppc-next-2015' into staging (2015-11-11 09:34:18 +) are available in the git repository at: git://repo.or.cz/qemu/armbru.git tags/pull-error-2015-11-11

[Qemu-devel] [PULL 1/1] gluster: allocate GlusterAIOCBs on the stack

From: Paolo Bonzini This is simpler now that the driver has been converted to coroutines. Signed-off-by: Paolo Bonzini Signed-off-by: Jeff Cody Reviewed-by: Kevin Wolf --- block/gluster.c | 86

[Qemu-devel] [PULL v2 0/1] error: More error_setg() usage

v2: Indentation touched up The following changes since commit 3c07587d49458341510360557c849e93e9afaf59: Merge remote-tracking branch 'remotes/dgibson/tags/ppc-next-2015' into staging (2015-11-11 09:34:18 +) are available in the git repository at: git://repo.or.cz/qemu/armbru.git

Re: [Qemu-devel] [PATCH 3/3] migrate-start-postcopy: Improve text

On 11/11/2015 07:02 AM, Dr. David Alan Gilbert (git) wrote: > From: "Dr. David Alan Gilbert" > > Improve the text in both the qapi-schema and hmp help to point out > you need to set the postcopy-ram capability prior to issuing > migrate-start-postcopy. > > Signed-off-by:

Re: [Qemu-devel] [PATCH v13 03/13] pcie: modify the capability size assert

On Wed, Nov 11, 2015 at 06:34:21PM +0800, Cao jin wrote: > From: Chen Fan > > Device's Offset and size can reach PCIE_CONFIG_SPACE_SIZE, > fix the corresponding assert. > > Signed-off-by: Chen Fan > Reviewed-by: Marcel Apfelbaum

Re: [Qemu-devel] [PATCH v10 29/30] cpu: Convert CpuInfo into flat union

Eric Blake writes: > On 11/11/2015 03:19 AM, Markus Armbruster wrote: > Do we need this to make 2.5? >>> >>> It's true that the introspection will change (instead of seeing flat >>> optional members, you now have to chase down variants). But I don't >>> think it is

[Qemu-devel] [PATCH 1/4] spapr: Extend rtas-blob

Extend rtas-blob to accommodate error log. Error log structure is saved in rtas space upon a machine check exception. Signed-off-by: Aravinda Prasad --- hw/ppc/spapr.c |4 1 file changed, 4 insertions(+) diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c index

[Qemu-devel] [PATCH 4/4] target-ppc: Handle NMI guest exit

Memory error such as bit flips that cannot be corrected by hardware are passed on to the kernel for handling. If the memory address in error belongs to guest then guest kernel is responsible for taking suitable action. Patch [1] enhances KVM to exit guest with exit reason set to KVM_EXIT_NMI in

[Qemu-devel] [PATCH 3/4] spapr: Handle "ibm, nmi-register" and "ibm, nmi-interlock" RTAS calls

This patch adds support in QEMU to handle "ibm,nmi-register" and "ibm,nmi-interlock" RTAS calls. The machine check notification address is saved when the OS issues "ibm,nmi-register" RTAS call. This patch also handles the case when multiple processors experience machine check at or about the

Re: [Qemu-devel] CUDA has problems with Mac OS 10.4

On 11/11/15 15:15, Programmingkid wrote: > I built Cormac O'Brien's QEMU repo for Mac OS 9 and tried to boot my Mac OS > 10.4 boot cd. Mac OS 10.4's kernel panics because of a CUDA problem. I did > use the mac99 target. Here is the error message: > > panic(cpu 0 caller 0x16E786CC): CUDA -

[Qemu-devel] [PULL for-2.5 03/15] MAINTAINERS: update s390 file patterns

We were missing some files, and some files should get an additional entry to add the people actually looking after the code. Reported-by: Thomas Huth Acked-by: Christian Borntraeger Signed-off-by: Cornelia Huck ---

[Qemu-devel] [PULL for-2.5 00/15] s390x patches for 2.5

The following changes since commit 3c07587d49458341510360557c849e93e9afaf59: Merge remote-tracking branch 'remotes/dgibson/tags/ppc-next-2015' into staging (2015-11-11 09:34:18 +) are available in the git repository at: git://github.com/cohuck/qemu tags/s390x-2015 for you

[Qemu-devel] [PULL for-2.5 10/15] pc-bios/s390-ccw: El Torito 16-bit boot image size field workaround

From: Maxim Samoylov Because of El Torito spec flaw boot image size needs to be verified. Boot catalog entry size field has 16-bit width, and specifies size in 512-byte units. Thus, boot image size cannot exceed 32M. We actually search for the file to get the file

Re: [Qemu-devel] [PULL v2 00/40] Block layer patches

On 11/11/2015 08:35 AM, Kevin Wolf wrote: >> Also some warnings: >> >> /Users/pm215/src/qemu-for-merges/qemu-io-cmds.c:772:56: warning: >> format specifies type 'size_t' (aka 'unsigned long') but the argument >> has type 'unsigned long lo >> ng' [-Wformat] >> printf("length cannot exceed

Re: [Qemu-devel] [PATCH v11 21/28] qapi: Convert qtype_code into qapi enum type

Eric Blake writes: > What's more meta than using qapi to define qapi? :) > > Convert qtype_code into a full-fledged[*] builtin qapi enum type, > so that a subsequent patch can then use it as the discriminator > type of qapi alternate types. Doing so is easiest when renaming >

Re: [Qemu-devel] [PATCH v11 21/28] qapi: Convert qtype_code into qapi enum type

On 11/11/2015 09:42 AM, Markus Armbruster wrote: > Eric Blake writes: > >> What's more meta than using qapi to define qapi? :) >> >> Convert qtype_code into a full-fledged[*] builtin qapi enum type, >> so that a subsequent patch can then use it as the discriminator >> type of

Re: [Qemu-devel] [PATCH v11 18/28] qerror: more error_setg() usage

Eric Blake writes: > On 11/11/2015 07:21 AM, Markus Armbruster wrote: >> Eric Blake writes: >> >>> A few uses of error_set(ERROR_CLASS_GENERIC_ERROR) have snuck in >>> since c6bd8c706. Nuke them. >> >> Doesn't really belong to this series, but that's

[Qemu-devel] [PULL 1/1] error: More error_setg() usage

From: Eric Blake A few uses of error_set(ERROR_CLASS_GENERIC_ERROR) were missed in c6bd8c706, or have snuck in since. Nuke them. Signed-off-by: Eric Blake Message-Id: <1447224690-9743-19-git-send-email-ebl...@redhat.com> Acked-by: Andreas Färber

Re: [Qemu-devel] [PATCH v11 18/28] qerror: more error_setg() usage

On 11/11/2015 10:31 AM, Markus Armbruster wrote: > Eric Blake writes: > >> On 11/11/2015 07:21 AM, Markus Armbruster wrote: >>> Eric Blake writes: >>> A few uses of error_set(ERROR_CLASS_GENERIC_ERROR) have snuck in since c6bd8c706. Nuke them.

[Qemu-devel] [PATCH for-2.5] qapi: Document introspection stability considerations

We are not ready (and might never be ready) to declare introspection stable between releases. Clients written to control multiple versions of qemu, and desiring to know whether a particular member is supported for a given command, must be prepared to locate that member in spite of qapi changes

[Qemu-devel] [PULL for-2.5 08/15] pc-bios/s390-ccw: ISO-9660 El Torito boot implementation

From: Maxim Samoylov This patch enables boot from media formatted according to ISO-9660 and El Torito bootable CD specification. We try to boot from device as ISO-9660 media when SCSI IPL failed. The first boot catalog entry with bootable flag is used. ISO-9660

[Qemu-devel] [PULL for-2.5 09/15] pc-bios/s390-ccw: El Torito s390x boot entry check

From: Maxim Samoylov Boot entry is considered compatible if boot image is Linux kernel with matching S390 Linux magic string. Empty boot images with sector_count == 0 are considered broken. Signed-off-by: Maxim Samoylov Reviewed-by:

[Qemu-devel] [PULL for-2.5 13/15] s390x/ipl: clean up qom definitions and turn into TYPE_DEVICE

From: David Hildenbrand Let's move the qom definitions of the ipl device into ipl.h, replace "s390-ipl" by a proper type define, turn it into a TYPE_DEVICE and remove the unneeded class definition. Signed-off-by: David Hildenbrand

[Qemu-devel] [PULL v2 1/1] error: More error_setg() usage

From: Eric Blake A few uses of error_set(ERROR_CLASS_GENERIC_ERROR) were missed in c6bd8c706, or have snuck in since. Nuke them. Signed-off-by: Eric Blake Message-Id: <1447224690-9743-19-git-send-email-ebl...@redhat.com> Acked-by: Andreas Färber

[Qemu-devel] [PULL 0/1] Block patches

The following changes since commit 3c07587d49458341510360557c849e93e9afaf59: Merge remote-tracking branch 'remotes/dgibson/tags/ppc-next-2015' into staging (2015-11-11 09:34:18 +) are available in the git repository at: g...@github.com:codyprime/qemu-kvm-jtc.git tags/block-pull

Re: [Qemu-devel] [PULL v3 00/41] Block layer patches

On 11 November 2015 at 16:08, Kevin Wolf <kw...@redhat.com> wrote: > The following changes since commit 3c07587d49458341510360557c849e93e9afaf59: > > Merge remote-tracking branch 'remotes/dgibson/tags/ppc-next-2015' into > staging (2015-11-11 09:34:18 +) > >

Re: [Qemu-devel] [PATCH v13 06/13] aer: impove pcie_aer_init to support vfio device

On Wed, Nov 11, 2015 at 06:34:24PM +0800, Cao jin wrote: > From: Chen Fan > > pcie_aer_init was used to emulate an aer capability for pcie device, > but for vfio device, the aer config space size is mutable and is not > always equal to PCI_ERR_SIZEOF(0x48). it

Re: [Qemu-devel] [PATCH v13 11/13] pcie_aer: expose pcie_aer_msg() interface

On Wed, Nov 11, 2015 at 06:34:29PM +0800, Cao jin wrote: > From: Chen Fan > > For vfio device, we need to propagate the aer error to > Guest OS. we use the pcie_aer_msg() to send aer error > to guest. > > Signed-off-by: Chen Fan

Re: [Qemu-devel] [PATCH v11 13/28] qapi: Hoist tag collision check to Variants.check()

Eric Blake writes: > On 11/11/2015 06:56 AM, Markus Armbruster wrote: >> Eric Blake writes: >> >>> Checking that a given QAPISchemaObjectTypeVariant.name is a >>> member of the corresponding QAPISchemaEnumType of the owning >>>

[Qemu-devel] [PATCH 0/4] target-ppc/spapr: Add FWNMI support in QEMU for PowerKVM guests

This series of patches add support for FWNMI in PowerKVM guests. Memory error such as bit flips that cannot be corrected by hardware is passed on to the kernel for handling by raising machine check exception (an NMI). Upon such machine check exception, if the address in error belongs to guest

[Qemu-devel] [PULL for-2.5 07/15] pc-bios/s390-ccw: Always adjust virtio sector count

From: Maxim Samoylov Let's always adjust the sector number to be read using the current virtio block size value. This prepares for the implementation of IPL from ISO-9660 media. Signed-off-by: Maxim Samoylov Reviewed-by: David

[Qemu-devel] [PULL for-2.5 02/15] s390x/pci : fix up s390 pci iommu translation function

From: Yi Min Zhao On s390x, each pci device has its own iommu, which is only properly setup in qemu once the mpcifc instruction used to register the translation table has been intercepted. Therefore, for a pci device that is not configured or has not been initialized,

[Qemu-devel] [PULL for-2.5 11/15] pc-bios/s390-ccw: rebuild image

Contains: pc-bios/s390-ccw: Always adjust virtio sector count pc-bios/s390-ccw: ISO-9660 El Torito boot implementation pc-bios/s390-ccw: El Torito s390x boot entry check pc-bios/s390-ccw: El Torito 16-bit boot image size field workaround Signed-off-by: Cornelia Huck

[Qemu-devel] [PULL for-2.5 12/15] qdev: provide qdev_reset_all_fn()

From: David Hildenbrand For TYPE_DEVICE, the dc->reset() function is not called on system resets yet. Until that is changed, we have to manually register a reset handler. Let's provide qdev_reset_all_fn(), that can directly be used - just like the reset handler that is

Re: [Qemu-devel] [PATCH v11 19/28] qapi: Change munging of CamelCase enum values

Eric Blake writes: > When munging enum values, the fact that we were passing the entire > prefix + value through camel_to_upper() meant that enum values > spelled with CamelCase could be turned into CAMEL_CASE. However, > this provides a potential collision (both OneTwo and

Re: [Qemu-devel] [PATCH] qga: fix append file open modes for win32

On 11/11/2015 15:02, Michael Roth wrote: >> GENERIC_READ for files >> = FILE_READ_DATA >> + FILE_READ_ATTRIBUTES >> + FILE_READ_EA >> + SYNCHRONIZE >> + STANDARD_RIGHTS_READ (which is READ_CONTROL) >> >> GENERIC_WRITE for files >> =

Re: [Qemu-devel] [PATCH 3/3] migrate-start-postcopy: Improve text

"Dr. David Alan Gilbert (git)" wrote: > From: "Dr. David Alan Gilbert" > > Improve the text in both the qapi-schema and hmp help to point out > you need to set the postcopy-ram capability prior to issuing > migrate-start-postcopy. > > Signed-off-by: Dr.

Re: [Qemu-devel] [PATCH for-2.5] block: make 'stats-intervals' a list of integers

On 11/11/2015 06:17 AM, Alberto Garcia wrote: > This is the natural JSON representation and prevents us from having to > decode the list manually. > > Signed-off-by: Alberto Garcia > --- > blockdev.c | 64 > ++ >

Re: [Qemu-devel] [PULL v3 00/18] Record/replay core for 2.5-rc1

On 11/11/2015 03:53 AM, Markus Armbruster wrote: > > Can we have an entry in MAINTAINERS, please? > A while ago, someone suggested patching checkpatch.pl to flag any new files without a maintainer; I'm not the best perl expert to try and write such a patch, though. -- Eric Blake eblake

[Qemu-devel] [PATCH 12/13] iotests: add default node-name

When testing migration, auto-generated by qemu node-names differs in source and destination qemu and migration fails. After this patch, auto-generated by iotest nodenames will be the same. Signed-off-by: Vladimir Sementsov-Ogievskiy --- tests/qemu-iotests/iotests.py |

[Qemu-devel] [PATCH 03/13] block: tiny refactoring: minimize hbitmap_(set/reset) usage

Reviewed-by: John Snow Signed-off-by: Vladimir Sementsov-Ogievskiy --- block.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/block.c b/block.c index 70106b8..1171dbb 100644 --- a/block.c +++ b/block.c @@ -3449,7 +3449,7 @@ void

[Qemu-devel] [PATCH 10/13] iotests: add add_incoming_migration to VM class

Reviewed-by: John Snow Signed-off-by: Vladimir Sementsov-Ogievskiy --- tests/qemu-iotests/iotests.py | 6 ++ 1 file changed, 6 insertions(+) diff --git a/tests/qemu-iotests/iotests.py b/tests/qemu-iotests/iotests.py index 92b6d5e..aac698a 100644

[Qemu-devel] [PATCH 08/13] migration: add migration/block-dirty-bitmap.c

Live migration of dirty bitmaps. Only named dirty bitmaps, associated with root nodes and non-root named nodes are migrated. If destination qemu is already containing a dirty bitmap with the same name as a migrated bitmap (for the same node), than, if their granularities are the same the

[Qemu-devel] [PATCH 01/13] hbitmap: serialization

Functions to serialize / deserialize(restore) HBitmap. HBitmap should be saved to linear sequence of bits independently of endianness and bitmap array element (unsigned long) size. Therefore Little Endian is chosen. These functions are appropriate for dirty bitmap migration, restoring the bitmap

[Qemu-devel] [PULL v3 14/41] blockdev: read-only-mode for blockdev-change-medium

From: Max Reitz Add an option to qmp_blockdev_change_medium() which allows changing the read-only status of the block device whose medium is changed. Some drives do not have a inherently fixed read-only status; for instance, floppy disks can be set read-only or writable

[Qemu-devel] [PULL v3 41/41] iotests: Check for quorum support in test 139

From: Alberto Garcia The quorum driver is always built in, but it is disabled during run-time if there's no SHA256 support available (see commit e94867e). This patch skips the quorum test in iotest 139 in that case. Signed-off-by: Alberto Garcia Message-id:

Re: [Qemu-devel] [PATCH v11 13/28] qapi: Hoist tag collision check to Variants.check()

On 11/11/2015 06:56 AM, Markus Armbruster wrote: > Eric Blake writes: > >> Checking that a given QAPISchemaObjectTypeVariant.name is a >> member of the corresponding QAPISchemaEnumType of the owning >> QAPISchemaObjectTypeVariants.tag_member ensures that there are >> no

Re: [Qemu-devel] [PATCH v11 18/28] qerror: more error_setg() usage

On 11/11/2015 07:21 AM, Markus Armbruster wrote: > Eric Blake writes: > >> A few uses of error_set(ERROR_CLASS_GENERIC_ERROR) have snuck in >> since c6bd8c706. Nuke them. > > Doesn't really belong to this series, but that's okay. If you're going to modify this for 2.5

[Qemu-devel] CUDA has problems with Mac OS 10.4

I built Cormac O'Brien's QEMU repo for Mac OS 9 and tried to boot my Mac OS 10.4 boot cd. Mac OS 10.4's kernel panics because of a CUDA problem. I did use the mac99 target. Here is the error message: panic(cpu 0 caller 0x16E786CC): CUDA - TODO CHECK FOR TRANSACTION TYPE AND ERROR This is the

  1   2   3   >