On Friday 10 June 2011, Chris Metcalf wrote: > This still leaves open the question of what really should go in this new > directory. Is it just for drivers that manage/control the hypervisor? Or > is it also for drivers that just use the hypervisor to do I/O of some kind, > but aren't related to any other "family" of drivers, i.e., a driver that > would have been dumped in drivers/char or drivers/misc in the old days? > > My specific interest at the moment is the proposed tile-srom.c driver > (https://patchwork.kernel.org/patch/843892/), which uses a simple > hypervisor read/write API to access the portion of the SPI ROM used to hold > the boot stream for a TILE processor. I'd still put that driver in drivers/char for now, because it already contains similar drivers. We can probaby group them in a subdirectory of drivers/char at some point or move them out to a new directory. For your raw hcall passthrough driver, that would be something that should go into drivers/virt/ IMHO. Arnd -- 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
