[Qemu-devel] [PATCH] Fix drive names in windows

Hi, Attached patch fixes drive names for windows. Using $ in formatting strings seems to be Unix specific. Regards, Edu --- vl.c 17 Dec 2007 04:42:28 - 1.388 +++ vl.c 21 Dec 2007 00:08:50 - @@ -5091,8 +5091,13 @@ if (type == IF_IDE || type == IF_SCSI) mediastr = (media ==

Re: [Qemu-devel] Re: Detecting an assembly instruction in QEMU

Hi, Your should create a new helper function in \target-i386\helper.c to perform whatever you want QEMU to do when movl %eax,%eax is found. To invoke that function create a new opcode in \target-i386\op.c. That opcode should only call your helper function. Finally, modify \target-i386\translate

[Qemu-devel] Feature proposal: USB devices over TCP

on port for incoming connections. A sample USB mouse in python is also provided that moves the cursor in circles. Would such a feature be of any interest for QEMU? Regards, Eduardo Felipe usb_over_tcp.diff Description: Binary data # Copyright (c) 2007 Eduardo Felipe # # Permission is hereby

Re: [Qemu-devel] Feature proposal: USB devices over TCP

It would be cool indeed. Maybe some wrapper around libusb could do the trick for host OSes where no USB/IP server is available. I'll have a look at USB/IP. Regards, Eduardo Felipe

Re: [Qemu-devel] Re: Detecting an assembly instruction in QEMU

Hi Atif, In target-i386/translate.c, there are many variants of mov i.e. case 0x89: /* mov Gv, Ev */ case 0xc7: /* mov Ev, Iv */ case 0x8b: /* mov Ev, Gv */ case 0x8e: /* mov seg, Gv */ That's true. I forgot the fact that mov %eax,%eax can be both: 0x89 0xC0 0x8B 0xC0 It's up to the com

Re: QEMU Automated Testing (was [Qemu-devel] qemu Makefile.target vl.h hw/acpi.c hw/adlib.c ...)

But that required some macro interface "click at x,y, wait some seconds, press 'k' key", that is not currently under QEMU. It does exist... it's called VNC server. Maybe you can have a look at: http://www.sodan.org/~penny/vncrec/ or http://suif.stanf

Re: [Qemu-devel] Re: Detecting an assembly instruction in QEMU

I recommend: http://fabrice.bellard.free.fr/qemu/user-doc.html Regards, Eduardo

Re: QEMU Automated Testing (was [Qemu-devel] qemu Makefile.target vl.h hw/acpi.c hw/adlib.c ...)

Sorry, I'm afraid I badly mixed up things in my mind. vncrec and pyvnc2swf record VNC server responses, not client actions, so they will hardly be of any help. To record and replay client actions these tools are more appropriate: http://cyberelk.net/tim/rfbproxy/ http://cyberelk.net/tim/rfbplay

Re: [Qemu-devel] time inside qemu

simulation] vm_start(); This just takes SystemC emulation time out of the equation. You cannot make any reliable performance measure of qemu's translated code, as already mentioned, but the former may be enough for your requirements. Regards, Eduardo Felipe

Re: [Qemu-devel] Re: Detecting an assembly instruction in QEMU

Hi 2007/4/17, Atif Hashmi <[EMAIL PROTECTED]>: But this prints "Transaction restart" once and then the program finishes. This means that commit transaction is not called the second time. Could you please tell me what am I doing wrong? Helper functions are outside the translated opcode strea

Re: [Qemu-devel] Re: Detecting an assembly instruction in QEMU

Hi Atif, Your code seems quite ok to me. Just try including stored_eip inside the DisasContext, otherwise you'll lose its value between calls to disas_insn function. Also make sure that the instructions you are using as markers are not executed elsewhere, as your compiler could generate them ins

Re: [Qemu-devel] Re: Detecting an assembly instruction in QEMU

Hi, You have a description of memory access instruction format in cpu-all.h, under /* CPU memory access without any memory or io remapping */ These instructions are defined in softmmu_header.h. If you don't care too much about performance it will be easier to modify the code written in C (undef

Re: [Qemu-devel] Re: Detecting an assembly instruction in QEMU

2007/4/25, Atif Hashmi <[EMAIL PROTECTED]>: Instructions like addl %ebx, (%eax) are also considered to be memory refernce instructions. Do these type of instructions also refer to the functions that you mentioned. No. You are using __asm_volatile("mov %al %al") to mark the start of your trans

