From: Arnd Bergmann <arnd@arndb.de>
To: Chris Metcalf <cmetcalf@tilera.com>
Cc: linuxppc-dev@lists.ozlabs.org,
Linux Virtualization <virtualization@lists.linux-foundation.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
Timur Tabi <timur@freescale.com>,
konrad.wilk@oracle.com, kumar.gala@freescale.com,
linux-kernel@vger.kernel.org, akpm@kernel.org,
dsaxena@linaro.org, linux-console@vger.kernel.org,
greg@kroah.com, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH 7/7] [v4] drivers/virt: introduce Freescale hypervisor management driver
Date: Fri, 10 Jun 2011 17:36:14 +0200 [thread overview]
Message-ID: <201106101736.14850.arnd@arndb.de> (raw)
In-Reply-To: <4DF22770.4010103@tilera.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Chris Metcalf <cmetcalf@tilera.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
konrad.wilk@oracle.com, greg@kroah.com, kumar.gala@freescale.com,
linux-kernel@vger.kernel.org,
Linux Virtualization <virtualization@lists.linux-foundation.org>,
dsaxena@linaro.org, linux-console@vger.kernel.org,
akpm@kernel.org, linuxppc-dev@lists.ozlabs.org,
Timur Tabi <timur@freescale.com>,
alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH 7/7] [v4] drivers/virt: introduce Freescale hypervisor management driver
Date: Fri, 10 Jun 2011 17:36:14 +0200 [thread overview]
Message-ID: <201106101736.14850.arnd@arndb.de> (raw)
In-Reply-To: <4DF22770.4010103@tilera.com>
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
next prev parent reply other threads:[~2011-06-10 15:36 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 22:45 [PATCH 7/7] [v4] drivers/virt: introduce Freescale hypervisor management driver Timur Tabi
2011-06-08 22:45 ` Timur Tabi
2011-06-08 23:10 ` Randy Dunlap
2011-06-08 23:10 ` Randy Dunlap
2011-06-08 23:10 ` Randy Dunlap
2011-06-08 23:16 ` Timur Tabi
2011-06-08 23:16 ` Timur Tabi
2011-06-08 23:16 ` Timur Tabi
2011-06-09 7:38 ` Arnd Bergmann
2011-06-09 7:38 ` Arnd Bergmann
2011-06-09 16:32 ` Randy Dunlap
2011-06-09 16:32 ` Randy Dunlap
2011-06-09 16:36 ` Timur Tabi
2011-06-09 16:36 ` Timur Tabi
2011-06-09 16:36 ` Timur Tabi
2011-06-09 16:42 ` Randy Dunlap
2011-06-09 16:42 ` Randy Dunlap
2011-06-09 16:42 ` Randy Dunlap
2011-06-09 16:48 ` Timur Tabi
2011-06-09 16:48 ` Timur Tabi
2011-06-09 16:48 ` Timur Tabi
2011-06-09 16:48 ` Timur Tabi
2011-06-09 16:36 ` Timur Tabi
2011-06-09 16:32 ` Randy Dunlap
2011-06-10 14:17 ` Chris Metcalf
2011-06-10 14:17 ` Chris Metcalf
2011-06-10 14:17 ` Chris Metcalf
2011-06-10 15:36 ` Arnd Bergmann
2011-06-10 15:36 ` Arnd Bergmann [this message]
2011-06-10 15:36 ` Arnd Bergmann
2011-06-10 14:17 ` Chris Metcalf
2011-06-09 7:38 ` Arnd Bergmann
2011-06-09 7:29 ` Arnd Bergmann
2011-06-09 7:29 ` Arnd Bergmann
2011-06-09 18:55 ` Timur Tabi
2011-06-09 18:55 ` Timur Tabi
2011-06-09 18:55 ` Timur Tabi
2011-06-09 20:20 ` Arnd Bergmann
2011-06-09 20:20 ` Arnd Bergmann
2011-06-09 20:24 ` Timur Tabi
2011-06-09 20:24 ` Timur Tabi
2011-06-09 20:24 ` Timur Tabi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201106101736.14850.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@kernel.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cmetcalf@tilera.com \
--cc=dsaxena@linaro.org \
--cc=greg@kroah.com \
--cc=konrad.wilk@oracle.com \
--cc=kumar.gala@freescale.com \
--cc=linux-console@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=randy.dunlap@oracle.com \
--cc=timur@freescale.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.