On 06/09/11 00:38, Arnd Bergmann wrote: > On Thursday 09 June 2011 01:10:09 Randy Dunlap wrote: >> On Wed, 8 Jun 2011 17:45:54 -0500 Timur Tabi wrote: >> >>> Add the drivers/virt directory, which houses drivers that support >>> virtualization environments, and add the Freescale hypervisor management >>> driver. >> >> It can't go in linux/virt or linux/virt/fsl instead? why drivers/ ? >> >> or maybe linux/virt should be drivers/virt ? > > See discussion for v2 of this patch. I suggested that drivers/firmware and virt/ > as options, the counterarguments were that drivers/firmware is for passive > firmware as opposed to firmware that acts as a hypervisor, and that virt/ is > for the host side of hypervisors like kvm, not for guests. OK, I read that thread. Didn't see a real consensus there. If you were not the drivers/misc/ maintainer, would you mind if this driver lived in drivers/misc/? I wouldn't. But it sounds like virt/ needs virt/host/ and virt/guest/ to me. > The driver in here most closely resembles the xen dom0 model, where a > priviledged guest controls other guests, but unlike xen there is a single > driver file, so there is no need to have drivers/fsl-hv directory just > for this one file. We do have a number of other hypervisors that fit in the > same category, so they can be added here later. -- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** -- 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
