On 11/26/2013 10:11 PM, Paolo Bonzini wrote:
Il 26/11/2013 14:53, Lei Li ha scritto:
1) ram_save_setup stage, it will send all the bytes in this stages
to destination, and send_pipefd by ram_control_before_iterate
at the end of it.
ram_save_setup runs doesn't send anything from guest
strtoul(l) might overflow, in which case it'll return '-1' and set
the appropriate error code. So update the calls to strtoul(l) when
parsing hex properties to avoid silent overflows.
Signed-off-by: Hannes Reinecke h...@suse.de
---
hw/core/qdev-properties.c | 20 ++--
1 file
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
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
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 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)
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
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 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
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
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 694fd42..76bb4b8 100644
--- a/block/stream.c
+++
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
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
On Wed, Nov 27, 2013 at 11:13:40AM +0100, Peter Lieven wrote:
Am 27.11.2013 11:07, schrieb Fam Zheng:
On 2013年11月27日 18:03, Peter Lieven wrote:
Am 27.11.2013 07:40, schrieb Fam Zheng:
On 2013年11月27日 14:01, Hu Tao wrote:
On Wed, Nov 27, 2013 at 11:01:23AM +0800, Fam Zheng wrote:
On
Il 28/11/2013 07:27, Zhanghaoyu (A) ha scritto:
Without synchronize_rcu you could have
VCPU writes to routing table
e = entry from IRQ routing table
kvm_irq_routing_update(kvm, new);
VCPU resumes execution
No, this would be exactly the same code that is running now:
mutex_lock(kvm-irq_lock);
old = kvm-irq_routing;
kvm_irq_routing_update(kvm, new);
mutex_unlock(kvm-irq_lock);
synchronize_rcu();
kfree(old);
On Thu, Nov 28, 2013 at 09:55:42AM +0100, Paolo Bonzini wrote:
Il 28/11/2013 07:27, Zhanghaoyu (A) ha scritto:
Without synchronize_rcu you could have
VCPU writes to routing table
e = entry from IRQ routing table
kvm_irq_routing_update(kvm,
On Thu, Nov 28, 2013 at 09:14:22AM +, Zhanghaoyu (A) wrote:
No, this would be exactly the same code that is running now:
mutex_lock(kvm-irq_lock);
old = kvm-irq_routing;
kvm_irq_routing_update(kvm, new);
Il 28/11/2013 10:19, Gleb Natapov ha scritto:
Not changing current behaviour is certainly safer, but I am still not 100%
convinced we have to ensure this.
Suppose guest does:
1: change msi interrupt by writing to pci register
2: read the pci register to flush the write
3: zero idt
I
On Thu, Nov 28, 2013 at 10:29:36AM +0100, Paolo Bonzini wrote:
Il 28/11/2013 10:19, Gleb Natapov ha scritto:
Not changing current behaviour is certainly safer, but I am still not 100%
convinced we have to ensure this.
Suppose guest does:
1: change msi interrupt by writing to pci
On 11/28/2013 11:19 AM, Gleb Natapov wrote:
On Thu, Nov 28, 2013 at 09:55:42AM +0100, Paolo Bonzini wrote:
Il 28/11/2013 07:27, Zhanghaoyu (A) ha scritto:
Without synchronize_rcu you could have
VCPU writes to routing table
e = entry from IRQ routing
Il 28/11/2013 10:49, Avi Kivity ha scritto:
Linux is safe, it does interrupt migration from within the interrupt
handler. If you do that before the device-specific EOI, you won't get
another interrupt until programming the MSI is complete.
Is virtio safe? IIRC it can post multiple
Hello,
On 2013-11-26 15:04, Sebastian Huber wrote:
The LEON3 processor has support for the CASA instruction which is
normally only available for SPARC V9 processors. Binutils 2.24
and GCC 4.9 will support this instruction for LEON3. GCC uses it to
generate C11 atomic operations.
---
On 28.11.2013 09:48, Hu Tao wrote:
On Wed, Nov 27, 2013 at 11:13:40AM +0100, Peter Lieven wrote:
Am 27.11.2013 11:07, schrieb Fam Zheng:
On 2013年11月27日 18:03, Peter Lieven wrote:
Am 27.11.2013 07:40, schrieb Fam Zheng:
On 2013年11月27日 14:01, Hu Tao wrote:
On Wed, Nov 27, 2013 at 11:01:23AM
On Thu, Nov 28, 2013 at 11:49:00AM +0200, Avi Kivity wrote:
On 11/28/2013 11:19 AM, Gleb Natapov wrote:
On Thu, Nov 28, 2013 at 09:55:42AM +0100, Paolo Bonzini wrote:
Il 28/11/2013 07:27, Zhanghaoyu (A) ha scritto:
Without synchronize_rcu you could have
VCPU writes to routing table
On 11/28/2013 12:11 PM, Gleb Natapov wrote:
On Thu, Nov 28, 2013 at 11:49:00AM +0200, Avi Kivity wrote:
On 11/28/2013 11:19 AM, Gleb Natapov wrote:
On Thu, Nov 28, 2013 at 09:55:42AM +0100, Paolo Bonzini wrote:
Il 28/11/2013 07:27, Zhanghaoyu (A) ha scritto:
Without synchronize_rcu you could
On 11/28/2013 11:53 AM, Paolo Bonzini wrote:
Il 28/11/2013 10:49, Avi Kivity ha scritto:
Linux is safe, it does interrupt migration from within the interrupt
handler. If you do that before the device-specific EOI, you won't get
another interrupt until programming the MSI is complete.
Is
On Mon, Nov 25, 2013 at 06:43:13PM +0100, Paolo Bonzini wrote:
v2: condition enablement of new mapping to new machine types (Paolo)
v3: fix changelog
v4: rebase
v5: ensure alignment of piecetwo on 2MB GPA (Igor)
do not register zero-sized piece-one(Igor)
v6: fix memory leak
The LEON3 processor has support for the CASA instruction which is
normally only available for SPARC V9 processors. Binutils 2.24
and GCC 4.9 will support this instruction for LEON3. GCC uses it to
generate C11 atomic operations.
The CAS synthetic instruction uses an ASI of 0x80. If
Am 27.11.2013 um 21:05 hat Max Reitz geschrieben:
Leaving the backing file open although it is not needed anymore can
cause problems if it is opened through a block driver which allows
exclusive access only and if the create function of the block driver
used for the top image (the one being
Il 28/11/2013 11:16, Avi Kivity ha scritto:
The QRCU I linked would work great latency-wise (it has roughly the same
latency of an rwsem but readers are lock-free). However, the locked
operations in the read path would hurt because of cache misses, so it's
not good either.
I guess srcu
On 11/28/2013 12:40 PM, Paolo Bonzini wrote:
Il 28/11/2013 11:16, Avi Kivity ha scritto:
The QRCU I linked would work great latency-wise (it has roughly the same
latency of an rwsem but readers are lock-free). However, the locked
operations in the read path would hurt because of cache misses,
VERIFY emulation was completely botched (and remained botched through
all the refactorings). The command must be emulated both in check-medium
mode (BYTCHK=00, which we implement by doing nothing) and in check-bytes
mode (which we do not implement yet). Unlike WRITE AND VERIFY (which we
treat
Windows executes the VERIFY command if the user forces a disk check
at the next startup. QEMU crashes on it; fix it by doing exactly
nothing to VERIFY a bunch of sectors.
Paolo Bonzini (2):
scsi-bus: fix transfer length and direction for VERIFY command
scsi-disk: fix VERIFY emulation
The amount of bytes to transfer depends on the BYTCHK field.
If any data is transferred, it is sent to the device.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/scsi/scsi-bus.c | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git
If you open an image temporarily just because you want to check its size
or get it flushed, there's no real reason to open the whole backing file
chain.
Signed-off-by: Kevin Wolf kw...@redhat.com
---
block.c | 3 ++-
block/qcow2.c | 3 ++-
block/vmdk.c | 2 +-
3 files changed, 5
On Thu, Nov 28, 2013 at 12:12:55PM +0200, Avi Kivity wrote:
On 11/28/2013 12:11 PM, Gleb Natapov wrote:
On Thu, Nov 28, 2013 at 11:49:00AM +0200, Avi Kivity wrote:
On 11/28/2013 11:19 AM, Gleb Natapov wrote:
On Thu, Nov 28, 2013 at 09:55:42AM +0100, Paolo Bonzini wrote:
Il 28/11/2013 07:27,
On Thu, Nov 28, 2013 at 11:40:06AM +0100, Paolo Bonzini wrote:
Il 28/11/2013 11:16, Avi Kivity ha scritto:
The QRCU I linked would work great latency-wise (it has roughly the same
latency of an rwsem but readers are lock-free). However, the locked
operations in the read path would hurt
Il 28/11/2013 12:09, Gleb Natapov ha scritto:
- if there are no callbacks, but there are readers, synchronize_srcu
busy-loops for some time checking if the readers complete. After a
while (20 us for synchronize_srcu, 120 us for
synchronize_srcu_expedited) it gives up and starts using a
On 11/28/2013 01:10 PM, Paolo Bonzini wrote:
Il 28/11/2013 12:09, Gleb Natapov ha scritto:
- if there are no callbacks, but there are readers, synchronize_srcu
busy-loops for some time checking if the readers complete. After a
while (20 us for synchronize_srcu, 120 us for
On 11/28/2013 01:02 PM, Gleb Natapov wrote:
On Thu, Nov 28, 2013 at 12:12:55PM +0200, Avi Kivity wrote:
On 11/28/2013 12:11 PM, Gleb Natapov wrote:
On Thu, Nov 28, 2013 at 11:49:00AM +0200, Avi Kivity wrote:
On 11/28/2013 11:19 AM, Gleb Natapov wrote:
On Thu, Nov 28, 2013 at 09:55:42AM
On Thu, Nov 28, 2013 at 01:18:54PM +0200, Avi Kivity wrote:
On 11/28/2013 01:02 PM, Gleb Natapov wrote:
On Thu, Nov 28, 2013 at 12:12:55PM +0200, Avi Kivity wrote:
On 11/28/2013 12:11 PM, Gleb Natapov wrote:
On Thu, Nov 28, 2013 at 11:49:00AM +0200, Avi Kivity wrote:
On 11/28/2013 11:19 AM,
On Thu, Nov 28, 2013 at 12:10:40PM +0100, Paolo Bonzini wrote:
Il 28/11/2013 12:09, Gleb Natapov ha scritto:
- if there are no callbacks, but there are readers, synchronize_srcu
busy-loops for some time checking if the readers complete. After a
while (20 us for synchronize_srcu, 120 us
On Thu, Nov 28, 2013 at 01:22:45PM +0200, Gleb Natapov wrote:
On Thu, Nov 28, 2013 at 01:18:54PM +0200, Avi Kivity wrote:
On 11/28/2013 01:02 PM, Gleb Natapov wrote:
On Thu, Nov 28, 2013 at 12:12:55PM +0200, Avi Kivity wrote:
On 11/28/2013 12:11 PM, Gleb Natapov wrote:
On Thu, Nov 28,
On 11/28/2013 01:22 PM, Gleb Natapov wrote:
On Thu, Nov 28, 2013 at 01:18:54PM +0200, Avi Kivity wrote:
On 11/28/2013 01:02 PM, Gleb Natapov wrote:
On Thu, Nov 28, 2013 at 12:12:55PM +0200, Avi Kivity wrote:
On 11/28/2013 12:11 PM, Gleb Natapov wrote:
On Thu, Nov 28, 2013 at 11:49:00AM
Il 28/11/2013 12:23, Gleb Natapov ha scritto:
Unless what ? :) Unless reader is scheduled out?
Yes. Or unless my brain is scheduled out in the middle of a sentence.
So we will have to disable preemption in a reader to prevent big latencies for
a writer, no?
I don't think that's
On Thu, Nov 28, 2013 at 01:33:48PM +0200, Michael S. Tsirkin wrote:
On Thu, Nov 28, 2013 at 01:22:45PM +0200, Gleb Natapov wrote:
On Thu, Nov 28, 2013 at 01:18:54PM +0200, Avi Kivity wrote:
On 11/28/2013 01:02 PM, Gleb Natapov wrote:
On Thu, Nov 28, 2013 at 12:12:55PM +0200, Avi Kivity
Am 27.11.2013 um 03:01 hat Fam Zheng geschrieben:
On 2013年11月20日 10:25, Fam Zheng wrote:
The second patch is too large as a mail, you can pull from:
https://github.com/famz/qemu.git 035-filter-qemu-io
v2: Rebase to current master.
[01] Add Reviewed-by for Eric.
[02] Update
On Wed, 27 Nov 2013 21:58:18 -0700
Eric Blake ebl...@redhat.com wrote:
On 11/27/2013 06:24 PM, Igor Mammedov wrote:
in case if caller setting property doesn't care about error and
passes in NULL as errp argument but error occurs in property setter,
it is silently discarded leaving object
On Thu, 28 Nov 2013 15:10:50 +1000
Peter Crosthwaite peter.crosthwa...@xilinx.com wrote:
Hi,
On Thu, Nov 28, 2013 at 11:24 AM, Igor Mammedov imamm...@redhat.com wrote:
in case if caller setting property doesn't care about error and
passes in NULL as errp argument but error occurs in
Enable KVM if the host and target CPU are both aarch64. Note
that host aarch64 + target arm is not valid for KVM acceleration:
the 64 bit kernel does not support the ioctl interface for
32 bit CPUs. 32 bit VMs on 64 bit hosts need to be created
using the 64 bit ioctl interface; when QEMU supports
This patchset adds support for basic AArch64 KVM VM control. It sits
on top of the mach-virt + cpu-host patchset I sent out last week.
The core of these patches is the work done by Mian M. Hamayun; I've
just taken that, refactored it a bit to sit on top of the
mach-virt+cpu-host patchset instead
For AArch64 we will obviously require a different set of
primary and secondary boot loader code fragments. However currently
we hardcode the offsets into the loader code where we must write
the entrypoint and other data into arm_load_kernel(). This makes it
hard to substitute a different loader
Split ARM KVM support code which is 32 bit specific out into its
own file, which we only compile on 32 bit hosts. This will give
us a place to add the 64 bit support code without adding lots of
ifdefs to kvm.c.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
target-arm/Makefile.objs |
The env-pstate field is a little odd since it doesn't strictly
speaking represent an architectural register. However it's convenient
for QEMU to use it to hold the various PSTATE architectural bits
in the same format the architecture specifies for SPSR registers
(since this is the same format the
From: Mian M. Hamayun m.hama...@virtualopensystems.com
Add the bare minimum set of functions needed for control of an
AArch64 KVM vcpu:
* CPU initialization
* minimal get/put register functions which only handle the
basic state of the CPU
Signed-off-by: Mian M. Hamayun
Il 28/11/2013 14:23, Igor Mammedov ha scritto:
object_property_set(Foo, bar, baz, abort_on_err);
that is just another way to put burden on caller, instead of doing it
in one place.
It's also much more self-documenting.
The problem is that there is one very good case where you want the
Am 28.11.2013 14:48, schrieb Igor Mammedov:
On Thu, 28 Nov 2013 14:42:38 +0100
Andreas Färber afaer...@suse.de wrote:
I will be more than happy to review and apply your patch (or contribute
further ones) going through (mis)uses of error_is_set().
I've sent such one for target-i386/cpu.c see
This series separates the QEMUFile and VMState code from savevm.c, and adds a
few unit tests to the VMState code.
Eduardo Habkost (9):
qemu-file: Make a few functions non-static
migration: Move QEMU_VM_* defines to migration/migration.h
savevm: Convert all tabs to spaces
savevm.c: Coding
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
I am submitting this as a separate patch because I don't know if this
will be the preferred way of breaking that line.
---
savevm.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/savevm.c b/savevm.c
index
The VMState code will be moved to vmstate.c and it uses some of the
QEMU_VM_* constants, so move it to a header.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
include/migration/migration.h | 11 +++
savevm.c | 11 ---
2 files changed, 11
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
savevm.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/savevm.c b/savevm.c
index 46643f1..3cdd5f2 100644
--- a/savevm.c
+++ b/savevm.c
@@ -53,7 +53,7 @@
#define ARP_OP_REQUEST_REV 0x3
static int
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
Makefile.objs | 1 +
qemu-file.c | 826 ++
savevm.c | 820 -
3 files changed, 827 insertions(+), 820 deletions(-)
create
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
savevm.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/savevm.c b/savevm.c
index 8eeb5ef..a2c2173 100644
--- a/savevm.c
+++ b/savevm.c
@@ -166,7 +166,9 @@ static QEMUFile *qemu_fopen_bdrv(BlockDriverState *bs,
This will allow unit tests to be written for VMState code without
pulling dependencies from the savevm code.
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
Makefile.objs | 1 +
savevm.c | 645 -
vmstate.c | 650
* Basic load/save tests
* Tests for loading older versions
* Tests for .field_exists() handling
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
tests/.gitignore | 1 +
tests/Makefile | 4 +
tests/test-vmstate.c | 357 +++
3
Am 28.11.2013 09:39, schrieb Hannes Reinecke:
strtoul(l) might overflow, in which case it'll return '-1' and set
the appropriate error code. So update the calls to strtoul(l) when
parsing hex properties to avoid silent overflows.
Signed-off-by: Hannes Reinecke h...@suse.de
---
Am 28.11.2013 15:01, schrieb Eduardo Habkost:
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
savevm.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/savevm.c b/savevm.c
index 8eeb5ef..a2c2173 100644
--- a/savevm.c
+++ b/savevm.c
@@ -166,7 +166,9 @@
On Thu, Nov 28, 2013 at 03:13:39PM +0100, Andreas Färber wrote:
Am 28.11.2013 15:01, schrieb Eduardo Habkost:
Signed-off-by: Eduardo Habkost ehabk...@redhat.com
---
savevm.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/savevm.c b/savevm.c
index
On Thu, 28 Nov 2013 14:19:48 +0800
Wenchao Xia xiaw...@linux.vnet.ibm.com wrote:
于 2013/11/26 0:47, Luiz Capitulino 写道:
On Wed, 13 Nov 2013 06:25:00 +0800
Wenchao Xia xiaw...@linux.vnet.ibm.com wrote:
This series is respined from RFC series at:
Am 28.11.2013 07:29, schrieb Antony Pavlov:
Signed-off-by: Antony Pavlov antonynpav...@gmail.com
Reviewed-by: Richard Henderson r...@twiddle.net
Are the int - long changes caused by the BIT() macro usage? Otherwise I
would've recommended to put that in a follow-up patch.
But either way,
Add functions to query QemuConsole properties.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
include/ui/console.h | 3 +++
ui/console.c | 24
2 files changed, 27 insertions(+)
diff --git a/include/ui/console.h b/include/ui/console.h
index 98edf41..09138e5
Define input event types, using qapi. So we get nicely autogenerated
types for our input events. And when it comes to qmp support some day
things will be alot easier.
Types are modeled after the linux input layer. There are separate
event types for each value. There is a sync to indicate the
Hi,
This patch series is the first draft of a input layer rewrite.
New core code is largely in place. There is some windup for
the legacy functions, to keep things working while switching
over users one by one.
Some ui code is converted to make clear how the new input layer
should be used.
A bunch of helper functions to manage keyboard events,
to make life simpler for the ui code when submitting
keyboard events.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
include/ui/input.h | 3 +++
ui/input.c | 19 +++
2 files changed, 22 insertions(+)
diff --git
legacy mouse event handlers are registered in the new core,
so they receive events submitted to the new input core.
legacy kbd_mouse_event() continues to use the old code paths.
So new-core event handlers wouldn't see events submitted via
kbd_mouse_event.
This leads to the constrain that we we
Rename ui/input.c to ui/input-legacy.c.
We are going to replace it step by step.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
ui/Makefile.objs | 2 +-
ui/{input.c = input-legacy.c} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
rename ui/{input.c = input-legacy.c}
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
ui/gtk.c | 58 +++---
1 file changed, 19 insertions(+), 39 deletions(-)
diff --git a/ui/gtk.c b/ui/gtk.c
index 3a97b36..3c37d2e 100644
--- a/ui/gtk.c
+++ b/ui/gtk.c
@@ -197,7 +197,7 @@ static
Likewise a bunch of helper functions to manage mouse button
and movement events, again to make life easier for the ui code.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
include/ui/input.h | 14 +++
ui/input.c | 71 ++
2
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
ui/input-legacy.c | 10 ++
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/ui/input-legacy.c b/ui/input-legacy.c
index 0163a46..d7dd880 100644
--- a/ui/input-legacy.c
+++ b/ui/input-legacy.c
@@ -260,10 +260,7 @@ static void
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
ui/gtk.c | 19 ---
1 file changed, 4 insertions(+), 15 deletions(-)
diff --git a/ui/gtk.c b/ui/gtk.c
index b5f4f0b..3a97b36 100644
--- a/ui/gtk.c
+++ b/ui/gtk.c
@@ -54,6 +54,7 @@
#include math.h
#include ui/console.h
On Thu, 28 Nov 2013 15:16:08 +0800
Wenchao Xia xiaw...@linux.vnet.ibm.com wrote:
于 2013/11/28 8:48, Luiz Capitulino 写道:
On Wed, 13 Nov 2013 09:44:52 +0800
Wenchao Xia xiaw...@linux.vnet.ibm.com wrote:
Nested structure is not supported now, so following define is not valid:
{ 'event':
FIXME: pause key not handled yet.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
ui/sdl.c | 23 ++-
1 file changed, 10 insertions(+), 13 deletions(-)
diff --git a/ui/sdl.c b/ui/sdl.c
index 9d8583c..1b1224a 100644
--- a/ui/sdl.c
+++ b/ui/sdl.c
@@ -30,6 +30,7 @@
Transform absolute mouse events according to graphic_rotate.
Legacy input code does it for both absolute and relative events,
but the logic is broken for relative coordinates, so this is
most likely not used anyway.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
ui/input.c | 33
Same as kbd_mouse_is_absolute(), but using new input core.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
include/ui/input.h | 1 +
ui/input.c | 8
2 files changed, 9 insertions(+)
diff --git a/include/ui/input.h b/include/ui/input.h
index 0d79342..43b9afc 100644
---
On Thu, Nov 28, 2013 at 7:56 PM, Kevin Wolf kw...@redhat.com wrote:
Am 27.11.2013 um 03:01 hat Fam Zheng geschrieben:
On 2013年11月20日 10:25, Fam Zheng wrote:
The second patch is too large as a mail, you can pull from:
https://github.com/famz/qemu.git 035-filter-qemu-io
v2: Rebase to
On Mo, 2013-11-25 at 13:08 +0100, arm...@redhat.com wrote:
From: Markus Armbruster arm...@redhat.com
Commit b5613fd neglected to drop the trace events along with the code.
Added to usb patch queue.
thanks,
Gerd
On Thu, Nov 28, 2013 at 7:56 PM, Kevin Wolf kw...@redhat.com wrote:
Am 27.11.2013 um 03:01 hat Fam Zheng geschrieben:
On 2013年11月20日 10:25, Fam Zheng wrote:
The second patch is too large as a mail, you can pull from:
https://github.com/famz/qemu.git 035-filter-qemu-io
v2: Rebase to
On Wed, 9 Oct 2013 17:43:08 +0800
Chen Fan chen.fan.f...@cn.fujitsu.com wrote:
Via implementing ACPI standard methods _EJ0 in bios, after Guest OS hot remove
one vCPU, it is able to send a signal to QEMU, then QEMU could notify
the assigned vCPU of exiting. meanwhile, and intruduce the QOM
Register and unregister handlers.
Event dispatcher code.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
include/ui/input.h | 32 +
ui/Makefile.objs | 2 +-
ui/input.c | 83 ++
3 files changed, 116
On Wed, 9 Oct 2013 17:43:18 +0800
Chen Fan chen.fan.f...@cn.fujitsu.com wrote:
After ACPI get a signal to eject a vCPU, then it will notify
the vCPU thread to exit in KVM, and the vCPU must be removed from CPU list，
before the vCPU really removed, there will release the all related vCPU
legacy kbd event handlers are registered in the new core,
so they receive events from the new input core code.
keycode - scancode translation needed here.
legacy kbd_put_keycode() sends events to the new core.
scancode - keycode translation needed here.
So with this patch the new input core is
Am 28.11.2013 um 15:34 hat Fam Zheng geschrieben:
On Thu, Nov 28, 2013 at 7:56 PM, Kevin Wolf kw...@redhat.com wrote:
Am 27.11.2013 um 03:01 hat Fam Zheng geschrieben:
On 2013年11月20日 10:25, Fam Zheng wrote:
The second patch is too large as a mail, you can pull from:
On Do, 2013-11-21 at 17:20 +0100, Hans de Goede wrote:
Hi Gerd,
Here is a new version of the 3 patches to add streams support to
usb-host-libusb, with the error when building with an older libusbx fixed.
Added to usb patch queue.
thanks,
Gerd
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
ui/sdl.c | 65 +---
1 file changed, 34 insertions(+), 31 deletions(-)
diff --git a/ui/sdl.c b/ui/sdl.c
index 1b1224a..13076e3 100644
--- a/ui/sdl.c
+++ b/ui/sdl.c
@@ -357,7 +357,7 @@
Am 12.11.2013 um 23:25 hat Wenchao Xia geschrieben:
This series is respined from RFC series at:
http://lists.nongnu.org/archive/html/qemu-devel/2013-11/msg00363.html
Patch 1-6 add support for enum as discriminator.
Patch 7 improve enum name generation, now AIOContext-AIO_CONTEXT, X86CPU-
On 19 November 2013 06:16, Christoffer Dall christoffer.d...@linaro.org wrote:
This patch series adds generic support for issuing device control
related ioctls and supports creating the ARM KVM-accelerated VGIC using
the device control API while maintaining backwards compatibility for
older
Igor Mammedov imamm...@redhat.com writes:
On Thu, 28 Nov 2013 15:10:50 +1000
Peter Crosthwaite peter.crosthwa...@xilinx.com wrote:
Hi,
On Thu, Nov 28, 2013 at 11:24 AM, Igor Mammedov imamm...@redhat.com wrote:
in case if caller setting property doesn't care about error and
passes in
Paolo Bonzini pbonz...@redhat.com writes:
Il 28/11/2013 14:23, Igor Mammedov ha scritto:
object_property_set(Foo, bar, baz, abort_on_err);
that is just another way to put burden on caller, instead of doing it
in one place.
It's also much more self-documenting.
The problem is that there
On Wed, Nov 27 2013, Stefan Hajnoczi wrote:
I finally got around to reading the Linux multiqueue block layer paper
and wanted to share some thoughts about how it relates to QEMU and
dataplane/QContext:
http://kernel.dk/blk-mq.pdf
I think Jens has virtio-blk multiqueue patches. So let's
1 - 100 of 253 matches
Mail list logo
