Re: [PATCH 7/7] [v2] drivers/misc: introduce Freescale hypervisor management driver
- To: Chris Metcalf <cmetcalf@xxxxxxxxxx>
- Subject: Re: [PATCH 7/7] [v2] drivers/misc: introduce Freescale hypervisor management driver
- From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
- Date: Mon, 6 Jun 2011 17:23:56 -0400
- Cc: Arnd Bergmann <arnd@xxxxxxxx>, Timur Tabi <timur@xxxxxxxxxxxxx>, Deepak Saxena <dsaxena@xxxxxxxxxx>, kumar.gala@xxxxxxxxxxxxx, benh@xxxxxxxxxxxxxxxxxxx, greg@xxxxxxxxx, akpm@xxxxxxxxxx, linuxppc-dev@xxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-console@xxxxxxxxxxxxxxx
- In-reply-to: <4DED4030.9050503@xxxxxxxxxx>
- List-id: <linux-console.vger.kernel.org>
- References: <1306953337-15698-1-git-send-email-timur@xxxxxxxxxxxxx> <201106061803.58531.arnd@xxxxxxxx> <4DECFBC5.6070205@xxxxxxxxxxxxx> <201106061824.53844.arnd@xxxxxxxx> <4DED4030.9050503@xxxxxxxxxx>
- Sender: linux-console-owner@xxxxxxxxxxxxxxx
- User-agent: Mutt/1.5.21 (2010-09-15)
On Mon, Jun 06, 2011 at 05:01:36PM -0400, Chris Metcalf wrote:
> 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
Was for? I am not seeing it in v3.0-rc2?
> 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
I believe that the code that deals with specific subsystem (so block API
for example) would reside in subsystem directory (so drivers/block would have
your virtualization block driver). This allows the maintainer of block
to make sure your driver is OK.
> 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
That looks to be arch/<x>/tilera/virt/ candidate?
> 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.
Well, I/O sounds like block API or network API. But then you are also
doing management ioctl - which implies "drivers". "drivers/tilera" does not
> Chris Metcalf, Tilera Corp.
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
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
[Index of Archives]
[Video 4 Linux]