Christian Borntraeger wrote: > Am Freitag, 9. November 2007 schrieb Dor Laor: > >> I believe that the network interface will quickly go to the kernel since >> copy takes most of the >> cpu time and qemu does not support scatter gather dma at the moment. >> Nevertheless using pio seems good enough, Anthony's suggestion of >> notifying the kernel using ioctls >> is logical. If we'll run into troubles further on we can add a hypercall >> capability and if exist use hypercalls >> instead of pios. >> > > Sorry for being late in this thread. > We (s390) will need a hypercall as we do not have port I/O. I think it should > be > possible to default to hypercall on s390 and use pio everywhere else. >
Or be generic: advertise the methods available according to host (kvm/x86, qemu/x86, kvm/s390) and let the guest pick. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
