Just to be clear, to use this repository, you need a kernel tree with Rusty's virtio patch queue applied.
For instance, if you had the latest KVM git tree, you would then need to get Rusty's queue at http://ozlabs.org/~rusty/kernel/hg. I apply up to virtio:virtio_net-performance-stats.patch. Then you need to apply the three patches I just posted. Then you can do a "make sync LINUX=/path/to/kernel/tree" and then a make. You should end up with a virtio.ko, virtio_ring.ko, virtio_pci.ko, and a virtio_blk.ko. Regards, Anthony Liguori Anthony Liguori wrote: > Hi, > > I've posted a repo that contains my initial attempt at backporting the > virtio modules. I've tested against a 2.6.22, 2.6.20, and 2.6.18 kernel > (although I haven't tried the block device against 2.6.18). It requires > Rusty's patch queue plus the three patches I just sent to > [EMAIL PROTECTED] > > The makefile supports a 'make sync LINUX=/path/to/linux' just like the > kvm-userspace/kernel directory does. > > This is still rough as I haven't went through and made sure all of the > #if's are right. > > http://hg.codemonkey.ws/virtio-ext-modules > > Regards, > > Anthony Liguori > > ------------------------------------------------------------------------- > 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/kvm-devel > ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/kvm-devel
