> -----Original Message----- > From: Greg KH [mailto:gregkh@xxxxxxxxxxxxxxxxxxx] > Sent: Wednesday, May 18, 2016 1:27 PM > To: Jes Sorensen > Cc: Kershner, David A; corbet@xxxxxxx; tglx@xxxxxxxxxxxxx; > mingo@xxxxxxxxxx; hpa@xxxxxxxxx; Arfvidson, Erik; Sell, Timothy C; > hofrat@xxxxxxxxx; dzickus@xxxxxxxxxx; Curtin, Alexander Paul; > janani.rvchndrn@xxxxxxxxx; sudipm.mukherjee@xxxxxxxxx; > prarit@xxxxxxxxxx; Binder, David Anthony; nhorman@xxxxxxxxxx; > dan.j.williams@xxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; linux- > doc@xxxxxxxxxxxxxxx; driverdev-devel@xxxxxxxxxxxxxxxxxxxxxx; *S-Par- > Maintainer > Subject: Re: [PATCH 0/5] add bus driver for Unisys s-Par paravirtualized > devices to arch/x86 > > On Wed, May 18, 2016 at 12:03:58PM -0400, Jes Sorensen wrote: > > Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> writes: > > > On Tue, May 17, 2016 at 07:49:53PM -0400, Jes Sorensen wrote: > > >> > Ok, but still no need to put it under arch/ anything, it should go in > > >> > drivers/ like all other drivers and busses are, no matter what the arch > > >> > it happens to run on is. > > >> > > >> I don't think thats obvious. arch/x86/kvm is an example of this, Sparc > > >> and PPC also have their stuff under arch/. > > > > > > For some things, yes, but let's not make the same mistakes as others :) > > > > > > Look at drivers/hv/ for an example of a very x86-only bus and driver > > > subsystem living in drivers/ Please don't burry driver stuff in arch/ > > > the ARM developers are trying to fix their mistakes of the past and move > > > all of their cruft out of arch/ for that reason. > > > > Works for me. > > > > So should they put it in drivers/visorbus or drivers/bus/visorbus? > > drivers/visorbus please. drivers/bus/ is an "odd" thing :( > > > What about drivers/virt? Would you suggest hv and xen gets moved in > > there? > > Ah, yeah, that would be great, never noticed it before, despite being > there since 2011... > > thanks, > > greg k-h tglx, Ingo, Dave, Timur, Kumar: We have a bus driver currently in drivers/staging/unisys/visorbus/ that we are trying to get out of staging and into the kernel proper. Since "visorbus" is a driver to host a virtual bus presented to a Linux guest in a hypervisor environment (refer to drivers/staging/unisys/Documentation/overview.txt for more details), Greg KH and Jes Sorensen have suggested the possibility that drivers/virt/ might be a good place for visorbus. But right now, we see that the only driver under drivers/virt/ is the Freescale hypervisor environment, which made us wonder whether this was really the correct place. Would you have any guidance for us? Our intent is to push our visorbus out of staging immediately following the current merge window. Thanks. Tim Sell -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
