[Qemu-devel] VFIO NATIVE_ENDIAN regions question

At the moment VFIO's BARs are NATIVE_ENDIAN. The idea is that since it does not parse BARs content and just provides transport, it should not do byte swaps, the guest does it anyway. That worked fine while the host was big-endian and it does not work when the host is little-endian. This happens bec

Re: [Qemu-devel] [PATCH v3] target-arm: Fix resetting issues on ARMv7-M CPUs

CC Alistair who is into ARMv7M On Sat, Sep 6, 2014 at 4:39 AM, Martin Galvan wrote: > When calling qemu_system_reset after startup on a Cortex-M > CPU, the initial values of PC, MSP and the Thumb bit weren't being set > correctly if the vector table was in ROM. In particular, since Thumb was 0, a

Re: [Qemu-devel] Supporting multiple CPU AddressSpaces and memory transaction attributes

On Fri, Sep 5, 2014 at 3:47 AM, Peter Maydell wrote: > One of the parts of the ARM TrustZone/Security Extensions > which the patchsets we've seen so far haven't attempted to > tackle is the problem of Secure vs NonSecure memory accesses. > Architecturally, every memory transaction should have > an

Re: [Qemu-devel] [PATCH 0/7] s390-ccw.img: block size and DASD format support

On 29.08.14 12:10, Christian Borntraeger wrote: > On 29/08/14 11:01, Jens Freimann wrote: >> Patches 1-5 contain changes improving support of more disk formats >> and block sizes. >> >> Patch 6 makes sure we print a newline to leave a clean slate before >> continuing with IPL. >> >> Patch 7 upda

Re: [Qemu-devel] [RFC][patch 0/6] pci pass-through support for qemu/KVM on s390

On 05.09.14 13:39, Frank Blaschka wrote: > On Fri, Sep 05, 2014 at 10:21:27AM +0200, Alexander Graf wrote: >> >> >> On 04.09.14 12:52, frank.blasc...@de.ibm.com wrote: >>> This set of patches implements pci pass-through support for qemu/KVM on >>> s390. >>> PCI support on s390 is very different

Re: [Qemu-devel] [patch 0/3] kvmclock: Ensure time in migration never goes backward (v3)

