Il 12/09/2013 05:25, Liu Ping Fan ha scritto:
v5:
use stand compat property to fix hpet intcap on pc-q35, while on pc-piix,
hard code intcap as IRQ2
v4:
use stand compat property to fix hpet intcap
v3:
change hpet interrupt capablity on board's demand
Liu Ping Fan (5):
Il 12/09/2013 04:52, Fam Zheng ha scritto:
define unnest-dir
$(foreach var,$(nested-vars),$(call push-var,$(var),$1/))
$(eval obj-parent-$1 := $(obj))
$(eval obj := $(if $(obj),$(obj)/$1,$1))
$(eval include $(SRC_PATH)/$1/Makefile.objs)
+$(foreach v,$(nested-vars),$(call
piix 1.7 is the default.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
hw/i386/pc_piix.c | 19 +--
hw/i386/pc_q35.c | 17 -
2 files changed, 33 insertions(+), 3 deletions(-)
diff --git a/hw/i386/pc_piix.c b/hw/i386/pc_piix.c
index 66551b4..0ade373 100644
This series implements feature of shared object building as described in:
http://wiki.qemu.org/Features/Modules
The main idea behind modules is to isolate dependencies on third party
libraries from qemu executables, such as libglusterfs or librbd, so that the
end users can install core qemu
Makefile.target includes rule.mak and unnested common-obj-y, then prefix
them with '../', this will ignore object specific QEMU_CFLAGS in subdir
Makefile.objs:
$(obj)/curl.o: QEMU_CFLAGS += $(CURL_CFLAGS)
Because $(obj) here is './block', instead of '../block'. This doesn't
hurt compiling
Adds extract-libs in LINK to expand any per object libs, the syntax to define
such a libs options is like:
foo.o-libs := $(CURL_LIBS)
in block/Makefile.objs.
Similarly,
foo.o-cflags := $(FOO_CFLAGS)
is also supported.
foo.o must be listed a nested var (e.g. common-obj-y) to
From: Peter Maydell peter.mayd...@linaro.org
Delete an unnecessary dependency for cocoa.o; we already have
a general rule that tells Make that we can build a .o file
from a .m source using an ObjC compiler, so this specific
rule is unnecessary. Further, it is using the dubious construct
Signed-off-by: Fam Zheng f...@redhat.com
---
.gitignore | 3 +++
1 file changed, 3 insertions(+)
diff --git a/.gitignore b/.gitignore
index d2c5c2f..4d0ac09 100644
--- a/.gitignore
+++ b/.gitignore
@@ -63,6 +63,9 @@ fsdev/virtfs-proxy-helper.pod
*.cp
*.dvi
*.exe
+*.dll
+*.so
+*.mo
*.fn
*.ky
Install all the subdirs for modules under configure option moddir.
Signed-off-by: Fam Zheng f...@redhat.com
---
Makefile | 6 ++
1 file changed, 6 insertions(+)
diff --git a/Makefile b/Makefile
index ef76967..00c2a52 100644
--- a/Makefile
+++ b/Makefile
@@ -360,6 +360,12 @@ install-datadir
Add necessary rules and flags for shared object generation.
$(common-obj-m) will include $(block-obj-m), like $(common-obj-y) does
for $(block-obj-y). The new rules introduced here are:
0) For all %.so compiling:
QEMU_CFLAGS += -fPIC
1) %.o in $(common-obj-m) is compiled to %.o, then linked
Added three types of modules:
typedef enum {
MODULE_LOAD_BLOCK = 0,
MODULE_LOAD_UI,
MODULE_LOAD_NET,
MODULE_LOAD_MAX,
} module_load_type;
and their loading function:
void module_load(module_load_type).
which loads all .so files in a subdir under
The converted block drivers are:
curl
iscsi
rbd
ssh
glusterfs
no longer adds flags and libs for them to global variables, instead
create config-host.mak variables like FOO_CFLAGS and FOO_LIBS, which is
used as per object cflags and libs.
Signed-off-by: Fam Zheng
On 09/11/2013 07:27 PM, Paolo Bonzini wrote:
Il 11/09/2013 13:06, Juan Quintela ha scritto:
And I think that the right solution is make qemu_get_rate_limit() to
return -1 in case of error (or the error, I don't care).
You might do both things, it would avoid the useless g_usleep you
pointed
On Thu, 09/12 08:34, Paolo Bonzini wrote:
Il 12/09/2013 04:52, Fam Zheng ha scritto:
define unnest-dir
$(foreach var,$(nested-vars),$(call push-var,$(var),$1/))
$(eval obj-parent-$1 := $(obj))
$(eval obj := $(if $(obj),$(obj)/$1,$1))
$(eval include
On 09/11/2013 04:54 AM, junqing.w...@cs2c.com.cn wrote:
Hi,
The first is that if the VM failure happen in the middle on the live
migration the backup VM state will be inconsistent which means you can't
failover to it.
Yes, I have concerned about this problem. That is why we need a
On 09/11/2013 02:27 PM, Paolo Bonzini wrote:
Il 11/09/2013 13:06, Juan Quintela ha scritto:
And I think that the right solution is make qemu_get_rate_limit() to
return -1 in case of error (or the error, I don't care).
You might do both things, it would avoid the useless g_usleep you
pointed
On Thu, Sep 12, 2013 at 2:29 PM, Paolo Bonzini pbonz...@redhat.com wrote:
Il 12/09/2013 05:25, Liu Ping Fan ha scritto:
v5:
use stand compat property to fix hpet intcap on pc-q35, while on pc-piix,
hard code intcap as IRQ2
v4:
use stand compat property to fix hpet intcap
v3:
Il 11/09/2013 20:26, Marcel Apfelbaum ha scritto:
Qemu is expected to quit if the same boot index value is used by two devices.
However, hot-plugging a device with a bootindex value already used should
fail with a friendly message rather than quitting a running VM.
I think the problem is right
Hi Max,
Thanks for your patience and help.
I`ve tried to do what you said, but the problem doesn`t go away.
And actually i cannot add a new register to the fpga device, because the
fpga device i`m emulating already exists in the real world.
So i cannot change anything about hardware
On Thu, Sep 12, 2013 at 11:49 AM, Xie Xianshan xi...@cn.fujitsu.com wrote:
Hi Max,
Thanks for your patience and help.
I`ve tried to do what you said, but the problem doesn`t go away.
And actually i cannot add a new register to the fpga device, because the
fpga device i`m emulating
On 10.09.2013 10:45, Peter Maydell wrote:
On 10 September 2013 09:27, Claudio Fontana claudio.font...@huawei.com
wrote:
On another side, I end up having to manually revert some parts
of these which you put as prerequisites, during bisection when
landing after them, which is a huge time drain
On Tue, Sep 10, 2013 at 02:42:10PM -0500, Michael Roth wrote:
Quoting Stefan Hajnoczi (2013-08-29 02:43:02)
On Thu, Aug 29, 2013 at 09:09:45AM +0800, Wenchao Xia wrote:
于 2013-8-28 16:49, Stefan Hajnoczi 写道:
On Wed, Aug 28, 2013 at 11:25:33AM +0800, Wenchao Xia wrote:
+void
On 10.09.2013 15:16, Richard Henderson wrote:
On 09/10/2013 01:27 AM, Claudio Fontana wrote:
There are two aspects.
On one side, although some changes do not break anything, I see some
problems in them.
Then let us discuss them, sooner rather than later.
Putting them as a prerequisite
On Thu, Sep 12, 2013 at 11:10:01AM +0800, liu ping fan wrote:
Do you think this series is ready to be merged?
I have some code to run hpet on a dedicated thread, and in theory it
will rely on this.
Yes, it is ready. To ease the merge I have rebased it and sent a new
revision.
Stefan
On Thu, Sep 12, 2013 at 4:17 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Thu, Sep 12, 2013 at 11:10:01AM +0800, liu ping fan wrote:
Do you think this series is ready to be merged?
I have some code to run hpet on a dedicated thread, and in theory it
will rely on this.
Yes, it is ready.
Hi,
I've notice that the virtio-serial Windows' driver doesn't use MSI-X
vectors when running using upstream qemu or
qemu-kvm-1.2.2-13.fc18.x86_64. The same VM works with MSI-X when using
qemu-kvm-0.12.1.2-2.355.el6.x86_64.
From what I saw, Windows is trying to enable MSI-X by writing a 2
On Wed, Sep 11, 2013 at 12:57:58PM +0200, Vincenzo Maffione wrote:
Thanks for the help!
Actually I've found out that the variable copied I use in this patch can
be removed, we can simply increment the variable ba instead (ba +=
iov_copy).
I have the patch v3 to do that ready. Do you think
On 02.09.2013 19:54, Richard Henderson wrote:
Signed-off-by: Richard Henderson r...@twiddle.net
---
tcg/aarch64/tcg-target.c | 28 +++-
1 file changed, 7 insertions(+), 21 deletions(-)
diff --git a/tcg/aarch64/tcg-target.c b/tcg/aarch64/tcg-target.c
index
On 02.09.2013 19:54, Richard Henderson wrote:
Signed-off-by: Richard Henderson r...@twiddle.net
---
tcg/aarch64/tcg-target.c | 44 ++--
1 file changed, 22 insertions(+), 22 deletions(-)
diff --git a/tcg/aarch64/tcg-target.c b/tcg/aarch64/tcg-target.c
On 02.09.2013 19:54, Richard Henderson wrote:
Signed-off-by: Richard Henderson r...@twiddle.net
---
tcg/aarch64/tcg-target.c | 20 +++-
1 file changed, 7 insertions(+), 13 deletions(-)
diff --git a/tcg/aarch64/tcg-target.c b/tcg/aarch64/tcg-target.c
index bde4c72..79a447d
hi,
At the moment in your implementation the prefetch buffer can be very large
(several copies of guest memory size) are you planning to address this
issue? I agree but we need some way to notify the user of such problem.
This issue has been handled (maybe not in the best way). The prefetch
qemu-iotests number 007 doesn't do test image cleanup. This will affect
those protocols that expect a clean state before every test. Hence
ensure that test image is cleaned up in this test.
Signed-off-by: Bharata B Rao bhar...@linux.vnet.ibm.com
---
tests/qemu-iotests/007 | 2 +-
1 file changed,
pty_chr_timer first calls pty_chr_update_read_handler(), then clears
timer_tag (because it is a one-shot timer). This is the wrong order
though. pty_chr_update_read_handler might re-arm time timer, and the
new timer_tag gets overwitten in that case.
This leads to crashes when unplugging a pty
On Tue, Sep 10, 2013 at 06:40:04PM +0200, Paolo Bonzini wrote:
The UUID is unique even across multiple hosts, thus it is
better than a VM name even if it is less user-friendly.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
block/iscsi.c | 23 ---
Hi,
Bugfix for the pty chardev which might segfault on unplug.
Has been on the list for quite a while, wasn't picked up so far,
so I'll try a single-patch-pull-request now ...
please pull,
Gerd
The following changes since commit 2d1fe1873a984d1c2c89ffa3d12949cafc718551:
Merge
On Thu, 2013-09-12 at 09:49 +0200, Paolo Bonzini wrote:
Il 11/09/2013 20:26, Marcel Apfelbaum ha scritto:
Qemu is expected to quit if the same boot index value is used by two
devices.
However, hot-plugging a device with a bootindex value already used should
fail with a friendly message
On Thu, Sep 12, 2013 at 11:23:46AM +0300, Gal Hammer wrote:
Hi,
I've notice that the virtio-serial Windows' driver doesn't use MSI-X
vectors when running using upstream qemu or
qemu-kvm-1.2.2-13.fc18.x86_64. The same VM works with MSI-X when
using qemu-kvm-0.12.1.2-2.355.el6.x86_64.
From
On Wed, Sep 11, 2013 at 05:38:07PM +0200, Kevin Wolf wrote:
Am 11.09.2013 um 17:32 hat Gabriel Kerneis geschrieben:
On Wed, Sep 11, 2013 at 05:24:55PM +0200, Kevin Wolf wrote:
In config-host.make we do get:
CONFIG_COROUTINE_POOL=0
But when config-host.h is generated from
This patch implements the NetClientInfo.receive_iov method for the
e1000 device emulation. In this way a network backend that uses
qemu_sendv_packet() can deliver the fragmented packet without
requiring an additional copy in the frontend/backend network code
(nc_sendv_compat() function).
The
On 12 September 2013 00:08, Richard Henderson r...@twiddle.net wrote:
There have been two patches posted for this uninitialized warning, outstanding
since June 14. I still encounter this daily...
Looks like material for -trivial to me, cc'ing.
-- PMM
Il 12/09/2013 10:38, Stefan Hajnoczi ha scritto:
On Tue, Sep 10, 2013 at 06:40:04PM +0200, Paolo Bonzini wrote:
The UUID is unique even across multiple hosts, thus it is
better than a VM name even if it is less user-friendly.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
On 18.07.2013 16:14, Paolo Bonzini wrote:
Il 18/07/2013 15:55, ronnie sahlberg ha scritto:
bdrv-write_zeroes will use writesame16 and set the unmap flag only if
BDRV_MAY_DISCARD == 1 and BDRV_O_UNMAP == 1 and lbprz == 1.
When you use WRITESAME16 you can ignore the lbprz flag.
Just send a
On Wed, Sep 11, 2013 at 04:08:01PM -0700, Richard Henderson wrote:
There have been two patches posted for this uninitialized warning, outstanding
since June 14. I still encounter this daily...
I'm still happy with the patch.
Michael: Do you want to take this through the trivial patches tree?
Il 12/09/2013 10:52, Peter Lieven ha scritto:
On 18.07.2013 16:14, Paolo Bonzini wrote:
Il 18/07/2013 15:55, ronnie sahlberg ha scritto:
bdrv-write_zeroes will use writesame16 and set the unmap flag only if
BDRV_MAY_DISCARD == 1 and BDRV_O_UNMAP == 1 and lbprz == 1.
When you use WRITESAME16
On 12 September 2013 09:03, Claudio Fontana claudio.font...@huawei.com wrote:
On 10.09.2013 10:45, Peter Maydell wrote:
On 10 September 2013 09:27, Claudio Fontana claudio.font...@huawei.com
wrote:
On another side, I end up having to manually revert some parts
of these which you put as
On 12 September 2013 09:25, Claudio Fontana claudio.font...@huawei.com wrote:
On 02.09.2013 19:54, Richard Henderson wrote:
-case INDEX_op_bswap64_i64:
-ext = 1; /* fall through */
case INDEX_op_bswap32_i64:
+/* Despite the _i64, this is a 32-bit bswap. */
+
On 12.09.2013 10:58, Peter Maydell wrote:
On 12 September 2013 09:25, Claudio Fontana claudio.font...@huawei.com
wrote:
On 02.09.2013 19:54, Richard Henderson wrote:
-case INDEX_op_bswap64_i64:
-ext = 1; /* fall through */
case INDEX_op_bswap32_i64:
+/* Despite
Introduce QEMUTimerList-active_timers_lock to protect the linked list
of active timers. This allows qemu_timer_mod_ns() to be called from any
thread.
Note that vm_clock is not thread-safe and its use of
qemu_clock_has_timers() works fine today but is also not thread-safe.
The purpose of this
host_alarm_handler() is invoked from the signal processing thread
(currently the iothread). Previously we did processing in a real signal
handler with signalfd and therefore needed signal-safe timer code.
Today host_alarm_handler() just marks the alarm timer as expired/pending
and notifies the
From: Paolo Bonzini pbonz...@redhat.com
We can deduce the result from expire_time, by making it always -1 if
the timer is not in the active_timers list. We need to check against
negative times passed to timer_mod_ns; clamping them to zero is not
a problem because the only clock that has a zero
v4:
* Rebased retested for easy review and merge
* No code changes
v3:
* Squashed Paolo's fixes and added his patch to avoid locking in
timer_pending()
v2:
* Rebased onto qemu.git/master following the merge of Alex's AioContext timers
The purpose of these patches is to eventually allow
On 12.09.2013 10:55, Paolo Bonzini wrote:
Il 12/09/2013 10:52, Peter Lieven ha scritto:
On 18.07.2013 16:14, Paolo Bonzini wrote:
Il 18/07/2013 15:55, ronnie sahlberg ha scritto:
bdrv-write_zeroes will use writesame16 and set the unmap flag only if
BDRV_MAY_DISCARD == 1 and BDRV_O_UNMAP == 1
On Thu, Sep 12, 2013 at 09:36:43AM +0400, Michael Tokarev wrote:
12.09.2013 07:02, Fam Zheng wrote.
On Wed, 09/11 11:46, Richard Henderson wrote:
On 09/11/2013 08:48 AM, Daniel P. Berrange wrote:
We know the precise list of valid modules when building QEMU,
so IMHO, this should just
This series will remove the usage of symbols of mon-protocol-event in
qemu-img, qemu-nbd and qemu-io, in short remove the connetion for block
layer.
Background:
I am tring to decouple block layer code with other unnnessary components,
and in ./stub there many symbols that qemu-img linked as
block_int.h included monitor.h, so it knows the typedef.
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
---
block.c |2 +-
include/block/block_int.h |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/block.c b/block.c
index a325efc..2e2774d
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
---
include/monitor/monitor.h | 38 +-
include/qapi/qmp/qevent.h | 41 +
include/qapi/qmp/types.h |1 +
3 files changed, 43 insertions(+), 37 deletions(-)
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
---
block.c|2 +-
include/block/block_int.h |2 +-
include/monitor/monitor.h |2 +-
include/qapi/qmp/qevent.h |4 ++--
monitor.c | 12 ++--
stubs/mon-protocol-event.c |2 +-
Now block layer do not use this symbol now, so qemg-img, qemu-io
and qemu-nbd do not link with this file any more. The test program
tests/test-qdev-global-props still need it, so add this obj in
rule of test/Makefile, and keeps the c file now.
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
Block layer do not need it any more.
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
---
include/block/block_int.h |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/include/block/block_int.h b/include/block/block_int.h
index db2cb49..ec92f16 100644
---
block_int.h already included it.
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
---
block.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/block.c b/block.c
index 2e2774d..a532eaa 100644
--- a/block.c
+++ b/block.c
@@ -24,7 +24,6 @@
#include config-host.h
This structure can hold some call back functions, such as
event emit, error printf. By using call back, block layer
can be decoupled with other components.
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
---
block.c |7 +++
include/block/block.h | 11 +++
2
For code inside block layer, it is replaced with a call back
function. vl.c will tell block layer how to emit the event.
Signed-off-by: Wenchao Xia xiaw...@linux.vnet.ibm.com
---
block.c| 12 ++--
block/qcow2-refcount.c |4 +++-
blockjob.c | 10
Il 12/09/2013 11:15, Wenchao Xia ha scritto:
This series will remove the usage of symbols of mon-protocol-event in
qemu-img, qemu-nbd and qemu-io, in short remove the connetion for block
layer.
Background:
I am tring to decouple block layer code with other unnnessary components,
and in
Paolo Bonzini pbonz...@redhat.com writes:
Il 11/09/2013 20:26, Marcel Apfelbaum ha scritto:
Qemu is expected to quit if the same boot index value is used by two devices.
However, hot-plugging a device with a bootindex value already used should
fail with a friendly message rather than quitting
-Original Message-
From: Alex Williamson [mailto:alex.william...@redhat.com]
Sent: Wednesday, September 11, 2013 10:45 PM
To: Yoder Stuart-B08248
Cc: Wood Scott-B07421; Sethi Varun-B16395; Bhushan Bharat-R65777; 'Peter
Maydell'; 'Santosh Shukla'; 'Alexander Graf'; 'Antonios
Device trees created with create_device_tree() may not have any
entries in their reservemap, because the FDT API requires that the
reservemap is completed before any FDT nodes are added, and
create_device_tree() itself creates a node. However we were not
calling fdt_finish_reservemap(), which
From: John Rigby john.ri...@linaro.org
If no fdt is provided on command line and the new field
get_dtb in struct arm_boot_info is set then call it to
get a device tree blob.
Signed-off-by: John Rigby john.ri...@linaro.org
[PMM: minor tweaks and cleanup]
Signed-off-by: Peter Maydell
On Thu, 2013-09-12 at 11:43 +0200, Markus Armbruster wrote:
Paolo Bonzini pbonz...@redhat.com writes:
Il 11/09/2013 20:26, Marcel Apfelbaum ha scritto:
Qemu is expected to quit if the same boot index value is used by two
devices.
However, hot-plugging a device with a bootindex value
This patch series adds a 'virt' platform which uses the
kernel's mach-virt (fully device-tree driven) support
to create a simple minimalist platform intended for
use for KVM VM guests.
The major change here is that I've added a PL011 UART.
Sample command line:
qemu-system-arm -machine
Add 'virt' platform support corresponding to arch/arm/mach-virt
in the Linux kernel tree. This has no platform-specific code but
can use any device whose kernel driver is is able to work purely
from a device tree node. We use this to instantiate a minimal
set of devices: a GIC and some virtio-mmio
Dear Max,
Does it mean an IRQ to be edge-triggered?
No, it is a level-sensitive and active-high interrupt.
This is why i tried to use qemu_irq_raise() to trigger IRQ.
Thanks,
Simen
Hi Max,
Thanks for your patience and help.
I`ve tried to do what you said, but the problem
Marcel Apfelbaum marce...@redhat.com writes:
On Thu, 2013-09-12 at 11:43 +0200, Markus Armbruster wrote:
Paolo Bonzini pbonz...@redhat.com writes:
Il 11/09/2013 20:26, Marcel Apfelbaum ha scritto:
Qemu is expected to quit if the same boot index value is used by
two devices.
However,
On Thu, Sep 12, 2013 at 2:51 PM, Xie Xianshan xi...@cn.fujitsu.com wrote:
Dear Max,
Does it mean an IRQ to be edge-triggered?
No, it is a level-sensitive and active-high interrupt.
This is why i tried to use qemu_irq_raise() to trigger IRQ.
Ok, back to your original question:
I`m
Anthony,
The following changes since commit 2d1fe1873a984d1c2c89ffa3d12949cafc718551:
Merge remote-tracking branch 'pmaydell/tags/pull-target-arm-20130910' into
staging (2013-09-11 14:46:52 -0500)
are available in the git repository at:
git://github.com/bonzini/qemu.git scsi-next
for
From: Peter Maydell peter.mayd...@linaro.org
Use sextract32() for doing sign-extension rather than rolling
our own implementation.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/scsi/lsi53c895a.c | 16 +---
1 file
From: Peter Maydell peter.mayd...@linaro.org
Use deposit32() rather than handcoded shifts/masks to update the
scratch registers. This is cleaner and incidentally avoids a clang
sanitizer complaint (runtime error: left shift of 255 by 24 places
cannot be represented in type 'int').
Signed-off-by:
From: Alexey Kardashevskiy a...@ozlabs.ru
At the moment the guest kernel issues two types of task management
requests to the hypervisor - task about and lun reset. This adds
handling for these tasks. As spapr-vscsi starts calling scsi_req_cancel(),
free_request callback was implemented.
As
From: Peter Lieven p...@kamp.de
Signed-off-by: Peter Lieven p...@kamp.de
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
block/iscsi.c | 77 +++
1 file changed, 77 insertions(+)
diff --git a/block/iscsi.c b/block/iscsi.c
index
From: Markus Armbruster arm...@redhat.com
It's the abstract base of virtio-scsi-device and vhost-scsi.
Signed-off-by: Markus Armbruster arm...@redhat.com
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/scsi/virtio-scsi.c | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Markus Armbruster arm...@redhat.com
scsi_bus_legacy_add_drive() creates either a scsi-disk or a
scsi-generic device. It sets property serial to argument serial
unless null. Crashes with scsi-generic, because it doesn't have such
the property.
Only usb_msd_initfn_storage() passes non-null
From: Alexey Kardashevskiy a...@ozlabs.ru
The existing driver just dropped unsupported requests. This adds error
responses to those unhandled requests.
Signed-off-by: Alexey Kardashevskiy a...@ozlabs.ru
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/scsi/spapr_vscsi.c | 22
From: Peter Lieven p...@kamp.de
this patch adds a coroutine for .bdrv_co_block_status as well as
a generic framework that can be used to build coroutines in block/iscsi.
Signed-off-by: Peter Lieven p...@kamp.de
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
block/iscsi.c | 136
From: Peter Lieven p...@kamp.de
Replace .bdrv_aio_discard with .bdrv_co_discard so that discard
requests can be split in multiple parts, each for a small amount
of sectors.
This is useful because we expose a generic API with no limit
on the amount of sectors that can be unmapped in one request.
From: Nikunj A. Dadhania nik...@linux.vnet.ibm.com
This implements capabilities exchange between vscsi host and client. As
at the moment no capability is supported, put zero flags everywhere and
return.
Signed-off-by: Nikunj A Dadhania nik...@linux.vnet.ibm.com
Signed-off-by: Paolo Bonzini
The UUID is unique even across multiple hosts, thus it is
better than a VM name even if it is less user-friendly.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
block/iscsi.c | 23 ---
include/sysemu/sysemu.h | 2 ++
stubs/Makefile.objs | 1 +
Il 27/08/2013 05:20, Liu Ping Fan ha scritto:
Saw the Alex's patches has been merged, rebase mine onto his.
v3:
1. rename seqlock_read_check as seqlock_read_retry
2. Document timerlist were protected by BQL, and discard private lock
around qemu_event_wait(tl-ev).
v2:
1. fix
On Thu, 2013-09-12 at 13:04 +0200, Markus Armbruster wrote:
Marcel Apfelbaum marce...@redhat.com writes:
On Thu, 2013-09-12 at 11:43 +0200, Markus Armbruster wrote:
Paolo Bonzini pbonz...@redhat.com writes:
Il 11/09/2013 20:26, Marcel Apfelbaum ha scritto:
Qemu is expected to quit
Am 11.09.2013 um 18:58 hat Eric Blake geschrieben:
On 09/11/2013 10:47 AM, Paolo Bonzini wrote:
Single quotes for JSON are a QMP-ism, use real JSON in
qemu-img output.
Reported-by: Kevin Wolf kw...@redhat.com
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
qemu-img.c | 2 +-
Am 12.09.2013 um 10:37 hat Bharata B Rao geschrieben:
qemu-iotests number 007 doesn't do test image cleanup. This will affect
those protocols that expect a clean state before every test. Hence
ensure that test image is cleaned up in this test.
Signed-off-by: Bharata B Rao
On 09/11/2013 11:36 PM, Michael Tokarev wrote:
A solution which I proposed at the very beginning -- to export
a hashed init function from modules, and call it from the
main executable. Like, instead of, say, qemu_module_init(),
call qemu_module_init_0xdeadbeaf(), where 0xdeadbeaf is a
hash
Am 12.09.2013 um 11:31 hat Paolo Bonzini geschrieben:
Il 12/09/2013 11:15, Wenchao Xia ha scritto:
This series will remove the usage of symbols of mon-protocol-event in
qemu-img, qemu-nbd and qemu-io, in short remove the connetion for block
layer.
Background:
I am tring to decouple
Public bug reported:
virtio-serial appears to lose writes, but only when used on top of
virtio-mmio. The scenario is this:
/home/rjones/d/qemu/arm-softmmu/qemu-system-arm \
-global virtio-blk-device.scsi=off \
-nodefconfig \
-nodefaults \
-nographic \
-M vexpress-a15 \
Am 12.09.2013 08:24, schrieb Michael S. Tsirkin:
piix 1.7 is the default.
Signed-off-by: Michael S. Tsirkin m...@redhat.com
---
hw/i386/pc_piix.c | 19 +--
hw/i386/pc_q35.c | 17 -
2 files changed, 33 insertions(+), 3 deletions(-)
Looks like you forget to
[Note cc: Luiz]
Paolo Bonzini pbonz...@redhat.com writes:
Il 12/09/2013 11:15, Wenchao Xia ha scritto:
This series will remove the usage of symbols of mon-protocol-event in
qemu-img, qemu-nbd and qemu-io, in short remove the connetion for block
layer.
Background:
I am tring to decouple
On Thu, Sep 12, 2013 at 05:59:30AM -0600, Eric Blake wrote:
On 09/11/2013 11:36 PM, Michael Tokarev wrote:
A solution which I proposed at the very beginning -- to export
a hashed init function from modules, and call it from the
main executable. Like, instead of, say, qemu_module_init(),
In qmp_transaction, assert that the BdrvActionOps to be used is actually
valid.
This assertion failing is very improbable, however, it might happen, if
a new TransactionActionKind is introduced out of order and the
actions[] array is not updated.
Signed-off-by: Max Reitz mre...@redhat.com
---
** Description changed:
virtio-serial appears to lose writes, but only when used on top of
virtio-mmio. The scenario is this:
/home/rjones/d/qemu/arm-softmmu/qemu-system-arm \
-global virtio-blk-device.scsi=off \
-nodefconfig \
-nodefaults \
-nographic \
-M
On Thu, Sep 12, 2013 at 10:47:37AM +0200, Vincenzo Maffione wrote:
This patch implements the NetClientInfo.receive_iov method for the
e1000 device emulation. In this way a network backend that uses
qemu_sendv_packet() can deliver the fragmented packet without
requiring an additional copy in
On 09/12/2013 01:58 AM, Peter Maydell wrote:
On 12 September 2013 09:25, Claudio Fontana claudio.font...@huawei.com
wrote:
On 02.09.2013 19:54, Richard Henderson wrote:
-case INDEX_op_bswap64_i64:
-ext = 1; /* fall through */
case INDEX_op_bswap32_i64:
+/* Despite
On 09/12/2013 01:29 AM, Claudio Fontana wrote:
I see the problem related to the previous patch.
What about continuing to use int in the previous patch,
and replace it with bool in this one? The previous patch would only target
the way ext is set,
and this one would really contain all bool
1 - 100 of 197 matches
Mail list logo
