[Qemu-devel] On-demand taint tracking

2007-02-23 Thread Heng Yin
Hi Qemu developers, I have implemented a whole-system taint tracking system on Qemu. But the performance overhead is big. Now I want to optimize it by performing on-demand taint tracking. The idea is that Qemu runs in virtualization mode most of time (running with kqemu), and switches to emula

Re: [Qemu-devel] Page protection and i386 cmpxchg8b

2007-02-23 Thread Ilya Shar
--- Pierre d'Herbemont <[EMAIL PROTECTED]> wrote: Hi Pierre, Thanks for your reply - please see comments inserted below: > Hi Ilya! > > On 23 févr. 07, at 21:32, Ilya Shar wrote: > > > I'm running i386-darwin-usrer on i386 and some > apps > > (Safari browser) crash because cmpxchg8b attempts

Re: [Qemu-devel] armv6 support

2007-02-23 Thread Paul Brook
On Friday 23 February 2007 20:09, Rodrigo Vivi wrote: > Hi all, > > Is there someone working on armv6 support? > I'm very interested to help this development... I already have ARMv6 and ARMv7 implemented, but am unable to release the code. See: http://lists.gnu.org/archive/html/qemu-devel/2006-03

Re: [Qemu-devel] Page protection and i386 cmpxchg8b

2007-02-23 Thread Pierre d'Herbemont
Hi Ilya! On 23 févr. 07, at 21:32, Ilya Shar wrote: I'm running i386-darwin-usrer on i386 and some apps (Safari browser) crash because cmpxchg8b attempts to wrie to a qemu-allocated page which is readable but write-protected. When I comment out mprotect in exec.c Are you sure it does Safari

[Qemu-devel] make install qemu-system-x86

2007-02-23 Thread Rob Landley
Could make install do a "qemu-system-x86" and then symlink the "qemu" name to whatever the host platform happens to be? (So if you build qemu on x86-64 then qemu points to "qemu-system-x86_64"? Or if you build the sucker on a PPC system...) The relevant code seems to be is in Makefile.target,

[Qemu-devel] Page protection and i386 cmpxchg8b

2007-02-23 Thread Ilya Shar
Hi, I'm running i386-darwin-usrer on i386 and some apps (Safari browser) crash because cmpxchg8b attempts to wrie to a qemu-allocated page which is readable but write-protected. When I comment out mprotect in exec.c //mprotect(g2h(page_addr), qemu_host_page_size, // (pr

[Qemu-devel] armv6 support

2007-02-23 Thread Rodrigo Vivi
Hi all, Is there someone working on armv6 support? I'm very interested to help this development... Thanks, Rodrigo Vivi. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel

[Qemu-devel] Re: QCOW image corruption under QEMU 0.9.0

2007-02-23 Thread J M Cerqueira Esteves
J M Cerqueira Esteves wrote: >11776-11791: 0x6c6f3d 6c6f0a 6574 68303d 6574 68300a 6c6f 3d 6c6f 0a 65746830 3d 65746830 0a or, of course (duh, I should have noticed, although I'm not sure this can help), lo=lo\n e

Re: [Qemu-devel] [PATCH] syscall readahead

2007-02-23 Thread Thiemo Seufer
Kirill A. Shutemov wrote: > Patch from Debian patchset in the attachment > --- linux-user/syscall.c.orig 2006-11-05 07:07:19.0 +0200 > +++ linux-user/syscall.c 2006-11-05 07:07:25.0 +0200 > @@ -3947,7 +3956,8 @@ long do_syscall(void *cpu_env, int num, > ret = get_err

Re: [Qemu-devel] [PATCH] [REPOST] Simplily linux-user/path.c

2007-02-23 Thread Thiemo Seufer
Kirill A. Shutemov wrote: > Fixed version of the patch in the attacment. Please, comment. [snip] > /* Look for path in emulation dir, otherwise return name. */ > const char *path(const char *name) > { > +char *newname = (char *) alloca(strlen(pref)+strlen(name)+1); > +struct stat buf; >

Re: [Qemu-devel] How to get 1280x1024 display from guest running Xorg?

2007-02-23 Thread Julian Seward
Thanks for the feedback. Since I do not wish to be involved in a great battle (as you so nicely put it) I'll stick with VMware (sigh). J On Wednesday 21 February 2007 15:05, Robin Atwood wrote: > On Wednesday 21 Feb 2007, Julian Seward wrote: > > (replying off list) > > > > So you have Solari

[Qemu-devel] QCOW image corruption under QEMU 0.9.0

2007-02-23 Thread J M Cerqueira Esteves
Greetings I got some error messages shortly after booting a Debian guest under QEMU 0.9.0. I did not annotate those, but they made me believe there could be disk access problems, and if fact something weird happened to one of the disk images (this was using two images, for hda and hdb): After sh