On 2013年12月12日 02:11, Max Reitz wrote:
Allow specifying a reference to an existing block device (by name) for
bdrv_file_open() instead of a filename and/or options.
Signed-off-by: Max Reitz mre...@redhat.com
---
block.c | 27 ---
block/blkdebug.c |
Fam Zheng f...@redhat.com writes:
On 2013年11月28日 16:39, Fam Zheng wrote:
This series adds for point-in-time snapshot NBD exporting based on
blockdev-backup (variant of drive-backup with existing device as target).
We get a thin point-in-time snapshot by COW mechanism of drive-backup, and
On Do, 2013-12-12 at 09:51 +1000, Dave Airlie wrote:
Now the vgabios.c does a check of bar 0 and bar 1 to see if they are
0xfff1 masked, this protects against the the i/o bar but fails to
protect against the LFB one as PCI BARs don't encode the size just the
base address, and a 4k BAR can be
On 2013年12月12日 16:14, Markus Armbruster wrote:
Fam Zheng f...@redhat.com writes:
On 2013年11月28日 16:39, Fam Zheng wrote:
This series adds for point-in-time snapshot NBD exporting based on
blockdev-backup (variant of drive-backup with existing device as target).
We get a thin point-in-time
On Wed, Dec 11, 2013 at 01:19:16PM +0100, Paolo Bonzini wrote:
The object must be unref-ed when its variable goes out of scope.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
vl.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Reviewed-by: Stefan Hajnoczi
On Wed, Dec 11, 2013 at 01:19:17PM +0100, Paolo Bonzini wrote:
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
qom/object.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
Reviewed-by: Stefan Hajnoczi stefa...@redhat.com
On Wed, Dec 11, 2013 at 09:37:11PM +0100, Stefan Weil wrote:
The buildbot shows these compiler warnings:
block/vvfat.c: In function 'create_short_and_long_name':
block/vvfat.c:620: warning: array size (8) smaller than bound length (11)
block/vvfat.c:620: warning: array size (8) smaller than
This series adds for point-in-time snapshot NBD exporting based on
blockdev-backup (variant of drive-backup with existing device as target).
We get a thin point-in-time snapshot by COW mechanism of drive-backup, and
export it through built in NBD server. The steps are as below:
1. (SHELL)
This reuses the new bdrv_drop_intermediate.
Signed-off-by: Fam Zheng f...@redhat.com
---
block/stream.c | 28 +---
1 file changed, 1 insertion(+), 27 deletions(-)
diff --git a/block/stream.c b/block/stream.c
index 46bec7d..9cdcf0e 100644
--- a/block/stream.c
+++
Dropping intermediate could be useful both for commit and stream, and
BDS refcnt plus bdrv_swap could do most of the job nicely. It also need
some improvements in preparation for op blockers.
Signed-off-by: Fam Zheng f...@redhat.com
---
block.c| 152
Signed-off-by: Fam Zheng f...@redhat.com
---
block.c | 109 +-
block/mirror.c| 2 +-
include/block/block.h | 3 +-
include/block/block_int.h | 3 ++
4 files changed, 76 insertions(+), 41 deletions(-)
diff --git
This adds the enum of all the operations that can be taken on a block
device.
Signed-off-by: Fam Zheng f...@redhat.com
---
qapi-schema.json | 49 +
1 file changed, 49 insertions(+)
diff --git a/qapi-schema.json b/qapi-schema.json
index
Similar to drive-backup, but this command uses a device id as target
instead of creating/opening an image file.
Also add blocker on target bs, since the target is also a named device
now.
Signed-off-by: Fam Zheng f...@redhat.com
---
block/backup.c | 21 +
blockdev.c
This drops BlockDriverState.in_use with op_blockers:
- Call bdrv_op_block_all in place of bdrv_set_in_use(bs, 1).
- Call bdrv_op_unblock_all in place of bdrv_set_in_use(bs, 0).
- Check bdrv_op_is_blocked() in place of bdrv_in_use(bs).
The specific types are used, e.g. in place of
BlockDriverState.op_blockers is an array of lists with BLOCK_OP_TYPE_MAX
elements. Each list is a list of blockers of an operation type
(BlockOpType), that marks this BDS as currently blocked for a certain
type of operation with reason errors stored in the list. The rule of
usage is:
* BDS user
Drive backup is a read only operation on source bs. We want to allow
this specific case to enable image-fleecing. Note that when
image-fleecing job starts, the job still add its blocker to source bs,
and any other operation on it will be blocked by that.
Signed-off-by: Fam Zheng f...@redhat.com
Before operate on a BlockDriverState, respective types are checked
against bs-op_blockers and it will error out if there's a blocker.
Signed-off-by: Fam Zheng f...@redhat.com
---
block/snapshot.c | 11 +++
blockdev.c | 8
2 files changed, 19 insertions(+)
diff --git
This allows descent error information to be reported.
Signed-off-by: Fam Zheng f...@redhat.com
---
block/snapshot.c | 5 +++--
blockdev.c | 2 +-
include/block/snapshot.h | 3 ++-
qemu-img.c | 2 +-
savevm.c | 2 +-
5 files changed, 8
On Tue, Dec 10, 2013 at 04:23:25PM +0100, Kevin Wolf wrote:
Am 10.12.2013 um 16:11 hat Juan Quintela geschrieben:
I can do any of them. Votes for the people that attend?
As I guess he commutes everyday, moving the day will not help :p
I prefer 15:00 CET (14:00 UTC).
+1
Stefan
ping ...
this patch is not changed since v8,
can it get some comments?
Thanks!
liguang wrote:
Signed-off-by: liguanglig.f...@cn.fujitsu.com
---
include/migration/vmstate.h |4
savevm.c| 31 +++
2 files changed, 35 insertions(+), 0
On Tue, Dec 10, 2013 at 11:23 PM, Kevin Wolf kw...@redhat.com wrote:
Am 10.12.2013 um 16:11 hat Juan Quintela geschrieben:
Anthony can't assist this call, just in the middle of his commute. As
it looks like a good idea that he can assit, can we move the call?
Options so far are (his local
Am 12.12.2013 um 09:22 hat Stefan Hajnoczi geschrieben:
On Wed, Dec 11, 2013 at 09:37:11PM +0100, Stefan Weil wrote:
The buildbot shows these compiler warnings:
block/vvfat.c: In function 'create_short_and_long_name':
block/vvfat.c:620: warning: array size (8) smaller than bound length
We use the rom infrastructure to write firmware and/or initial kernel
blobs into guest address space. So we're basically emulating the cache
off phase on very early system bootup.
That phase is usually responsible for clearing the instruction cache for
anything it writes into cachable memory, to
Am 12.12.2013 um 08:51 hat Thomas Huth geschrieben:
On Thu, 12 Dec 2013 10:57:49 +0800
Wenchao Xia xiaw...@linux.vnet.ibm.com wrote:
+static int bdrv_refresh_limits(BlockDriverState *bs)
+{
+BlockDriver *drv = bs-drv;
+
+memset(bs-bl, 0, sizeof(bs-bl));
+
+
Am 12.12.2013 um 07:17 hat Peter Lieven geschrieben:
Am 11.12.2013 22:08, schrieb Kevin Wolf:
This function separates filling the BlockLimits from bdrv_open(), which
allows it to call it from other operations which may change the limits
(e.g. modifications to the backing file chain or
On 11.12.2013, at 20:30, Richard Henderson r...@twiddle.net wrote:
The first patch is purely mechanical. The subsequent patches
tidy things up as allowed by the new interfaces.
Reviewed-by: Alexander Graf ag...@suse.de
Alex
Il 12/12/2013 06:47, Liu, Jinsong ha scritto:
Paolo Bonzini wrote:
Il 11/12/2013 09:31, Liu, Jinsong ha scritto:
Paolo, comments for version 2?
I think I commented that it's fine, I'm just waiting for a rebase on
top of the generic patches.
Paolo
Thanks! common MPX definiation patches
Am 12.12.2013 um 07:09 hat Peter Lieven geschrieben:
Should it be possible to boot from a 4K-native drive with this series?
If yes, I will run some test with some new iSCSI arrays we got for testing
they can export 4k blocksize LUNs.
Yes, you should be able to use a 4k-native backend for a
Hi,
I saw a missing return below:
On 11 December 2013 23:01, Peter Maydell peter.mayd...@linaro.org wrote:
From: Alex Bennée alex.ben...@linaro.org
This patch support the basic load and store pair instructions and
includes the generic helper functions:
* do_gpr_st()
* do_fp_st()
*
Am 12.12.2013 10:47, schrieb Kevin Wolf:
Am 12.12.2013 um 07:09 hat Peter Lieven geschrieben:
Should it be possible to boot from a 4K-native drive with this series?
If yes, I will run some test with some new iSCSI arrays we got for testing
they can export 4k blocksize LUNs.
Yes, you should be
On 2013年12月12日 02:11, Max Reitz wrote:
Add a test for the new blkdebug/blkverify interface.
Signed-off-by: Max Reitz mre...@redhat.com
---
tests/qemu-iotests/071 | 201 +
tests/qemu-iotests/071.out | 73
On 2013年12月12日 02:10, Max Reitz wrote:
Currently, the configuration of blkdebug and blkverify is done through
the filename alone. There is now way of manually choosing blkdebug or
blkverify as a driver and using a normal image filename.
In the case of blkdebug, the filename starts with the
Paolo Bonzini wrote:
Il 12/12/2013 06:47, Liu, Jinsong ha scritto:
Paolo Bonzini wrote:
Il 11/12/2013 09:31, Liu, Jinsong ha scritto:
Paolo, comments for version 2?
I think I commented that it's fine, I'm just waiting for a rebase
on top of the generic patches.
Paolo
Thanks!
claudio.font...@linaro.org writes:
Hi,
I saw a missing return below:
snip
+default: /* Failed decoder tree? */
+unallocated_encoding(s);
+break;
+}
This doesn't seem right (break instead of return):
default:
unallocated_encoding(s);
return;
}
Good
On 12 December 2013 11:43, Alex Bennée alex.ben...@linaro.org wrote:
claudio.font...@linaro.org writes:
Hi,
I saw a missing return below:
snip
+default: /* Failed decoder tree? */
+unallocated_encoding(s);
+break;
+}
This doesn't seem right (break instead of
Gal Hammer gham...@redhat.com writes:
Fix a bug that was introduced in commit 386a5a1e. A removal of a device
set the chr handlers to NULL. However when the device is plugged back,
its read callback is not restored so data can't be transftered from the
host to the guest (e.g. via the
On 12 December 2013 12:45, Peter Maydell peter.mayd...@linaro.org wrote:
On 12 December 2013 11:43, Alex Bennée alex.ben...@linaro.org wrote:
claudio.font...@linaro.org writes:
Hi,
I saw a missing return below:
snip
+default: /* Failed decoder tree? */
+
Il 12/12/2013 03:52, Fernando Luis Vázquez Cao ha scritto:
On 12/09/2013 05:50 PM, Fernando Luis Vázquez Cao wrote:
On 12/06/2013 11:22 PM, Marcelo Tosatti wrote:
On Fri, Dec 06, 2013 at 05:24:18PM +0900, Fernando Luis Vázquez Cao
wrote:
I also wanted to make sure that the initialization that
Am 12.12.2013 um 09:23 hat Fam Zheng geschrieben:
This adds the enum of all the operations that can be taken on a block
device.
Signed-off-by: Fam Zheng f...@redhat.com
---
qapi-schema.json | 49 +
1 file changed, 49 insertions(+)
diff
Hi,
+if (port_offset) {
+int baseport;
+errno = 0;
+baseport = strtol(port, NULL, 10);
rant
WHY is strtol() such a PAINFUL interface to use correctly?
Crossed my mind too after reading the manpage, which sayed you should
clear errno to reliable detect
On 2013年12月12日 20:21, Kevin Wolf wrote:
Am 12.12.2013 um 09:23 hat Fam Zheng geschrieben:
This adds the enum of all the operations that can be taken on a block
device.
Signed-off-by: Fam Zheng f...@redhat.com
---
qapi-schema.json | 49 +
1
Hi,
Isn't this backwards-incompatible?
Yes. I think it is the correct thing nevertheless.
Fine by me, let's just make sure we document it well. Can you start the
2.0 changelog wiki page?
-ENOACCOUNT
Anthony? Can you add me? uid kraxel please.
cheers,
Gerd
Am 12.12.2013 10:47, schrieb Kevin Wolf:
Am 12.12.2013 um 07:09 hat Peter Lieven geschrieben:
Should it be possible to boot from a 4K-native drive with this series?
If yes, I will run some test with some new iSCSI arrays we got for testing
they can export 4k blocksize LUNs.
Yes, you should be
On Tue, Dec 10, 2013 at 04:23:25PM +0100, Kevin Wolf wrote:
Am 10.12.2013 um 16:11 hat Juan Quintela geschrieben:
Anthony can't assist this call, just in the middle of his commute. As
it looks like a good idea that he can assit, can we move the call?
Options so far are (his local
Fam Zheng f...@redhat.com writes:
This adds the enum of all the operations that can be taken on a block
device.
All operations? All blockable operations? Something else?
Signed-off-by: Fam Zheng f...@redhat.com
---
qapi-schema.json | 49 +
On Thu, Dec 12, 2013 at 05:01:55PM +0800, Zhi Yong Wu wrote:
On Tue, Dec 10, 2013 at 11:23 PM, Kevin Wolf kw...@redhat.com wrote:
Am 10.12.2013 um 16:11 hat Juan Quintela geschrieben:
Anthony can't assist this call, just in the middle of his commute. As
it looks like a good idea that he
Fam Zheng f...@redhat.com writes:
BlockDriverState.op_blockers is an array of lists with BLOCK_OP_TYPE_MAX
elements. Each list is a list of blockers of an operation type
(BlockOpType), that marks this BDS as currently blocked for a certain
type of operation with reason errors stored in the
Fam Zheng f...@redhat.com writes:
Signed-off-by: Fam Zheng f...@redhat.com
---
block.c | 109
+-
block/mirror.c| 2 +-
include/block/block.h | 3 +-
include/block/block_int.h | 3 ++
4 files changed, 76
On 2013年12月12日 20:49, Markus Armbruster wrote:
Fam Zheng f...@redhat.com writes:
This adds the enum of all the operations that can be taken on a block
device.
All operations? All blockable operations? Something else?
All QMP operations those apply on device, plus all operations those
On Mi, 2013-12-11 at 11:12 +1000, Dave Airlie wrote:
On Wed, Dec 11, 2013 at 12:35 AM, Gerd Hoffmann kra...@redhat.com wrote:
Hi,
The biggest changes were in the input handling, where SDL2 has done a major
overhaul, and I've had to include a generated translation file to get from
SDL2
during testing around with 4k LUNs a bad target implementation
triggert an -EIO in iscsi_get_block_status, but it got never caught
resulting in an invinite loop.
CC: qemu-sta...@nongnu.org
Signed-off-by: Peter Lieven p...@kamp.de
---
block.c |5 +
1 file changed, 5 insertions(+)
diff
On Thu, Dec 12, 2013 at 8:53 PM, Michael S. Tsirkin m...@redhat.com wrote:
On Thu, Dec 12, 2013 at 05:01:55PM +0800, Zhi Yong Wu wrote:
On Tue, Dec 10, 2013 at 11:23 PM, Kevin Wolf kw...@redhat.com wrote:
Am 10.12.2013 um 16:11 hat Juan Quintela geschrieben:
Anthony can't assist this call,
Il 11/12/2013 17:55, Wei Liu ha scritto:
On Wed, Dec 11, 2013 at 05:11:37PM +0100, Fabio Fantoni wrote:
Il 11/12/2013 16:38, Wei Liu ha scritto:
On Wed, Dec 11, 2013 at 02:41:57PM +0100, Fabio Fantoni wrote:
[...]
Thanks for your reply.
Before starting bisection I tried with qemu 1.3.1 from
This series moves the event loop thread out of dataplane code. It makes
-iothread id=foo a separate concept. This makes it possible to bind several
devices to the same iothread.
Syntax:
qemu -iothread id=iothread0 \
-device virtio-blk-pci,iothread=iothread0,x-data-plane=on,...
For
QemuMutex does not guarantee fairness and cannot be acquired
recursively:
Fairness means each locker gets a turn and the scheduler cannot cause
starvation.
Recursive locking is useful for composition, it allows a sequence of
locking operations to be invoked atomically by acquiring the lock
It can be useful to run an AioContext from a thread which normally does
not own the AioContext. For example, request draining can be
implemented by acquiring the AioContext and looping aio_poll() until all
requests have been completed.
The following pattern should work:
/* Event loop thread
This is a stand-in for Michael Roth's QContext. I expect this to be
replaced once QContext is completed.
The IOThread object is an AioContext event loop thread. This patch adds
the concept of multiple event loop threads, allowing users to define
them.
When SMP guests run on SMP hosts it makes
get_pointer() assumes the string has unspecified lifetime (at least as
long as the object is alive). In some cases we can only produce a
temporary string that should be freed when get_pointer() is done.
Signed-off-by: Stefan Hajnoczi stefa...@redhat.com
---
hw/core/qdev-properties-system.c | 14
Today virtio-blk dataplane uses a 1:1 device-per-thread model. Now that
IOThreads have been introduced we can generalize this to N:M devices per
threads.
This patch drops thread code from dataplane in favor of running inside
an IOThread AioContext.
As a bonus we solve the case where a guest
The -object option has several limitations that prevent it from fully
instantiating an IOThread. Igor Mammedov and Paolo Bonzini are fixing
-object.
In the meantime, add a traditional -iothread command-line option that
takes an identifier and keeps a global list of IOThreads.
Signed-off-by:
Add a iothread qdev property type so devices can be hooked up to an
IOThread from the comand-line:
qemu -iothread id=iothread0 \
-device some-device,iothread=iothread0
Signed-off-by: Stefan Hajnoczi stefa...@redhat.com
---
hw/core/qdev-properties-system.c | 51
Am 12.12.2013 um 09:23 hat Fam Zheng geschrieben:
Dropping intermediate could be useful both for commit and stream, and
BDS refcnt plus bdrv_swap could do most of the job nicely. It also need
some improvements in preparation for op blockers.
Signed-off-by: Fam Zheng f...@redhat.com
---
On Thu, Dec 12, 2013 at 01:57:05PM +0100, Peter Lieven wrote:
during testing around with 4k LUNs a bad target implementation
triggert an -EIO in iscsi_get_block_status, but it got never caught
resulting in an invinite loop.
CC: qemu-sta...@nongnu.org
Signed-off-by: Peter Lieven p...@kamp.de
On Wed, Dec 11, 2013 at 11:07:20AM -0800, Richard Henderson wrote:
On 12/11/2013 06:07 AM, Aurelien Jarno wrote:
Cc: Richard Henderson r...@twiddle.net
Signed-off-by: Aurelien Jarno aurel...@aurel32.net
---
tcg/tcg.h |6 ++
1 file changed, 6 insertions(+)
diff --git
Signed-off-by: Aurelien Jarno aurel...@aurel32.net
---
target-mips/translate.c | 119 +--
1 file changed, 52 insertions(+), 67 deletions(-)
diff --git a/target-mips/translate.c b/target-mips/translate.c
index e302734..ef0a2c3 100644
---
On Thu, Dec 12, 2013 at 5:07 AM, Xin Tong trent.t...@gmail.com wrote:
see questions below.
On Tue, Dec 10, 2013 at 12:25 AM, Alex Bennée alex.ben...@linaro.org wrote:
trent.t...@gmail.com writes:
Does anyone have profiles on how much time QEMU spends in translating
instructions. QEMU does
On Wed, Dec 11, 2013 at 04:36:14PM +0200, Mar Tsan wrote:
Hello. I'm working with Android Emulator (which as I understand is
something like QEMU but not the same) and I would like to print messages
concerning the Emulator. What I mean is that I want to edit the source code
of the Emulator
On 12/12/2013 01:09, Sean Xie wrote:
Hi all,
Recently I am struggling in examing the effect of host kernel I/O
stacks on high-speed SSD, especially the new PCIe SSD, without
the availability of the necessary hardware. After several reading
online I found out QEMU+SystemC model environment
On Wed, Dec 11, 2013 at 08:55:33PM +, Yaodong Yang wrote:
I have a quick question about the virtio inside qemu. When the user
application sends to a specific virtual disk a large number of read requests
in a very short time, where should these requests be queued? Inside the
virtqueue?
Fam Zheng f...@redhat.com writes:
This drops BlockDriverState.in_use with op_blockers:
- Call bdrv_op_block_all in place of bdrv_set_in_use(bs, 1).
- Call bdrv_op_unblock_all in place of bdrv_set_in_use(bs, 0).
- Check bdrv_op_is_blocked() in place of bdrv_in_use(bs).
The specific
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
hw/usb/host-libusb.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/hw/usb/host-libusb.c b/hw/usb/host-libusb.c
index fd320cd..164adf8 100644
--- a/hw/usb/host-libusb.c
+++ b/hw/usb/host-libusb.c
@@ -898,6 +898,19 @@ static
Fam Zheng f...@redhat.com writes:
This allows descent error information to be reported.
Signed-off-by: Fam Zheng f...@redhat.com
---
block/snapshot.c | 5 +++--
blockdev.c | 2 +-
include/block/snapshot.h | 3 ++-
qemu-img.c | 2 +-
savevm.c
Fam Zheng f...@redhat.com writes:
Before operate on a BlockDriverState, respective types are checked
against bs-op_blockers and it will error out if there's a blocker.
Signed-off-by: Fam Zheng f...@redhat.com
So this patch adds protection against two of the same kind
simultaneously. How
On Wed, Dec 11, 2013 at 09:22:13PM +1100, Alexey Kardashevskiy wrote:
With the great help from Paolo, I am presenting yet another try of bootindex
support on sPAPR, this time with some QOM fixes. Details are in the commit
messages.
Please, comment. Thanks.
Alexey Kardashevskiy (5):
On Wed, Dec 11, 2013 at 12:59:37PM +0100, mreza...@redhat.com wrote:
From: Miroslav Rezanina mreza...@redhat.com
Function hpet_find could not be used for checking hpet availability becouse
it was not build when hpet was disabled.
To allow proper use of this function, moving it from
On Thu, 12 Dec 2013 08:23:06 +0100
Markus Armbruster arm...@redhat.com wrote:
Peter Crosthwaite peter.crosthwa...@xilinx.com writes:
On Wed, Dec 11, 2013 at 11:57 PM, Markus Armbruster arm...@redhat.com
wrote:
Peter Crosthwaite peter.crosthwa...@xilinx.com writes:
Following our
Am 12.12.2013 um 14:31 hat Stefan Hajnoczi geschrieben:
On Thu, Dec 12, 2013 at 01:57:05PM +0100, Peter Lieven wrote:
during testing around with 4k LUNs a bad target implementation
triggert an -EIO in iscsi_get_block_status, but it got never caught
resulting in an invinite loop.
Il 12/12/2013 13:52, Michael S. Tsirkin ha scritto:
On Tue, Dec 10, 2013 at 04:23:25PM +0100, Kevin Wolf wrote:
Am 10.12.2013 um 16:11 hat Juan Quintela geschrieben:
Anthony can't assist this call, just in the middle of his commute. As
it looks like a good idea that he can assit, can we
On Thu, Dec 05, 2013 at 11:33:48PM +, Peter Maydell wrote:
On 5 December 2013 22:33, Michael Roth mdr...@linux.vnet.ibm.com wrote:
Some kernels program a 0 address for io regions. PCI 3.0 spec
sectio 6.2.5.1 doesn't seem to disallow this.
Hmm. The last PCI spec I looked at said 0
The GStaticMutex API was deprecated in glib 2.32. We cannot switch over
to GMutex unconditionally since we would drop support for older glib
versions. But the deprecated API warnings during build are annoying so
use static GMutex when possible.
Signed-off-by: Stefan Hajnoczi stefa...@redhat.com
Hello everyone,
I am having trouble with my qemu guests. I am facing buffer input output
errors on the guests' kernel log:
[TIMESTAMP] Buffer I/O error on device vda1, logical block XX
[TIMESTAMP] end_request: I/O error, dev vda, sector XX
I am also reading in the qemu log:
On Thu, Dec 12, 2013 at 02:10:23PM +0100, Fabio Fantoni wrote:
[...]
I did some other tests, I narrowed down the commit range to the one between:
commit c9fea5d701f8fd33f0843728ec264d95cee3ed37 Mon, 22 Jul 2013
15:14:18 (Merge remote-tracking branch 'bonzini/iommu-for-anthony')
where there
v5:
block empty node names [Kevin]
factorize setting of node-name option [Kevin]
NULL terminate node_name on removal [Kevin]
make query-named-block-nodes return BlockDeviceInfo structure [Eric]
Change some doc in query-named-block-nodes [Eric]
Document the choice of the QMP
Signed-off-by: Benoit Canet ben...@irqsave.net
---
block.c | 38 ++
1 file changed, 38 insertions(+)
diff --git a/block.c b/block.c
index 481d566..1c57f0d 100644
--- a/block.c
+++ b/block.c
@@ -735,6 +735,39 @@ static int bdrv_open_flags(BlockDriverState *bs,
Add the minimum of code to prepare for the following patches.
Signed-off-by: Benoit Canet ben...@irqsave.net
---
block.c | 57 +++
include/block/block.h | 1 +
include/block/block_int.h | 9 +++-
3 files changed, 52
There was two candidate ways to implement named node manipulation:
1)
{ 'command': 'block_passwd', 'data': {'*device': 'str',
'*node-name': 'str', 'password': 'str'}
}
2)
{ 'command': 'block_passwd', 'data': {'device': 'str',
Signed-off-by: Benoit Canet ben...@irqsave.net
---
block.c | 18 +
block/qapi.c | 109 +-
blockdev.c| 5 +++
include/block/block.h | 1 +
include/block/qapi.h | 1 +
qapi-schema.json | 16
Signed-off-by: Benoit Canet ben...@irqsave.net
---
blockdev.c | 18 ++
hmp.c| 2 +-
qapi-schema.json | 10 --
qmp-commands.hx | 3 ++-
4 files changed, 25 insertions(+), 8 deletions(-)
diff --git a/blockdev.c b/blockdev.c
index ebb8f48..374d03d 100644
Signed-off-by: Benoit Canet ben...@irqsave.net
---
blockdev.c | 55 ---
hmp.c| 4 +++-
qapi-schema.json | 13 ++---
qmp-commands.hx | 11 ++-
4 files changed, 71 insertions(+), 12 deletions(-)
diff --git
Signed-off-by: Benoit Canet ben...@irqsave.net
---
block.c | 65 ---
block/blkverify.c | 2 +-
blockdev.c| 2 +-
include/block/block.h | 20 +++
include/block/block_int.h | 12 ++---
5
12.12.2013 18:52, Stefan Hajnoczi wrote:
The GStaticMutex API was deprecated in glib 2.32. We cannot switch over
to GMutex unconditionally since we would drop support for older glib
versions. But the deprecated API warnings during build are annoying so
use static GMutex when possible.
On 12/12/2013 05:02 AM, Markus Armbruster wrote:
Gal Hammer gham...@redhat.com writes:
Fix a bug that was introduced in commit 386a5a1e. A removal of a device
set the chr handlers to NULL. However when the device is plugged back,
its read callback is not restored so data can't be transftered
On Wed, 11 Dec 2013 20:57:43 +0100
Markus Armbruster arm...@redhat.com wrote:
Please spell it pluggable, both in C identifiers and strings.
Sure,
I'll respin series since it will touch several patches.
Hi,
is anyone aware of a problem with a clock jump in Windows (observed in Server
2012)
where after a successful live migration the clock jumps roughly 2 days into the
future?
Maybe this is already fixed we observed this with qemu-kvm-1.2.0. I have not
yet managed
to reproduce this, but it
Il 12/12/2013 16:23, Wei Liu ha scritto:
On Thu, Dec 12, 2013 at 02:10:23PM +0100, Fabio Fantoni wrote:
[...]
I did some other tests, I narrowed down the commit range to the one between:
commit c9fea5d701f8fd33f0843728ec264d95cee3ed37 Mon, 22 Jul 2013
15:14:18 (Merge remote-tracking branch
On Tue, 10 Dec 2013 18:00:23 +0100
Paolo Bonzini pbonz...@redhat.com wrote:
These allow hotplugging (and hot-unplugging without leaking an object)
virtio-rng devices. They can also be used for memory hotplug.
Paolo Bonzini (5):
rng: initialize file descriptor to -1
qom: fix leak for
On 12/12/2013 05:27 AM, Gerd Hoffmann wrote:
Hi,
+if (port_offset) {
+int baseport;
+errno = 0;
+baseport = strtol(port, NULL, 10);
rant
WHY is strtol() such a PAINFUL interface to use correctly?
Crossed my mind too after reading the manpage, which
Last call for review/testing/comments on this patchset:
I'm planning to do a target-arm pullreq early next week
which will include this patchset.
thanks
-- PMM
On 5 December 2013 15:23, Peter Maydell peter.mayd...@linaro.org wrote:
Slightly over-eager ping for code review and/or testing, since
On 5 December 2013 17:54, Ard Biesheuvel ard.biesheu...@linaro.org wrote:
This adds support for the AESE/AESD/AESMC/AESIMC instructions that
are available on some v8 implementations of Aarch32.
Signed-off-by: Ard Biesheuvel ard.biesheu...@linaro.org
I finally managed to get set up to compare
On 5 December 2013 21:35, Roy Franz roy.fr...@linaro.org wrote:
For handling CFI and device ID reads, we need to not only know the
width that a NOR flash device is configured for, but also its maximum
width. The maximum width addressing mode is used for multi-width
parts no matter which width
1 - 100 of 178 matches
Mail list logo