Re: [Qemu-devel] Re: Detecting an assembly instruction in QEMU

I think I could not explain my question regarding "addl %ebx, (%eax)". What I wanted to ask was that this instruction also accesses the memory and I also need to intercept it within a transaction. Incase of "addl %ebx, (%eax)", Are the functions under "/* CPU memory access without any memory or

Re: [Qemu-devel] vnc with german keymap

Hi, Some time ago I made a patch to handle keyboard localization for vnc: http://lists.gnu.org/archive/html/qemu-devel/2006-08/msg00129.html It is outdated and most probably won't apply to current CVS, but with some tweaking it can improve things a bit. Regads, Eduardo Felipe 200

Re: [Qemu-devel] vnc with german keymap

2007/7/4, Juergen Lock <[EMAIL PROTECTED]>: Ah, thanx, I didnt see that one! :) I have a qeuestion tho: does this patch do deadkey handling on the host? Yes. IIRC I needed that because some VNC clients I tested didn't send dead keys to the server. They just waited for a full character to be

Re: [Qemu-devel] vnc with german keymap

2007/7/6, Juergen Lock <[EMAIL PROTECTED]>: On Thu, Jul 05, 2007 at 10:42:03AM +0200, Eduardo Felipe wrote: > Your VNC client probably sends deadkey messages... or maybe I have a > complicated way to handle simple things :) Yup, I tested with tightvnc-1.3.8. I've tried tig

[Qemu-devel] [Patch] Support UltraVNC clients

Hi, UltraVNC clients report non standard RFB protocol 3.4. Attached patch makes vnc server treat them as 3.3. Regards, Edu *** vnc.c 17 Sep 2007 08:09:45 - 1.24 --- vnc.c 26 Sep 2007 22:44:57 - @@ -1818,6 +1818,7 @@ VNC_DEBUG("Client request protocol version %d.%d\n", vs->major, vs->

[Qemu-devel] [Patch] VNC: Fix crash with non-resizing clients

Hi, 2007/9/25, GUERRAZ Francois <[EMAIL PROTECTED]>: > > > About your VNC problems : I have had problems w/ vnc too (see > http://qemu-forum.ipi.fi/viewtopic.php?p=10468) but had no answer as > well... This problem happens when the VNC client doesn't support the DesktopSize pseudo-encoding. Qemu

Re: [Qemu-devel] [Patch] VNC: Fix crash with non-resizing clients

2007/10/3, Daniel P. Berrange <[EMAIL PROTECTED]>: > > > The memset calls in that patch are bogus & not correctly fixing the buffer > update problem. You're merely setting the 'old data' to have pixel value > 42 - if the guest OS framebuffer happens to also have aras with pixel > value > of 42 too,

Re: [Qemu-devel] fake device to access to host fs

2007/11/8, Tristan Gingold <[EMAIL PROTECTED]>: > > Hi, > > has anyone already implemented a fake device to access to the host FS ? > > I am planning to implement one soon, but if it is already available... > > Thanks, > Tristan. Hi, Have a look to the vvfat block device. Regards, Edu

Re: [Qemu-devel] qemu fpu/softfloat-specialize.h fpu/softfloat.c...

2007/11/21, Paul Brook <[EMAIL PROTECTED]>: > > > Ok the problem comes from bad copy&paste. Please find a patch below that > > fixes the problem on MIPS. > > > > av = float64_val(a); > > -bv = float64_val(a); > > +bv = float64_val(b); > > Applied, thanks for tracking this down. Sorry a

Re: [Qemu-devel] Windows build broken

2007/12/12, C.W. Betts <[EMAIL PROTECTED]>: > > Same problem with cygwin. I think it's a problem with BlockInterfaceType > not being correctly parsed on mingw-gcc for some odd reason. Hi, I don't think it is related with BlockInterfaceType itself. The problem is to use "interface" as a variabl

Re: [Qemu-devel] Windows build broken

2007/12/12, C.W. Betts <[EMAIL PROTECTED]>: > > Could you perhaps give a patch? I don't feel like going through and > changing every instance of BlockInterfaceType to something else. > Having a closer look I think the underlying problem is a name conflict with a #define in Mingw's header file ba

Re: [Qemu-devel] Problem with windows qemu port

around. Regards, Eduardo Felipe ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel