Hello,
No news about this patch, could someone apply it?
Samuel
Samuel Thibault, le Wed 27 Feb 2008 14:45:55 +, a écrit :
> While using a virtual usbtablet, I noticed that I could not reach the
> extreme bottom and right pixels. That is because of the conversion from
> screen coordinates to
Anthony Liguori writes ("[Qemu-devel] [PATCH] Support redirect -curses
> over a character driver"): I love the -curses feature but I really
> wanted to use it over a telnet: character device. This patch
> enables this and changes the syntax of the -curses argument to take
> a character device.
Su
Hello,
The patch below fixes SDL mouse events processing:
- GetRelativeMouseState always returns the last position, so when the
polling loop gets several mouse events in one go, we would send
useless 'no move' events.
- So as to make sure we don't miss any mouse click / double click, we
shou
Hi,
On Wed, 5 Mar 2008, Samuel Thibault wrote:
> The patch below fixes SDL mouse events processing:
> - GetRelativeMouseState always returns the last position, so when the
> polling loop gets several mouse events in one go, we would send
> useless 'no move' events.
> - So as to make sure we d
Johannes Schindelin, le Wed 05 Mar 2008 14:09:10 +0100, a écrit :
> What is this good for? (I imagine that it would make sense to add a
> comment to document why this is here, for clueless people like me.)
>
> Maybe it is to initialise the state of the mouse buttons?
That's it.
> This means th
Here is a revamped patch:
This fixes SDL mouse events processing:
- GetRelativeMouseState() always returns the last position, so when the
polling loop gets several mouse events in one go, we would send
useless 'no move' events, let's avoid that.
- So as to make sure we don't miss any mouse cli
Hi,
On Wed, 5 Mar 2008, Samuel Thibault wrote:
> Here is a revamped patch:
Thanks, and thanks for the explanations, too.
Ciao,
Dscho
Ian Jackson wrote:
Anthony Liguori writes ("[Qemu-devel] [PATCH] Support redirect -curses
over a character driver"): I love the -curses feature but I really
wanted to use it over a telnet: character device. This patch
enables this and changes the syntax of the -curses argument to take
a char
Ian Jackson wrote:
Anthony Liguori writes ("[Qemu-devel] [PATCH] Support redirect -curses
over a character driver"): I love the -curses feature but I really
wanted to use it over a telnet: character device. This patch
enables this and changes the syntax of the -curses argument to take
a char
CVSROOT:/cvsroot/qemu
Module name:qemu
Changes by: Blue Swirl 08/03/05 17:59:49
Modified files:
linux-user : main.c
target-sparc : cpu.h op.c op_helper.c translate.c
Log message:
Convert Sparc64 trap state ops to TCG
CVSWeb URLs:
http://cvs.sava
CVSROOT:/cvsroot/qemu
Module name:qemu
Changes by: Blue Swirl 08/03/05 18:16:09
Modified files:
. : Makefile
Log message:
Properly bomb out on errors in Makefile shell fragments (Ian Jackson)
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/M
CVSROOT:/cvsroot/qemu
Module name:qemu
Changes by: Blue Swirl 08/03/05 18:27:45
Modified files:
. : vl.c
hw : boards.h sun4m.c
Log message:
Add more machine definitions
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/vl.
Avi Kivity wrote:
Ian Jackson wrote:
Anthony Liguori writes ("[Qemu-devel] [PATCH] Support redirect -curses
over a character driver"): I love the -curses feature but I really
wanted to use it over a telnet: character device. This patch
enables this and changes the syntax of the -curses argum
Anthony Liguori wrote:
I'm on the fence because while I like what I've posted, I'd like to
eventually tunnel the curses data over VNC in which case, having a
separate option makes sense. -curses would imply that the GUI would
be rendered with curses.
I'm lost. What does 'tunnel curses d
Avi Kivity wrote:
Anthony Liguori wrote:
I'm on the fence because while I like what I've posted, I'd like to
eventually tunnel the curses data over VNC in which case, having a
separate option makes sense. -curses would imply that the GUI would
be rendered with curses.
I'm lost. What do
Hey,
This patch series expose the actual thread id of each cpu via the qemu
monitor. It is done through "info cpus", which I though would be the
most natural command to do it. (If you disagree, please voice it)
Goal is to allow tools like libvirt to easily grab it and feed taskset
for thinks like
This patch exposes the thread id associated with each
cpu through the already well known info cpus interface.
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
qemu/monitor.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/qemu/monitor.c b/qemu/monitor.c
index 0874671.
This patch introduces a "thread_id" variable to CPUState.
It's duty will be to hold the process, or more generally, thread
id of the current executing cpu
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
qemu/cpu-defs.h |1 +
qemu/exec.c |5 +
2 files changed, 6 insertions(+),
At kvm ap creation, update CPUState with the actual thread id.
For us, they are actually different
Signed-off-by: Glauber Costa <[EMAIL PROTECTED]>
---
qemu/qemu-kvm.c |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/qemu/qemu-kvm.c b/qemu/qemu-kvm.c
index 051946e..
Oops!
Forgot the -n option in git.
Anyway, the series is small and straightforward, so I'm not reposting
it. If there is any doubt about the ordering, please tell me.
On Wed, Mar 5, 2008 at 5:01 PM, Glauber Costa <[EMAIL PROTECTED]> wrote:
> Hey,
>
> This patch series expose the actual thread i
I'm tracking down a image corruption issue and I'm curious if you can
answer the following:
1) Is there any difference between sending a "TERM" signal to the QEMU
process and typing "quit" at the monitor?
2) Will sending TERM corrupt the 'gcow2' image (in ways other than
normal guest OS dirt
David Barrett wrote:
I'm tracking down a image corruption issue and I'm curious if you can
answer the following:
1) Is there any difference between sending a "TERM" signal to the QEMU
process and typing "quit" at the monitor?
Yes. Since QEMU is single threaded, when you issue a quit, you kn
Ah thanks, that makes a lot of sense. Unfortunately, -snapshot doesn't
appear to work with -loadvm: any VM snapshots created outside of
snapshot mode are suppressed, and any VM snapshots created inside
snapshot mode disappear on close (even if you try to commit):
= I have a snapshot VM na
Fix microSPARC II SFSR mask.
diff -p -u -r1.96 translate.c
--- target-sparc/translate.c5 Mar 2008 17:59:48 - 1.96
+++ target-sparc/translate.c6 Mar 2008 02:15:30 -
@@ -4259,7 +4259,7 @@ static const sparc_def_t sparc_defs[] =
.mmu_bm = 0x4000,
.mmu_ctpr
On Wednesday 05 March 2008 01:54:08 Edgar E. Iglesias wrote:
> On Wed, Mar 05, 2008 at 12:51:36AM -0600, Rob Landley wrote:
> > On Tuesday 04 March 2008 05:22:12 you wrote:
> > > On Mon, Mar 03, 2008 at 06:28:22PM -0600, Rob Landley wrote:
> > > > Quick and dirty patch to teach qemu application emu
Glauber Costa wrote:
Hey,
This patch series expose the actual thread id of each cpu via the qemu
monitor. It is done through "info cpus", which I though would be the
most natural command to do it. (If you disagree, please voice it)
Goal is to allow tools like libvirt to easily grab it and feed
Anthony Liguori wrote:
David Barrett wrote:
I'm tracking down a image corruption issue and I'm curious if you can
answer the following:
1) Is there any difference between sending a "TERM" signal to the
QEMU process and typing "quit" at the monitor?
Yes. Since QEMU is single threaded, when
Anthony Liguori wrote:
Avi Kivity wrote:
Anthony Liguori wrote:
I'm on the fence because while I like what I've posted, I'd like to
eventually tunnel the curses data over VNC in which case, having a
separate option makes sense. -curses would imply that the GUI would
be rendered with curses
28 matches
Mail list logo
