All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@lists.ozlabs.org,
	Linux Virtualization <virtualization@lists.linux-foundation.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	konrad.wilk@oracle.com, greg@kroah.com, kumar.gala@freescale.com,
	linux-kernel@vger.kernel.org, cmetcalf@tilera.com,
	akpm@kernel.org, dsaxena@linaro.org,
	linux-console@vger.kernel.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: Thu, 9 Jun 2011 09:38:22 +0200	[thread overview]
Message-ID: <201106090938.23027.arnd@arndb.de> (raw)
In-Reply-To: <20110608161009.7b05d305.randy.dunlap@oracle.com>

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.

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.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@lists.ozlabs.org,
	Linux Virtualization <virtualization@lists.linux-foundation.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Timur Tabi <timur@freescale.com>,
	konrad.wilk@oracle.com, kumar.gala@freescale.com,
	linux-kernel@vger.kernel.org, cmetcalf@tilera.com,
	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: Thu, 9 Jun 2011 09:38:22 +0200	[thread overview]
Message-ID: <201106090938.23027.arnd@arndb.de> (raw)
In-Reply-To: <20110608161009.7b05d305.randy.dunlap@oracle.com>

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.

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.

	Arnd

  parent reply	other threads:[~2011-06-09  7:38 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 [this message]
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: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-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
2011-06-10 15:36       ` Arnd Bergmann
2011-06-10 14:17     ` Chris Metcalf
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=201106090938.23027.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.