On Sat, Sep 6, 2014 at 2:14 AM, Paolo Bonzini wrote: > Il 05/09/2014 21:35, Andrey Korolyov ha scritto: >> - boot up a VM, make sure to feed it heavy long task, for example >> kernel compilation, >> - neither migrate once in the middle of process (with fallback to >> non-live migration which is av

Re: [Qemu-devel] [RFC][patch 0/6] pci pass-through support for qemu/KVM on s390

On 05.09.14 13:55, Frank Blaschka wrote: > On Fri, Sep 05, 2014 at 10:35:59AM +0200, Alexander Graf wrote: >> >> >> On 05.09.14 09:46, Frank Blaschka wrote: >>> On Thu, Sep 04, 2014 at 07:16:24AM -0600, Alex Williamson wrote: On Thu, 2014-09-04 at 12:52 +0200, frank.blasc...@de.ibm.com wrote

Re: [Qemu-devel] [PATCH 1/2] util: introduce bitmap_try_new

On 09/05/2014 02:00 PM, Peter Lieven wrote: >>> + >> What you have works, but I personally would have reimplemented >> bitmap_new as the first caller of bitmap_try_new in this patch, where >> bitmap_new handles a NULL bitmap_try_new return by abort()ing, so that >> it has the same behavior. By ro

Re: [Qemu-devel] [patch 0/3] kvmclock: Ensure time in migration never goes backward (v3)

Il 05/09/2014 21:35, Andrey Korolyov ha scritto: > - boot up a VM, make sure to feed it heavy long task, for example > kernel compilation, > - neither migrate once in the middle of process (with fallback to > non-live migration which is available in libvirt, else it may take > forever) or just wait

Re: [Qemu-devel] [PATCH 01/12] spapr: populate DRC entries for root dt node

On 08/18/2014 05:21 PM, Michael Roth wrote: > From: Nathan Fontenot > > This add entries to the root OF node to advertise our PHBs as being > DR-capable in according with PAPR specification. > > Each PHB is given a name of PHB, advertised as a PHB type, > and associated with a power domain of -1

Re: [Qemu-devel] [Xen-devel] [RFC Patch v3 23/22] Introduce "xen-load-devices-state"

On Fri, 5 Sep 2014, Wen Congyang wrote: > introduce a "xen-load-devices-state" QAPI command that can be used to load > the state of all devices, but not the RAM or the block devices of the > VM. Hello Wen, please CC qemu-devel too for QEMU patches. Could you please explain why do you need this co

Re: [Qemu-devel] [RFC PATCH v0 14/15] ppc: Add CPU hotplug support for sPAPR guests

On 09/03/2014 11:06 PM, Bharata B Rao wrote: > Add support for cpu-add monitor command. Use the exising EPOW event > infrastructure to send CPU hotplug notification to the guest. > > Signed-off-by: Bharata B Rao > --- > hw/ppc/spapr.c | 240 >

[Qemu-devel] [PATCH 1/1] Add support for DRM IOCTLs to QEMU user mode virtualization.

This patch modifies the syscall virtualization table with DRM IOCTLs used by user mode libraries like libdrm, xorg-video-driver and mesa to talk to the host kernel and the Intel i915/i965+ DRM driver. This patch doesn't include radeon, nouveau, vmwgfx, etc. IOCTLs. In practice it should be roughly

[Qemu-devel] [PATCH 0/1] Add support for DRM IOCTLs to QEMU user mode virtualization.

This patch adds initial user-virtualization support for the DRM (type 'd') IOCTLs in linux. With it and a corresponding architecture chroot (say aarch64), I am able to successfully run a few 2D and 3D applications with native graphics acceleration. Some notes/caveats are: 1. It will only work with

Re: [Qemu-devel] [PATCH] vnc: add additional key up event before repeated key down

On Fri, 5 Sep 2014, Chunyan Liu wrote: > Using xen tools 'xl vncviewer' with tigervnc (default on SLE-12), > found that: the display of the guest is unexpected while keep > pressing a key. We expect the same character multiple times, but > it prints only one time. This happens on a PV guest in text

Re: [Qemu-devel] [PATCH 0/4] introduce max_transfer_length

Feel free to add a Reviewed-by: Ronnie Sahlberg to the patches. On Fri, Sep 5, 2014 at 12:52 PM, Peter Lieven wrote: > Am 05.09.2014 um 19:05 schrieb ronnie sahlberg: >> Looks good to me. >> >> (minor question is just why not let default max be 0x for both 10 >> and 16 CDBs ?) > > You are

Re: [Qemu-devel] [Bug 1358722] Re: latest acpi commits causes memory allocation fault in macosx

On 09/04/2014 10:21 AM, Marco Minetti wrote: On Thu, 2014-09-04 at 09:10 -0400, Gabriel L. Somlo wrote: On Thu, 04 Sep 2014 08:43:12, Marco Minetti wrote: The experiments for running MacOSXon KVM/QEMU I followed are here: http://www.contrib.andrew.cmu.edu/~somlo/OSXKVM/ [...] Bug descript

[Qemu-devel] [PATCHv2] ui/vnc: set TCP_NODELAY

we currently have the Nagle algorithm enabled for all outgoing VNC updates. This may delay sensitive updates as mouse movements or typing in the console. As we currently prepare all data in a buffer and then send as much as we can disabling the Nagle algorithm should not cause big trouble. Well est

Re: [Qemu-devel] [PATCH 1/2] util: introduce bitmap_try_new

Am 25.08.2014 um 17:09 schrieb Eric Blake: > On 08/22/2014 03:26 AM, Peter Lieven wrote: >> regular bitmap_new simply aborts if the memory allocation fails. >> bitmap_try_new returns NULL on failure and allows for proper >> error handling. >> >> Signed-off-by: Peter Lieven >> --- >> include/qemu/

Re: [Qemu-devel] [PATCH 0/4] introduce max_transfer_length

Am 05.09.2014 um 19:05 schrieb ronnie sahlberg: > Looks good to me. > > (minor question is just why not let default max be 0x for both 10 > and 16 CDBs ?) You are right. I was looking at the technical limit, but in fact it doesn't make sense to have different limits. Its ridiculous to say, you

Re: [Qemu-devel] [patch 0/3] kvmclock: Ensure time in migration never goes backward (v3)

On Fri, Sep 5, 2014 at 10:35 PM, Andrey Korolyov wrote: > On Fri, Sep 5, 2014 at 10:26 PM, Marcelo Tosatti wrote: >> On Fri, Sep 05, 2014 at 10:16:17PM +0400, Andrey Korolyov wrote: >>> On Fri, Sep 5, 2014 at 5:52 PM, Marcelo Tosatti wrote: >>> > Regression fix tested with fio and ping-pong migr

Re: [Qemu-devel] [question] PIC and APIC

On 2014-09-05, 13:03, "Paolo Bonzini" wrote: >Il 05/09/2014 17:51, Richard Bilson ha scritto: >> Greetings folks, >> >> I've been tracking down certain obscure failures that we see running our >> kernel on qemu x86 smp. Based on a few days diving into qemu internals >>it >> seems that the problem

[Qemu-devel] [RFC PATCH v2] Support vhd type VHD_DIFFERENCING

Now qemu only supports vhd type VHD_FIXED and VHD_DYNAMIC, so qemu can't read snapshot volume of vhd, and can't support other storage features of vhd file. This patch add read parent information in function "vpc_open", read bitmap in "vpc_read", and change bitmap in "vpc_write". Signed-off-by: Xi

[Qemu-devel] [PATCH] Fix improper usage of cpu_to_be32 in vpc

cpu_to_be32() is wrong since vhd_type is an enum constant (just a regular CPU-endian integer). Signed-off-by: Xiaodong Gong --- block/vpc.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/block/vpc.c b/block/vpc.c index 055efc4..c024b4c 100644 --- a/block/vpc.c +++ b/

[Qemu-devel] [PATCH v3] target-arm: Fix resetting issues on ARMv7-M CPUs

When calling qemu_system_reset after startup on a Cortex-M CPU, the initial values of PC, MSP and the Thumb bit weren't being set correctly if the vector table was in ROM. In particular, since Thumb was 0, a Usage Fault would arise immediately after trying to execute any instruction on a Cortex-M.

Re: [Qemu-devel] [PATCH v7 24/28] ide: add bootindex to qom property

On Fri, Sep 05, 2014 at 04:37:32PM +0800, arei.gong...@huawei.com wrote: > From: Gonglei > > Add a qom property with the same name 'bootindex', > when we remove it form qdev property, things will > continue to work just fine, and we can use qom features > which are not supported by qdev property.

Re: [Qemu-devel] [patch 0/3] kvmclock: Ensure time in migration never goes backward (v3)

On Fri, Sep 5, 2014 at 10:26 PM, Marcelo Tosatti wrote: > On Fri, Sep 05, 2014 at 10:16:17PM +0400, Andrey Korolyov wrote: >> On Fri, Sep 5, 2014 at 5:52 PM, Marcelo Tosatti wrote: >> > Regression fix tested with fio and ping-pong migration. >> > >> > >> >> Thanks, actually this series also intro

Re: [Qemu-devel] [patch 0/3] kvmclock: Ensure time in migration never goes backward (v3)

Il 05/09/2014 20:26, Marcelo Tosatti ha scritto: >> > Thanks, actually this series also introduces regression with average >> > live migration time - 42s avg vs 7s avg for the reference VM on >> > ping-pong test. Can you please confirm this? > Can't confirm - migration time is similar for me. It's

Re: [Qemu-devel] [PATCH v7 08/28] virtio-net: add bootindex to qom property

On Fri, Sep 05, 2014 at 04:37:16PM +0800, arei.gong...@huawei.com wrote: > From: Gonglei > > Add a qom property with the same name 'bootindex', > when we remove it form qdev property, things will > continue to work just fine, and we can use qom features > which are not supported by qdev property.

Re: [Qemu-devel] [patch 0/3] kvmclock: Ensure time in migration never goes backward (v3)

On Fri, Sep 05, 2014 at 10:16:17PM +0400, Andrey Korolyov wrote: > On Fri, Sep 5, 2014 at 5:52 PM, Marcelo Tosatti wrote: > > Regression fix tested with fio and ping-pong migration. > > > > > > Thanks, actually this series also introduces regression with average > live migration time - 42s avg vs

Re: [Qemu-devel] HelloWord kernel for qemu-system-aarch64

On 09/05/2014 01:52 PM, Semion Prihodko wrote: > This is tricky to deepen in this large code base. It looks strange that > there's no simple concrete tutorial like we have for all other CPU > architectures (e.g. in osdev.org ). AArch64 hasn't really changed the PL011 UART (nor GI

Re: [Qemu-devel] [patch 0/3] kvmclock: Ensure time in migration never goes backward (v3)

On Fri, Sep 5, 2014 at 5:52 PM, Marcelo Tosatti wrote: > Regression fix tested with fio and ping-pong migration. > > Thanks, actually this series also introduces regression with average live migration time - 42s avg vs 7s avg for the reference VM on ping-pong test. Can you please confirm this?

Re: [Qemu-devel] [PATCH v7 05/28] bootindex: rework add_boot_device_path function

On Fri, Sep 05, 2014 at 04:37:13PM +0800, arei.gong...@huawei.com wrote: [...] > +static void del_original_boot_device(DeviceState *dev, const char *suffix) > +{ > +FWBootEntry *i; > + > +if (dev == NULL) { > +return; > +} > + > +QTAILQ_FOREACH(i, &fw_boot_order, link) { > +

Re: [Qemu-devel] [PATCH v4 00/33] target-arm: add Security Extensions for CPUs

On 1 July 2014 00:09, wrote: > From: Greg Bellows > > Updated Fabian's v3 patchset for review comments. This patchset includes > changes in support of the security extension on v7 aarch32 with hooks for > later > enabling v8 aarch64. > > The patches are built upon and therefore dependent on v3

Re: [Qemu-devel] HelloWord kernel for qemu-system-aarch64

This is tricky to deepen in this large code base. It looks strange that there's no simple concrete tutorial like we have for all other CPU architectures (e.g. in osdev.org). 05 Сен 2014 г. 19:57 пользователь "Claudio Fontana" < claudio.font...@huawei.com> написал: > On 05.09.2014 16:50, Semion Pri

Re: [Qemu-devel] [PATCH v2] target-arm: Fix resetting issues on ARMv7-M CPUs

Once again, you're right. I'll fix that right away and send v3. On Fri, Sep 5, 2014 at 2:43 PM, Peter Maydell wrote: > On 4 September 2014 19:12, Martin Galvan > wrote: > > Thanks for this patch. I think it's generally right > but could use a little tweaking for style issues. > >> When calling q

Re: [Qemu-devel] Serial: possible hang during intensive interaction over the console

On Thu, Sep 4, 2014 at 8:03 PM, Andrey Korolyov wrote: > On Thu, Sep 4, 2014 at 5:33 PM, Kirill Batuzov wrote: >> On Thu, 4 Sep 2014, Andrey Korolyov wrote: >>> >>> Thanks, the launch string can be borrowed from attach here: >>> http://lists.nongnu.org/archive/html/qemu-devel/2014-09/msg00482.htm

Re: [Qemu-devel] [PATCH v2] target-arm: Fix resetting issues on ARMv7-M CPUs

On 4 September 2014 19:12, Martin Galvan wrote: Thanks for this patch. I think it's generally right but could use a little tweaking for style issues. > When calling qemu_system_reset after startup on a Cortex-M CPU, the > initial values of PC, MSP and the Thumb bit weren't set correctly Add "if

Re: [Qemu-devel] qcow2, lazy_refcounts and killing qemu

On Fri, Sep 05, 2014 at 04:39:51PM +0100, Stefan Hajnoczi wrote: > Did you try older QEMU versions? I'm curious if this is something that > crept in later or is fundamentally broken in lazy_refcounts=on. At your prompting, I've done a bit more investigation. I was basing my observations on qemu

Re: [Qemu-devel] [Bug 1362755] [NEW] QEmu +2 does not route VLAN tagged packets, that are originated within the Hypervisor itself.

Does this also fail with a build of git://git.qemu.org/qemu.git? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1362755 Title: QEmu +2 does not route VLAN tagged packets, that are originated within

Re: [Qemu-devel] [Qemu-ppc] [PATCH 2/2] PPC: openpic_kvm: Filter region callbacks based on memory region offset

On Wed, 2014-09-03 at 14:36 -0400, Bogdan Purcareata wrote: > This is done due to the fact that the kvm-openpic region_{add,del} callbacks > can be invoked for sections generated from other memory regions as well. These > callbacks should handle only requests for the kvm-openpic memory region. > >

Re: [Qemu-devel] [Qemu-ppc] [PATCH 09/12] spapr_pci: enable basic hotplug operations

On 09/04/2014 08:10 PM, Nathan Fontenot wrote: > On 09/04/2014 11:34 AM, Michael Roth wrote: >> Quoting Michael Roth (2014-09-04 11:12:15) >>> Quoting Bharata B Rao (2014-09-04 10:08:20) On Thu, Sep 4, 2014 at 4:33 AM, Michael Roth wrote: >>> +static int spapr_device_hotplug_add(Dev

Re: [Qemu-devel] [Qemu-ppc] [PATCH 1/2] memory: Add MemoryRegion get address space offset helper function

On Wed, 2014-09-03 at 14:36 -0400, Bogdan Purcareata wrote: > Adding this function would allow a MemoryRegion to compute its start address > within the AddressSpace. This is done recursively based on mr->container. > > Signed-off-by: Bogdan Purcareata > --- > include/exec/memory.h |8 +++

Re: [Qemu-devel] [PATCH 0/4] introduce max_transfer_length

Looks good to me. (minor question is just why not let default max be 0x for both 10 and 16 CDBs ?) On Fri, Sep 5, 2014 at 9:51 AM, Peter Lieven wrote: > This series adds the basics for introducing a maximum transfer length > to the block layer. Its main purpose is currently avoiding that > a

Re: [Qemu-devel] [question] PIC and APIC

Il 05/09/2014 17:51, Richard Bilson ha scritto: > Greetings folks, > > I've been tracking down certain obscure failures that we see running our > kernel on qemu x86 smp. Based on a few days diving into qemu internals it > seems that the problems relate to mixing PIC and APIC-generated > interrupts

Re: [Qemu-devel] HelloWord kernel for qemu-system-aarch64

On 05.09.2014 16:50, Semion Prihodko wrote: > Let's discard semihosting. I have aarch64-linux-gnu-* toolchain and > qemu-system-aarch64 emulator. How can I build a minimal kernel which > outputs Hello World! via serial port and run it on the emulator? > If you run qemu with the "virt" platform, y

[Qemu-devel] [PATCH 0/4] introduce max_transfer_length

This series adds the basics for introducing a maximum transfer length to the block layer. Its main purpose is currently avoiding that a multiwrite_merge exceeds the max_xfer_len of an attached iSCSI LUN. This is a required bug fix. Discussed reporting of this maximum in the SCSI Disk Inquiry Emula

[Qemu-devel] [PATCH 2/4] block: immediately cancel oversized read/write requests

Signed-off-by: Peter Lieven --- block.c | 14 ++ 1 file changed, 14 insertions(+) diff --git a/block.c b/block.c index 2c4a5de..fa4c34b 100644 --- a/block.c +++ b/block.c @@ -3215,6 +3215,13 @@ static int coroutine_fn bdrv_co_do_readv(BlockDriverState *bs, return -EINVAL;

[Qemu-devel] [PATCH 3/4] block/iscsi: set max_transfer_length

the limit of 0xff for 16 byte CDBs is intentional to avoid overflows on 32-bit architectures. Signed-off-by: Peter Lieven --- block/iscsi.c | 12 ++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/block/iscsi.c b/block/iscsi.c index 3e19202..a4b625c 100644 --- a/bl

[Qemu-devel] [PATCH 4/4] block: avoid creating oversized writes in multiwrite_merge

Signed-off-by: Peter Lieven --- block.c |5 + 1 file changed, 5 insertions(+) diff --git a/block.c b/block.c index fa4c34b..db3f842 100644 --- a/block.c +++ b/block.c @@ -4554,6 +4554,11 @@ static int multiwrite_merge(BlockDriverState *bs, BlockRequest *reqs, merge = 0;

[Qemu-devel] [PATCH 1/4] BlockLimits: introduce max_transfer_length

Signed-off-by: Peter Lieven --- block.c |4 include/block/block_int.h |3 +++ 2 files changed, 7 insertions(+) diff --git a/block.c b/block.c index cb670fd..2c4a5de 100644 --- a/block.c +++ b/block.c @@ -529,6 +529,7 @@ void bdrv_refresh_limits(BlockDriverState *bs

Re: [Qemu-devel] I/O parallelism on QCOW2

On Fri, Sep 5, 2014 at 6:02 AM, Stefan Hajnoczi wrote: > On Thu, Sep 04, 2014 at 12:32:12PM -0400, Xingbo Wu wrote: > > After running a 16-thread sync-random-write test against qcow2, It is > > observed that QCOW2 seems to be serializing all its metadata-related > writes. > > If qcow2 is desig

Re: [Qemu-devel] [PATCH] pl061: implement input interrupt logic

On 30 August 2014 23:27, Colin Leitner wrote: > This patch adds the missing input interrupt logic to the pl061 GPIO device. To > keep the floating output pins to stay high, the old state variable had to be > split into two separate ones for input and output - which brings the vmstate > version to

Re: [Qemu-devel] [PATCH 6/6] hw/arm/boot: enable DTB support when booting ELF images

> On 5 sep. 2014, at 17:15, Ard Biesheuvel wrote: > > Add support for loading DTB images when booting ELF images via -kernel. > The DTB image is located at the next 4 KB boundary above the highest address > covered by the loaded ELF image. > Apologies, this commit message is out of date: the

[Qemu-devel] [PATCH] target-ppc: Implement IVOR[59] By Default for Book E

Adjust the IVOR mask for generic Book E implementation to support bit 59. This is consistent with the Power ISA. Signed-off-by: Tom Musta Reported-by: Pierre Mallard --- target-ppc/translate_init.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/target-ppc/translate_in

Re: [Qemu-devel] [PULL 00/26] Block patches

On 5 September 2014 17:13, Stefan Hajnoczi wrote: > The following changes since commit 30eaca3acdf17d7bcbd1213eb149c02037edfb0b: > > Merge remote-tracking branch 'remotes/spice/tags/pull-spice-20140902-1' > into staging (2014-09-02 10:26:10 +0100) > > are available in the git repository at: > >

[Qemu-devel] [PULL 26/26] ide: Add resize callback to ide/core

From: John Snow Currently, if the block device backing the IDE drive is resized, the information about the device as cached inside of the IDEState structure is not updated, thus when a guest OS re-queries the drive, it is unable to see the expanded size. This patch adds a resize callback that up

[Qemu-devel] [PATCH] seccomp: whitelist syscalls fallocate(), fadvise64(), inotify_init1() and inotify_add_watch()

fallocate() is needed for snapshotting. If it isn’t whitelisted $ qemu-img create -f qcow2 x.qcow 1G Formatting 'x.qcow', fmt=qcow2 size=1073741824 encryption=off cluster_size=65536 lazy_refcounts=off $ qemu-kvm -display none -monitor stdio -sandbox on x.qcow QEMU 2.1.50 monitor -

[Qemu-devel] [PULL 25/26] IDE: Fill the IDENTIFY request consistently

From: John Snow IDE-HD, IDE-ATAPI and IDE-CFATA all fill the identify buffer in slightly different ways, this is a relatively minor patch to make them uniform, to emphasize that: (1) We build the s->identify_data cache first, then (2) We copy it to s->io_buffer to fulfill the request. Signed-of

[Qemu-devel] [PULL 21/26] qtest/ide: Uninitialize PC allocator

From: John Snow Use the new call to pc_alloc_uninit as a test for the new pathways. The leak checking / assert pathways are not enabled in this patch, leaving this as an option to future test writers. Signed-off-by: John Snow Signed-off-by: Stefan Hajnoczi --- tests/ide-test.c | 2 ++ 1 file

[Qemu-devel] [PULL 22/26] ide: Add wwn support to IDE-ATAPI drive

From: John Snow Although it is possible to specify the wwn property for cdrom devices on the command line, the underlying driver fails to relay this information to the guest operating system via IDENTIFY. This is a simple patch to correct that. See ATA8-ACS, Table 22 parts 5, 6, and 9. Signed-

Re: [Qemu-devel] [PATCH] virtio-pci: fix virtio-net child refcount in transports

On Fri, Sep 05, 2014 at 11:46:32PM +0800, Gonglei wrote: > Hi, > > > Subject: Re: [Qemu-devel] [PATCH] virtio-pci: fix virtio-net child refcount > > in > > transports > > > > On Thu, Sep 04, 2014 at 07:41:32PM +0800, arei.gong...@huawei.com wrote: > > > From: Gonglei > > > > > > object_initiali

[Qemu-devel] [PULL 20/26] libqos: add a simple first-fit memory allocator

From: John Snow Implement a simple first-fit memory allocator that attempts to keep track of leased blocks of memory in order to be able to re-use blocks. Additionally, allow the user to specify when initializing the device that upon cleanup, we would like to assert that there are no blocks in u

[Qemu-devel] [PULL 18/26] qemu-nbd: fix indentation and coding style

From: Peter Lieven Signed-off-by: Peter Lieven Reviewed-by: Eric Blake Reviewed-by: Benoit Canet Signed-off-by: Stefan Hajnoczi --- qemu-nbd.c | 75 -- 1 file changed, 39 insertions(+), 36 deletions(-) diff --git a/qemu-nbd.c b/qem

[Qemu-devel] [PULL 19/26] MAINTAINERS: update sheepdog maintainer

From: MORITA Kazutaka Hitoshi takes over sheepdog maintenance from me. Signed-off-by: MORITA Kazutaka Signed-off-by: Stefan Hajnoczi --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 142f68a..42a668b 100644 --- a/MAINTAINERS ++

[Qemu-devel] [PULL 14/26] qemu-img: fix rebase src_cache option documentation

The src_cache option (-T) specifies the cache mode for backing files. It applies both the image's old backing file as well as the new backing file: ret = bdrv_open(&bs_old_backing, backing_name, NULL, NULL, src_flags, old_backing_drv, &local_err); if (ret) { ... } i

[Qemu-devel] [PULL 13/26] qemu-img: clarify src_cache option documentation

The source cache option takes the same values as the cache option. The documentation reads a little strange because it starts with "In contrast the src_cache option ...". The fact that this is comparing with the previous documented option (the 'cache' option) is implicit. Readers may be confused

[Qemu-devel] [PULL 12/26] libqos: Added EVENT_IDX support

From: Marc Marí Added avail_event and NO_NOTIFY check before notifying. Added used_event setting. Signed-off-by: Marc Marí Signed-off-by: Stefan Hajnoczi --- tests/libqos/virtio-pci.c | 1 + tests/libqos/virtio.c | 27 +- tests/libqos/virtio.h | 5 ++ tests/virtio-blk-tes

[Qemu-devel] [PULL 24/26] vmdk: fix buf leak in vmdk_parse_extents()

vmdk_open_sparse() does not take ownership of buf so the caller always needs to free it. Signed-off-by: Stefan Hajnoczi Reviewed-by: Max Reitz Reviewed-by: Fam Zheng --- block/vmdk.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/block/vmdk.c b/block/vmdk.c index 9bf28f3..

[Qemu-devel] [PULL 17/26] qemu-nbd: add option to set detect-zeroes mode

From: Peter Lieven Signed-off-by: Peter Lieven Reviewed-by: Eric Blake Reviewed-by: Benoit Canet Signed-off-by: Stefan Hajnoczi --- qemu-nbd.c | 25 + 1 file changed, 25 insertions(+) diff --git a/qemu-nbd.c b/qemu-nbd.c index 626e584..6ef8b10 100644 --- a/qemu-nbd.c

[Qemu-devel] [PULL 10/26] libqos: Added test case for configuration changes in virtio-blk test

From: Marc Marí Reviewed-by: Stefan Hajnoczi Signed-off-by: Marc Marí Signed-off-by: Stefan Hajnoczi --- tests/virtio-blk-test.c | 34 ++ 1 file changed, 34 insertions(+) diff --git a/tests/virtio-blk-test.c b/tests/virtio-blk-test.c index 2f9cc2b..672580b 100

[Qemu-devel] [PULL 09/26] libqos: Added indirect descriptor support to virtio implementation

From: Marc Marí Add functions necessary for working with indirect descriptors. Add test using new functions. Reviewed-by: Stefan Hajnoczi Signed-off-by: Marc Marí Signed-off-by: Stefan Hajnoczi --- tests/libqos/virtio-pci.c | 10 + tests/libqos/virtio.c | 64 +++

[Qemu-devel] [PULL 16/26] rename parse_enum_option to qapi_enum_parse and make it public

From: Peter Lieven relaxing the license to LGPLv2+ is intentional. Suggested-by: Markus Armbruster Signed-off-by: Hu Tao Signed-off-by: Peter Lieven Reviewed-by: Eric Blake Reviewed-by: Benoit Canet Signed-off-by: Stefan Hajnoczi --- blockdev.c | 30 ++

[Qemu-devel] [PULL 07/26] tests: Add virtio device initialization

From: Marc Marí Add functions to read and write virtio header fields. Add status bit setting in virtio-blk-device. Signed-off-by: Marc Marí Signed-off-by: Stefan Hajnoczi --- tests/Makefile| 2 +- tests/libqos/virtio-pci.c | 71 +++ tes

[Qemu-devel] [PULL 08/26] libqos: Added basic virtqueue support to virtio implementation

From: Marc Marí Add status changing and feature negotiation. Add basic virtqueue support for adding and sending virtqueue requests. Add ISR checking. [Squashed request endianness fix by Greg Kurz --Stefan] Reviewed-by: Stefan Hajnoczi Signed-off-by: Marc Marí Signed-off-by: Stefan Hajnoczi

[Qemu-devel] [PULL 06/26] tests: Functions bus_foreach and device_find from libqos virtio API

From: Marc Marí Virtio header has been changed to compile and work with a real device. Functions bus_foreach and device_find have been implemented for PCI. Virtio-blk test case now opens a fake device. Reviewed-by: Stefan Hajnoczi Signed-off-by: Marc Marí Signed-off-by: Stefan Hajnoczi --- t

[Qemu-devel] [PULL 11/26] libqos: Added MSI-X support

From: Marc Marí Added MSI-X support for qtest PCI. Added MSI-X support for virtio-pci. Added MSI-X test case in virtio-blk-test. Signed-off-by: Marc Marí Signed-off-by: Stefan Hajnoczi --- tests/libqos/pci.c| 111 +++- tests/libqos/pci.h| 10 +++ tests

[Qemu-devel] [PULL 23/26] vmdk: fix vmdk_parse_extents() extent_file leaks

Signed-off-by: Stefan Hajnoczi Reviewed-by: Max Reitz Reviewed-by: Fam Zheng --- block/vmdk.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/block/vmdk.c b/block/vmdk.c index 07cb62c..9bf28f3 100644 --- a/block/vmdk.c +++ b/block/vmdk.c @@ -834,6 +834,7 @@ static int vmdk_parse_extents(c

[Qemu-devel] [PULL 04/26] virtio: Import virtio_vring.h

From: Fam Zheng This header has no further dependencies. It only has some stable data types and primitive functions, so we can copy it to include/hw/virtio in order to allow vring code (and its user virtio-blk dataplane) to be built unconditionally, even for cross compiling. Suggested-by: Paolo

[Qemu-devel] [PULL 03/26] pflash_cfi01: write flash contents to bdrv on incoming migration

From: Laszlo Ersek A drive that backs a pflash device is special: - it is very small, - its entire contents are kept in a RAMBlock at all times, covering the guest-phys address range that provides the guest's view of the emulated flash chip. The pflash device model keeps the drive (the host-

[Qemu-devel] [PULL 05/26] block: Always compile virtio-blk dataplane

From: Fam Zheng Dataplane doesn't depend on linux-aio any more, so we don't need the compiling condition now. Configure options are kept but just print a message. Signed-off-by: Fam Zheng Signed-off-by: Stefan Hajnoczi --- configure | 21 ++--- hw/block/M

[Qemu-devel] [PULL 15/26] block/archipelago: Use QEMU atomic builtins

From: Chrysostomos Nanakos Replace __sync builtins with ones provided by QEMU for atomic operations. Special thanks goes to Paolo Bonzini for his refactoring suggestion in order to use the already existing atomic builtins interface. Signed-off-by: Chrysostomos Nanakos Signed-off-by: Stefan Haj

[Qemu-devel] [PULL 02/26] pflash_cfi01: fixup stale DPRINTF() calls

From: Laszlo Ersek Signed-off-by: Laszlo Ersek Signed-off-by: Stefan Hajnoczi --- hw/block/pflash_cfi01.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hw/block/pflash_cfi01.c b/hw/block/pflash_cfi01.c index 2238f39..fddef39 100644 --- a/hw/block/pflash_cfi01.c +++ b/

[Qemu-devel] [PULL 01/26] block: kill tail whitespace in block.c

From: Liu Yuan Cc: Kevin Wolf Cc: Stefan Hajnoczi Signed-off-by: Liu Yuan Reviewed-by: Benoît Canet Signed-off-by: Stefan Hajnoczi --- block.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/block.c b/block.c index cb670fd..d06dd51 100644 --- a/block.c +++ b/block.c @@ -

[Qemu-devel] [PULL 00/26] Block patches

The following changes since commit 30eaca3acdf17d7bcbd1213eb149c02037edfb0b: Merge remote-tracking branch 'remotes/spice/tags/pull-spice-20140902-1' into staging (2014-09-02 10:26:10 +0100) are available in the git repository at: git://github.com/stefanha/qemu.git tags/block-pull-request

Re: [Qemu-devel] [PULL v3 0/3] QOM CPUState patch queue 2014-09-05

On 5 September 2014 15:39, Andreas Färber wrote: > Hello Peter, > > This is my (corrected) QOM CPU patch queue. Please pull. > > Regards, > Andreas > > Cc: Peter Maydell > > Cc: Eduardo Habkost > > The following changes since commit fd884c07658d02a96a882b8457d6d7a5cd71a407: > > Merge remote-tr

[Qemu-devel] [question] PIC and APIC

Greetings folks, I've been tracking down certain obscure failures that we see running our kernel on qemu x86 smp. Based on a few days diving into qemu internals it seems that the problems relate to mixing PIC and APIC-generated interrupts. I'd appreciate some help in understanding if this is a lim

Re: [Qemu-devel] [PATCH] virtio-pci: fix virtio-net child refcount in transports

Hi, > Subject: Re: [Qemu-devel] [PATCH] virtio-pci: fix virtio-net child refcount in > transports > > On Thu, Sep 04, 2014 at 07:41:32PM +0800, arei.gong...@huawei.com wrote: > > From: Gonglei > > > > object_initialize() leaves the object with a refcount of 1. > > object_property_add_child() add

Re: [Qemu-devel] [PATCH] virtio-pci: fix virtio-net child refcount in transports

Hi, > Subject: Re: [Qemu-devel] [PATCH] virtio-pci: fix virtio-net child refcount in > transports > > On Thu, Sep 04, 2014 at 07:41:32PM +0800, arei.gong...@huawei.com wrote: > > From: Gonglei > > > > object_initialize() leaves the object with a refcount of 1. > > object_property_add_child() add

Re: [Qemu-devel] qemu-system-s390x and Linux

Hi, Am 05.09.2014 15:55, schrieb Robert Święcki: > 1). Python doesn't work - it works under hercules though (the same / > almost identical image), depending on version it throws marshalling > assertions. > > 2). Kernel throws an error upon testing cryptographic routines (they > produce different

Re: [Qemu-devel] qcow2, lazy_refcounts and killing qemu

On Sat, Aug 30, 2014 at 03:53:13PM +0100, Richard W.M. Jones wrote: > I found out a few days ago that if you: > > (1) Open a qcow2 file that has lazy_refcounts = on and a backing file, and > > (2) Write lots of stuff, and > > (3) Kill qemu with SIGTERM [which I believed, maybe incorrectly, is a

Re: [Qemu-devel] [PATCH v2] qcow2: add update refcount table realization for update_refcount

On Mon, Sep 01, 2014 at 06:52:48PM +0800, Jun Li wrote: > When every item of refcount block is NULL, free refcount block and reset the > corresponding item of refcount table with NULL. > > Signed-off-by: Jun Li > --- By the way, test cases are definitely needed for this change. See tests/qemu-i

Re: [Qemu-devel] [PATCH v2] qcow2: add update refcount table realization for update_refcount

On Mon, Sep 01, 2014 at 06:52:48PM +0800, Jun Li wrote: How does this patch handle self-describing refcount blocks? I think they will keep the refcount block alive forever because your code will not decide to free them. This patch should also discard the refcount block if we decide to free it (i

Re: [Qemu-devel] [PATCH 2/2] util: Add an utility infrastructure used to compute an average on a time slice

On Fri, Sep 05, 2014 at 08:55:53AM -0600, Eric Blake wrote: > On 09/05/2014 08:21 AM, Benoît Canet wrote: > > The algorithm used was defined on the list while discussing the new IO > > accounting > > overhaul. > > See http://lists.nongnu.org/archive/html/qemu-devel/2014-08/msg04954.html > > > > S

Re: [Qemu-devel] [libvirt] IO accounting overhaul

The Friday 05 Sep 2014 à 16:30:31 (+0200), Kevin Wolf wrote : > Am 01.09.2014 um 13:41 hat Markus Armbruster geschrieben: > > Benoît Canet writes: > > > > > The Monday 01 Sep 2014 à 11:52:00 (+0200), Markus Armbruster wrote : > > >> Cc'ing libvirt following Stefan's lead. > > >> > > >> Benoît Ca

[Qemu-devel] [PATCH 0/6] ARM: -bios/-kernel + DTB boot roundup

This series contains the remaining bits and pieces I keep in my local tree to run the Tianocore/EDK2 UEFI bootloader under QEMU. Patch #1 has been posted by Peter before, and has been included for completeness. Patch #2 adds an output parameter to load_dtb() that is used by the DTB loading functi

[Qemu-devel] [PATCH 5/6] hw/arm/boot: load DTB as a ROM image

In order to make the device tree blob (DTB) available in memory not only at first boot, but also after system reset, use rom_blob_add_fixed() to install it into memory. Signed-off-by: Ard Biesheuvel --- hw/arm/boot.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/hw/arm/

[Qemu-devel] [PATCH 1/6] hw/arm/virt: Provide flash devices for boot ROMs

From: Peter Maydell Add two flash devices to the virt board, so that it can be used for running guests which want a bootrom image such as UEFI. We provide two flash devices to make it more convenient to provide both a read-only UEFI image and a read-write place to store guest-set UEFI config vari

[Qemu-devel] [PATCH 2/6] hw/arm/boot: return size of loaded DTB from load_dtb()

Add a dtb_size output parameter to load_dtb() so that we can find out what its memory footprint is. Signed-off-by: Ard Biesheuvel --- hw/arm/boot.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/hw/arm/boot.c b/hw/arm/boot.c index e32f2f415885..c103a8fdc941 100644 --

[Qemu-devel] [PATCH 4/6] hw/arm/boot: register cpu reset handlers if using -bios

When booting with -bios or -pflash rather than -kernel, we need to make sure reset handlers are registered. Signed-off-by: Ard Biesheuvel --- hw/arm/boot.c | 4 1 file changed, 4 insertions(+) diff --git a/hw/arm/boot.c b/hw/arm/boot.c index 8f5649a250fd..0cfc11d42962 100644 --- a/hw/arm/b

  1   2   3   >