Howdy Anthony, > Here's a tiny patch that adds a i386-kvm target. The main difference > between the i386-kvm and i386-softmmu target is that the -kvm target > does not have any of the dyngen infrastructure. This means that it will > build with gcc-4. I know you can do --cc=gcc to use gcc-4 but quite a > few versions of gcc-4 have trouble with compiling dyngen.
I understand that your approach is to remove the "binary translation" part of the vanilla qemu, because we dont need it. We only need the device emulation code of qemu for kvm. Do I understand correctly? If so, we do not need to depend on gcc3 tricks anymore. Removing the dependent on gcc3 is really an important achievement. Thanks, Jun ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ kvm-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kvm-devel
