On 6/6/2011 12:24 PM, Arnd Bergmann wrote: > On Monday 06 June 2011, Timur Tabi wrote:. >> And what about my concern that my driver will be the only one in drivers/virt? > I have no doubt that more of these will come. Chris Metcalf is currently > looking for a home for his tilera hypervisor drivers, and we have the > microsoft hyperv drivers in drivers/staging, so they will hopefully > move to a proper place later. We also have similar drivers in other > places, e.g. drivers/ps3/ps3-sys-manager.c, drivers/s390/char/vmcp.c > or parts of drivers/xen. It might help if someone (Arnd?) wanted to propose a statement of what drivers/virt was really for. If it's for any Linux driver that upcalls to a hypervisor for any reason, then the Tilera paravirtualized drivers fit in well. If it's intended more for drivers that guests running under a hypervisor can use to talk to the hypervisor itself (e.g. managing notifications that a hypervisor delivers to a guest to cause it to shut down or take other actions), then it doesn't seem like the Tilera paravirtualized device drivers belong there, since they're just using the Tilera hypervisor synchronously to do I/O or get/set device and driver state. -- Chris Metcalf, Tilera Corp. http://www.tilera.com -- To unsubscribe from this list: send the line "unsubscribe linux-console" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
