This patch breaks cpu list(-cpu ?).
--
SUN OF A BEACH
On Fri, Apr 16, 2010 at 03:08, Blue Swirl blauwir...@gmail.com wrote:
Since kvm.h can be used in files compiled once,
we can partially revert
b33612d03540fda7fa67485f1c20395beb7a2bf0.
Signed-off-by: Blue Swirl blauwir...@gmail.com
---
A userspace barrier API would be very useful instead of doing fsync when
only ordering is required. I'd like to follow that discussion too.
Stefan
On 4 May 2010 05:39, Rusty Russell ru...@rustcorp.com.au wrote:
On Fri, 19 Feb 2010 08:52:20 am Michael S. Tsirkin wrote:
I took a stub at
On writing errors, we just returned -1 even if some bytes were already
written out. Ensure we return the number of bytes written before we
return the error (on a subsequent call to qemu_chr_write()).
Signed-off-by: Amit Shah amit.s...@redhat.com
---
qemu-char.c |9 +++--
1 files changed,
Add a non-blocking write handler that can return with -EAGAIN to the
caller and also callback when the socket becomes writable.
Non-blocking writes are only enabled for sockets that are opened in
non-blocking mode and only for callers that have registered a callback
handler for resuming writes.
The initialisation for generic ports and console ports is similar.
Factor out the parts that are the same in a different function that can
be called from each of the initfns.
Signed-off-by: Amit Shah amit.s...@redhat.com
---
hw/virtio-console.c | 31 ++-
1 files
For char devices whose backing files are open in non-blocking mode,
non-blocking writes can now be made using qemu_chr_write_nb().
For non-blocking chardevs, we can return -EAGAIN to callers of
qemu_chr_write_nb(). When the backend is ready to accept more data,
we can let the caller know via a
If the char device we're connected to is overwhelmed with data and it
can't accept any more, signal to the virtio-serial-bus to stop sending
us more data till we tell otherwise.
If the current buffer being processed hasn't been completely written out
to the char device, we have to keep it around
Hello,
This series lets interested callers ask for an -EAGAIN return from the
chardev backends (only unix and tcp sockets as of now) to implement
their own flow control.
A new call, qemu_chr_write_nb() is added, that will fallback to
qemu_chr_write() if the backend file isn't non-blocking or if
On 05/04/10 09:17, Amit Shah wrote:
Add a non-blocking write handler that can return with -EAGAIN to the
caller and also callback when the socket becomes writable.
Non-blocking writes are only enabled for sockets that are opened in
non-blocking mode and only for callers that have registered a
On 05/04/10 09:56, Amit Shah wrote:
The logic will be pretty much the same for all filehandle-based backends
on unix. So maybe create some helper functions, so implementing
$backend_chr_write_unblocked can be done with just three lines of code?
Yes, that's the next step. Let's push this for
Sure. Submitted as v5.
Thanks,
Yoshi
2010/5/4 Anthony Liguori anth...@codemonkey.ws:
Hi Yoshi,
Could you rebase this series and resubmit? It conflicts with the latest
HEAD.
Regards,
Anthony Liguori
On 04/19/2010 10:40 PM, Yoshiaki Tamura wrote:
Replaces byte-based phys_ram_dirty
On 05/04/2010 07:38 AM, Rusty Russell wrote:
On Fri, 19 Feb 2010 08:52:20 am Michael S. Tsirkin wrote:
I took a stub at documenting CMD and FLUSH request types in virtio
block. Christoph, could you look over this please?
I note that the interface seems full of warts to me,
this might be a
Am 03.05.2010 23:26, schrieb Peter Lieven:
Hi Qemu/KVM Devel Team,
i'm using qemu-kvm 0.12.3 with latest Kernel 2.6.33.3.
As backend we use open-iSCSI with dm-multipath.
Multipath is configured to queue i/o if no path is available.
If we create a failure on all paths, qemu starts to
Anthony Liguori anth...@codemonkey.ws writes:
On 05/03/2010 04:29 AM, Markus Armbruster wrote:
[...]
Why am I proposing to remove pci_add from QMP before its replacement is
ready? I want it out sooner rather than later, because it isn't fully
functional (errors and drive_add are missing),
On Tue, May 04 2010, Rusty Russell wrote:
On Fri, 19 Feb 2010 08:52:20 am Michael S. Tsirkin wrote:
I took a stub at documenting CMD and FLUSH request types in virtio
block. Christoph, could you look over this please?
I note that the interface seems full of warts to me,
this might be
Modifies ram_save_block() and ram_save_remaining() to use
cpu_physical_memory_get_dirty_range() to check multiple dirty and non-dirty
pages at once.
Signed-off-by: Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp
Signed-off-by: OHMURA Kei ohmura@lab.ntt.co.jp
---
arch_init.c | 54
Replaces byte-based phys_ram_dirty bitmap with four (MASTER, VGA, CODE,
MIGRATION) bit-based phys_ram_dirty bitmap. On allocation, it sets all bits in
the bitmap. It uses ffs() to convert DIRTY_FLAG to DIRTY_IDX.
Modifies wrapper functions for byte-based phys_ram_dirty bitmap to bit-based
Am 03.05.2010 19:01, schrieb Anthony Liguori:
On 03/29/2010 06:03 AM, Kevin Wolf wrote:
Am 28.03.2010 19:07, schrieb Ryota Ozaki:
- use err(3) instead of errx(3) if errno is available
to report why failed
- let fail prior to daemon(3) if opening a nbd file
is likely to fail after
On Mon, May 03, 2010 at 11:59:55AM -0500, Anthony Liguori wrote:
On 05/03/2010 04:29 AM, Markus Armbruster wrote:
Why am I proposing to remove pci_add from QMP before its replacement is
ready? I want it out sooner rather than later, because it isn't fully
functional (errors and drive_add are
It checks the first row and puts dirty addr in the array. If the first row is
empty, it skips to the first non-dirty row or the end addr, and put the length
in the first entry of the array.
Signed-off-by: Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp
Signed-off-by: OHMURA Kei
On 04/27/2010 12:46 PM, Michael Tokarev wrote:
I've a debian bugreport that claims to have a fix
for apparently wrong keymap for usb keyboard. I
noticed this before with ps/2 keyboard too, the
sympthoms were that e.g windows keys were not
working in guests, but later on that has been
fixed.
On Tue, May 04, 2010 at 02:08:24PM +0930, Rusty Russell wrote:
On Fri, 19 Feb 2010 08:52:20 am Michael S. Tsirkin wrote:
I took a stub at documenting CMD and FLUSH request types in virtio
block. Christoph, could you look over this please?
I note that the interface seems full of warts to
Hi,
-static int unix_write(int fd, const uint8_t *buf, int len1)
+static int unix_write(int fd, const uint8_t *buf, int len1, bool nonblock)
{
int ret, len;
@@ -522,6 +537,9 @@ static int unix_write(int fd, const uint8_t *buf, int len1)
while (len 0) {
ret =
Modifies kvm_physical_sync_dirty_bitmap to use
cpu_physical_memory_set_dirty_range() to update the row of the bit-based
phys_ram_dirty bitmap at once.
Signed-off-by: OHMURA Kei ohmura@lab.ntt.co.jp
Signed-off-by: Yoshiaki Tamura tamura.yoshi...@lab.ntt.co.jp
---
kvm-all.c | 24
This series cleans up the simple read-only block drivers to use the
qemu block device API to access their backing devices, making the code
simpler and usable over nbd/curl. I've not touched dmg yet as it's even
more bitrot than usual and deserves it's own series.
Use pread instead of lseek + read in preparation of using the qemu
block API.
Signed-off-by: Christoph Hellwig h...@lst.de
Index: qemu-kevin/block/bochs.c
===
--- qemu-kevin.orig/block/bochs.c 2010-05-03 12:58:53.419012621
Use bdrv_pwrite to access the backing device instead of pread, and
convert the driver to implementing the bdrv_open method which gives
it an already opened BlockDriverState for the underlying device.
Signed-off-by: Christoph Hellwig h...@lst.de
Index: qemu-kevin/block/bochs.c
Use pread instead of lseek + read in preparation of using the qemu
block API.
Signed-off-by: Christoph Hellwig h...@lst.de
Index: qemu-kevin/block/cloop.c
===
--- qemu-kevin.orig/block/cloop.c 2010-05-03 13:01:09.035025542
Use bdrv_pwrite to access the backing device instead of pread, and
convert the driver to implementing the bdrv_open method which gives
it an already opened BlockDriverState for the underlying device.
Signed-off-by: Christoph Hellwig h...@lst.de
Index: qemu-kevin/block/cloop.c
Use pread instead of lseek + read in preparation of using the qemu
block API.
Signed-off-by: Christoph Hellwig h...@lst.de
Index: qemu-kevin/block/parallels.c
===
--- qemu-kevin.orig/block/parallels.c 2010-05-03 13:00:09.711253925
Use bdrv_pwrite to access the backing device instead of pread, and
convert the driver to implementing the bdrv_open method which gives
it an already opened BlockDriverState for the underlying device.
Signed-off-by: Christoph Hellwig h...@lst.de
Index: qemu-kevin/block/parallels.c
The initialisation for generic ports and console ports is similar.
Factor out the parts that are the same in a different function that can
be called from each of the initfns.
Signed-off-by: Amit Shah amit.s...@redhat.com
---
hw/virtio-console.c | 31 ++-
1 files
Hello,
This series lets interested callers ask for an -EAGAIN return from the
chardev backends (only unix and tcp sockets as of now) to implement
their own flow control.
A new call, qemu_chr_write_nb() is added, that will fallback to
qemu_chr_write() if the backend file isn't non-blocking or if
On writing errors, we just returned -1 even if some bytes were already
written out. Ensure we return the number of bytes written before we
return the error (on a subsequent call to qemu_chr_write()).
Signed-off-by: Amit Shah amit.s...@redhat.com
---
qemu-char.c |9 -
1 files changed,
For char devices whose backing files are open in non-blocking mode,
non-blocking writes can now be made using qemu_chr_write_nb().
For non-blocking chardevs, we can return -EAGAIN to callers of
qemu_chr_write_nb(). When the backend is ready to accept more data,
we can let the caller know via a
Instead of passing each handler in the qemu_add_handlers() function,
create a struct of handlers that can be passed to the function instead.
Signed-off-by: Amit Shah amit.s...@redhat.com
---
gdbstub.c|9 +++--
hw/debugcon.c|2 +-
hw/escc.c|9
If the char device we're connected to is overwhelmed with data and it
can't accept any more, signal to the virtio-serial-bus to stop sending
us more data till we tell otherwise.
If the current buffer being processed hasn't been completely written out
to the char device, we have to keep it around
The iov functions can be useful to other code as well.
Signed-off-by: Amit Shah amit.s...@redhat.com
CC: Christoph Hellwig h...@lst.de
---
hw/iov.c = iov.c |0
hw/iov.h = iov.h |0
2 files changed, 0 insertions(+), 0 deletions(-)
rename hw/iov.c = iov.c (100%)
rename hw/iov.h = iov.h
Broken in commit 2313086a.
Signed-off-by: Markus Armbruster arm...@redhat.com
---
qemu-monitor.hx |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/qemu-monitor.hx b/qemu-monitor.hx
index bf47ae0..220ed9c 100644
--- a/qemu-monitor.hx
+++ b/qemu-monitor.hx
@@ -611,6 +611,8
Commit f3546deb replaced host_net_redir by hostfwd_add,
hostfwd_remove, but neglected to update documentation.
Signed-off-by: Markus Armbruster arm...@redhat.com
---
qemu-monitor.hx | 13 ++---
1 files changed, 10 insertions(+), 3 deletions(-)
diff --git a/qemu-monitor.hx
Commit 15dfcd45 added acl_add and acl_reset, but fat-fingered their
documentation to read acl_allow and acl_remove.
Signed-off-by: Markus Armbruster arm...@redhat.com
---
qemu-monitor.hx |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/qemu-monitor.hx
Markus Armbruster (4):
doc: Fix host forwarding monitor command documentation
doc: Fix acl monitor command documentation
doc: Heading for monitor command cpu got lost, restore it
doc: Clean up monitor command function index
qemu-monitor.hx | 26 +-
1 files
2010/5/4 Christoph Hellwig h...@lst.de:
Use pread instead of lseek + read in preparation of using the qemu
block API.
IIRC there is no pread in MinGW.
@@ -531,8 +534,12 @@ static int unix_write(int fd, const uint8_t *buf, int len1)
while (len 0) {
ret = write(fd, buf, len);
if (ret 0) {
-if (errno != EINTR errno != EAGAIN)
+if (len1 - len) {
+return len1 - len;
+}
The dirty and non-dirty pages are checked one by one. When most of the memory
is not dirty, checking the dirty and non-dirty pages by multiple page size
should be much faster than checking them one by one. We introduced bit-based
phys_ram_dirty for VGA, CODE, MIGRATION, MASTER, and
On (Tue) May 04 2010 [13:24:58], Gerd Hoffmann wrote:
@@ -531,8 +534,12 @@ static int unix_write(int fd, const uint8_t *buf, int
len1)
while (len 0) {
ret = write(fd, buf, len);
if (ret 0) {
-if (errno != EINTR errno != EAGAIN)
+if (len1
On Tue, May 04, 2010 at 07:20:22PM +0800, Roy Tam wrote:
2010/5/4 Christoph Hellwig h...@lst.de:
Use pread instead of lseek + read in preparation of using the qemu
block API.
IIRC there is no pread in MinGW.
It gets replaced in the next patch anyway.
hi kevin,
i set a breakpint at bmdma_active_if. the first 2 breaks encountered
when the last path in the multipath
failed, but the assertion was not true.
when i kicked one path back in the breakpoint was reached again, this
time leading to an assert.
the stacktrace is from the point shortly
From RFB specs: The order of the encoding types given in this
message is a hint by the client as to its preference (the first
encoding specified being most preferred)
Signed-off-by: Corentin Chary corenti...@iksaif.net
---
vnc.c | 14 ++
1 files changed, 10 insertions(+), 4
On (Tue) May 04 2010 [09:43:04], Gerd Hoffmann wrote:
On 05/04/10 09:17, Amit Shah wrote:
Add a non-blocking write handler that can return with -EAGAIN to the
caller and also callback when the socket becomes writable.
Non-blocking writes are only enabled for sockets that are opened in
According to the LSI spec, the reset value of dcmd, dstat, and ctest2
were wrong, and sdid as well as ssid require zero initialization. There
are surely more discrepancies, this is just another increment.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
hw/lsi53c895a.c |8 +---
1
This series finally stabilizes system reset during ongoing SCSI I/O
here. The first patch is a repost, the others include missing reset
related bits that mostly concern the LSI controller. And the last patch
addresses a disk hotplugging issue: The LSI used to keep pointers to the
selected device,
We must not store references to selected devices as they may be
hot-removed. Instead, look up the device based on its tag right before
using it. If the device disappeared, throw an interrupt and disconnect.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
hw/lsi53c895a.c | 60
Declare the input message queue empty and initialize the related state
machine properly on controller reset. This fixes unrecoverable errors
when the controller was reset during ongoing requests.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
hw/lsi53c895a.c |2 ++
1 files changed, 2
Ensure that pending requests of an SCSI disk are purged on system reset
and also restore max_lba. The latter is no only present in the reset
handler as that one is called after init as well.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
hw/scsi-disk.c | 35
Once the I/O completion callback returned, aiocb will be released by the
controller. So we have to clear the reference not only in
scsi_write_complete, but also in scsi_read_complete. Otherwise we risk
inconsistencies when a reset hits us before the related request is
released.
Signed-off-by: Jan
Am 04.05.2010 13:38, schrieb Peter Lieven:
hi kevin,
i set a breakpint at bmdma_active_if. the first 2 breaks encountered
when the last path in the multipath
failed, but the assertion was not true.
when i kicked one path back in the breakpoint was reached again, this
time leading to an
Am 04.05.2010 12:43, schrieb Christoph Hellwig:
This series cleans up the simple read-only block drivers to use the
qemu block device API to access their backing devices, making the code
simpler and usable over nbd/curl. I've not touched dmg yet as it's even
more bitrot than usual and
From: Jan Kiszka jan.kis...@siemens.com
It is not safe to retrieve the KVM internal state of a given cpu
while its potentially modifying it.
Queue the request to run on cpu context, similarly to qemu-kvm.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
Index: qemu/kvm-all.c
run_on_cpu allows to execute work on a given CPUState context.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
Index: qemu/cpu-all.h
===
--- qemu.orig/cpu-all.h
+++ qemu/cpu-all.h
@@ -818,6 +818,7 @@ void
cpu_reset zeroes CPUState upto breakpoints member. Contents of
stop/stopped should not be zeroed on cpu_reset.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
Index: qemu/cpu-defs.h
===
--- qemu.orig/cpu-defs.h
+++
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
Index: qemu/cpu-all.h
===
--- qemu.orig/cpu-all.h
+++ qemu/cpu-all.h
@@ -818,6 +818,7 @@ void cpu_watchpoint_remove_all(CPUState
void cpu_single_step(CPUState *env, int enabled);
Process INIT/SIPI requests and enable -smp 1.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
Index: qemu/kvm-all.c
===
--- qemu.orig/kvm-all.c
+++ qemu/kvm-all.c
@@ -593,11 +593,6 @@ int kvm_init(int smp_cpus)
int ret;
On Mon, 2010-05-03 at 21:30 +0200, Kenneth Johansson wrote:
I'm trying to setup a debian root that I can chroot into for armel and
mips from an ubuntu 9.10 x86_64.
While I have it working for armel on a specific qemu the mips target is
more problematic.
first both fail for qemu newer
On 05/04/10 13:31, Amit Shah wrote:
On (Tue) May 04 2010 [13:24:58], Gerd Hoffmann wrote:
@@ -531,8 +534,12 @@ static int unix_write(int fd, const uint8_t *buf, int len1)
while (len 0) {
ret = write(fd, buf, len);
if (ret 0) {
-if (errno != EINTR
Commit 37c34d9d5d87ea9d51760310c8863b82cb8c055a introduced a regression when
using relative mouse mode with a client that understands the PointerTypeChange
pseudo-encoding.
Reported-by: Marcelo Tosatti mtosa...@redhat.com
Reported-by: Gerhard Wiesinger li...@wiesinger.com
Signed-off-by: Anthony
hi kevin,
you did it *g*
looks promising. applied this patched and was not able to reproduce yet :-)
secure way to reproduce was to shut down all multipath paths, then
initiate i/o
in the vm (e.g. start an application). of course, everything hangs at
this point.
after reenabling one path,
On 04/20/2010 11:56 AM, Alexander Graf wrote:
Virtio-Console can only process one character at a time. Using it on S390
gave me strage lags where I got the character I pressed before when
pressing one. So I typed in abc and only received a, then pressed d
but the guest received b and so on.
On 04/20/2010 01:48 PM, Bernhard M. Wiedemann wrote:
updated version of an old patch
http://xenon.stanford.edu/~eswierk/misc/qemu-linuxbios/qemu-piix-ram-size.patch
that together with
http://www.mail-archive.com/linuxb...@linuxbios.org/msg02390.html
(which is already in coreboot trunk) allows
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
Index: qemu/cpus.c
===
--- qemu.orig/cpus.c
+++ qemu/cpus.c
@@ -454,8 +454,7 @@ void qemu_cpu_kick(void *_env)
{
CPUState *env = _env;
qemu_cond_broadcast(env-halt_cond);
Zero cpu_single_env before leaving global lock protection, and
restore on return.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
Index: qemu/kvm-all.c
===
--- qemu.orig/kvm-all.c
+++ qemu/kvm-all.c
@@ -846,9 +846,11 @@ int
Store tcg loop exit request on a global variable, and transfer it to
per-CPUState exit_request after assignment of cpu_single_env.
This makes exit request signal from robust. Drop the timedlock hack.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
Index: qemu/cpu-exec.c
From: Jan Kiszka jan.kis...@siemens.com
Validate that KVM vcpu state is only read/written from cpu thread itself
or that cpu is stopped.
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
Index: qemu/target-i386/kvm.c
===
---
On 05/04/2010 08:56 AM, Luiz Capitulino wrote:
On Mon, 03 May 2010 08:16:35 -0500
Anthony Liguorianth...@codemonkey.ws wrote:
On 05/03/2010 08:06 AM, Markus Armbruster wrote:
Luiz Capitulinolcapitul...@redhat.com writes:
We need to expose errno in QMP, for three
Am 04.05.2010 15:42, schrieb Peter Lieven:
hi kevin,
you did it *g*
looks promising. applied this patched and was not able to reproduce yet :-)
secure way to reproduce was to shut down all multipath paths, then
initiate i/o
in the vm (e.g. start an application). of course, everything
On Mon, 03 May 2010 08:16:35 -0500
Anthony Liguori anth...@codemonkey.ws wrote:
On 05/03/2010 08:06 AM, Markus Armbruster wrote:
Luiz Capitulinolcapitul...@redhat.com writes:
We need to expose errno in QMP, for three reasons:
1. Some error handling functions print errno codes
KVM Forum topic ideas
- mgmt interface (qemud)
- working breakout sessions are welcome at the Forum
stable tree
- have a volunteer (thanks Justin)
- Anthony will write up proposal which is basically
- bug fixes actively proposed for stable tree
- stable maintainer collects and applies
-
On 05/04/2010 03:12 AM, Kevin Wolf wrote:
Am 03.05.2010 19:15, schrieb Anthony Liguori:
On 05/03/2010 07:31 AM, Corentin Chary wrote:
This will allow to implement new encodings (tight, zrle, ..)
in a cleaner way. This may hurt performances, because some
functions like
On Fri, Apr 30, 2010 at 11:43:43AM +0200, Martin Mohring wrote:
not sure how to handle the situation. But since the commit of the new
memory allocator for QEMU user mode, my test suites show it is broken.
The 0 sized write patch still isn't applied upstream. Is that the issue
(eg visible by
On 04/16/2010 12:11 PM, Bruce Rogers wrote:
The boot option is missing from the documentation for the -drive parameter.
If there is a better way to descibe it, I'm all ears.
Signed-off-by: Bruce Rogersbrog...@novell.com
diff --git a/qemu-options.hx b/qemu-options.hx
index f4b3bfe..f0f9a7c
Am 04.05.2010 um 15:44 schrieb Anthony Liguori anth...@codemonkey.ws:
On 04/20/2010 11:56 AM, Alexander Graf wrote:
Virtio-Console can only process one character at a time. Using it
on S390
gave me strage lags where I got the character I pressed before when
pressing one. So I typed in abc
On 05/04/2010 09:30 AM, Alexander Graf wrote:
Am 04.05.2010 um 15:44 schrieb Anthony Liguori anth...@codemonkey.ws:
On 04/20/2010 11:56 AM, Alexander Graf wrote:
Virtio-Console can only process one character at a time. Using it on
S390
gave me strage lags where I got the character I
Hi Peter,
On 03.05.2010 23:26, Peter Lieven wrote:
Hi Qemu/KVM Devel Team,
i'm using qemu-kvm 0.12.3 with latest Kernel 2.6.33.3.
As backend we use open-iSCSI with dm-multipath.
Multipath is configured to queue i/o if no path is available.
If we create a failure on all paths, qemu starts to
Hi,
I am maintaining the tightvnc package for openSUSE and was recently
confronted with an alleged vnc problem with QWMU that turned out to be
a shortcoming in QEMU's code for handling TCP server sockets, which is
used by the vnc and char modules.
The problem occurs when the address to
Am 04.05.2010 um 16:34 schrieb Anthony Liguori anth...@codemonkey.ws:
On 05/04/2010 09:30 AM, Alexander Graf wrote:
Am 04.05.2010 um 15:44 schrieb Anthony Liguori
anth...@codemonkey.ws:
On 04/20/2010 11:56 AM, Alexander Graf wrote:
Virtio-Console can only process one character at a
On 05/04/2010 08:49 AM, Reinhard Max wrote:
Hi,
I am maintaining the tightvnc package for openSUSE and was recently
confronted with an alleged vnc problem with QWMU that turned out to be
a shortcoming in QEMU's code for handling TCP server sockets, which is
used by the vnc and char modules.
On 05/04/2010 11:01 AM, Alexander Graf wrote:
Am 04.05.2010 um 16:34 schrieb Anthony Liguori anth...@codemonkey.ws:
On 05/04/2010 09:30 AM, Alexander Graf wrote:
Am 04.05.2010 um 15:44 schrieb Anthony Liguori anth...@codemonkey.ws:
On 04/20/2010 11:56 AM, Alexander Graf wrote:
Anthony Liguori wrote:
On 05/04/2010 11:01 AM, Alexander Graf wrote:
Am 04.05.2010 um 16:34 schrieb Anthony Liguori anth...@codemonkey.ws:
On 05/04/2010 09:30 AM, Alexander Graf wrote:
Am 04.05.2010 um 15:44 schrieb Anthony Liguori anth...@codemonkey.ws:
On 04/20/2010 11:56 AM, Alexander
Adds a parameter to the monitor's mouse_move command to specify the
hwheel delta.
Signed-off-by: Brad Jorsch ano...@users.sourceforge.net
---
monitor.c |8 ++--
qemu-monitor.hx |4 ++--
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/monitor.c b/monitor.c
index
Add a parameter for the hwheel delta to QEMUPutMouseEntry and
kbd_mouse_event, and adjust all users of those to match. At the moment,
all calls to kbd_mouse_event will pass 0 for the delta.
Signed-off-by: Brad Jorsch ano...@users.sourceforge.net
---
cocoa.m |6 +++---
console.h
SDL seems to report hwheel events as SDL_BUTTON_X1 and SDL_BUTTON_X2.
VNC I am guessing is similar, and online docs indicate that Cocoa
reports hwheel deltas in deltaX for NSScrollWheel.
Signed-off-by: Brad Jorsch ano...@users.sourceforge.net
---
cocoa.m |2 +-
sdl.c | 12 ++--
Adjust the USB report descriptors to indicate that the mouse and tablet
have horizontal wheels, and then report the delta when polled.
Signed-off-by: Brad Jorsch ano...@users.sourceforge.net
---
hw/usb-hid.c | 44
1 files changed, 36 insertions(+),
Have the emulated mouse report horizontal wheel events when in exps/2
mode.
Signed-off-by: Brad Jorsch ano...@users.sourceforge.net
---
hw/ps2.c | 56 +++-
1 files changed, 43 insertions(+), 13 deletions(-)
diff --git a/hw/ps2.c b/hw/ps2.c
The emulated mice should emulate a horizontal wheel when possible. This
patch series does that for the USB mouse and tablet and the ExPS/2
mouse. As far as I can tell the vmmouse protocol doesn't handle a
horizontal wheel, and I have no idea if emulating a wheel might make
sense for any of the
95 matches
Mail list logo
