Hi all, Yes, now I fixed some kemu kernel module codes and which is ready for your testing. It works fine under current my environmtn (thinkpat t60p) with DragonFry 2.3-0-dev host, DragonFly 2.2 guest.
The problem causing performance issue was in ioctl call with KQEMU_SET_PHYS_MEM. Pleaes replace attachment with previous my post and build kqemu.ko by using Makefile.dragonfly I'd like to know especially it works with USB devices. Pleaese let me know if you find someting interesting. thank you for the kindly support :-) -Naoya On Sun, Apr 19, 2009 at 3:23 AM, Johannes Hofmann <[email protected]> wrote: > Hi, > > Michael Neumann <[email protected]> wrote: >> On Fri, 10 Apr 2009 23:16:37 -0700 >> Naoya Sugioka <[email protected]> wrote: >> >>> Hi, >>> >>> >>> I just motivated to port kqemu module since QEMU starts working good >>> recently, according to this mailing list. >> >> Hi, >> >> I'd really like to see a working kqemu on DragonFly... >> >> If your compare kqemutest.messages.fly with kqemutest.messages.linux >> you'll notice some "kqemu_unlock_user_page failed" messages for >> Dragonfly nearly the end. They don't occur on Linux. Maybe this is >> related to your performance problems? > > After looking at vm/vm_glue.c and vm/vm_map.c I tried to use: > > ret = vm_map_wire(&vm->vm_map, va, va+PAGE_SIZE, 0); > > to wire a page and: > > ret = vm_map_wire(&vm->vm_map, va, va+PAGE_SIZE, KM_PAGEABLE); > > to unwire it. > > This seems to solve the "kqemu_unlock_user_page failed" errors, but I > still get guest panics with the linux-0.2.img form qemu.org and don't > see any performance gains :( > > Cheers, > Johannes >
kqemu-dragonfly.c
Description: Binary data
