From: Arnd Bergmann <arnd@arndb•de>
To: Scott Wood <scottwood@freescale•com>
Cc: greg@kroah•com, kumar.gala@freescale•com,
linux-kernel@vger•kernel.org, akpm@kernel•org,
linux-console@vger•kernel.org, linuxppc-dev@lists•ozlabs.org,
Timur Tabi <timur@freescale•com>
Subject: Re: [PATCH 7/7] [v2] drivers/misc: introduce Freescale hypervisor management driver
Date: Fri, 3 Jun 2011 17:28:43 +0200 [thread overview]
Message-ID: <201106031728.43707.arnd@arndb.de> (raw)
In-Reply-To: <20110601172412.761ff799@schlenkerla.am.freescale.net>
On Thursday 02 June 2011, Scott Wood wrote:
> I wanted to have the hypervisor take an update dtb (we already have special
> meta-properties for things like deletion as part of the hv config
> mechanism). But others on the project wanted to keep it simple, and so
> get/set property it was. :-/
>
> It's unlikely to change at this point without a real need.
>
> As for a filesystem interface, it's not a good match either.
> You can't iterate over anything to read out the full tree from the hv.
kexec iterates over /proc/device-tree to create a dts blob.
> You can't delete anything.
rm, rmdir
> You can't create empty nodes.
mkdir
> The hv interface was meant to enable some specific management actions,
> rather than to provide general device tree access. This driver is a thin
> wrapper around the management hcalls.
A file system would be a slightly more abstract interface to do the
same thing, I gues.
> There would still be other ioctls needed for starting/stopping the
> partition, etc.
Right, although you could model them as a file interface as well.
KVMfs is one example doing that.
Arnd
next prev parent reply other threads:[~2011-06-03 15:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 18:35 [PATCH 7/7] [v2] drivers/misc: introduce Freescale hypervisor management driver Timur Tabi
2011-06-01 19:46 ` Alan Cox
2011-06-01 20:24 ` Timur Tabi
2011-06-01 20:34 ` Alan Cox
2011-06-01 20:54 ` Scott Wood
2011-06-01 21:45 ` Alan Cox
2011-06-01 21:40 ` Arnd Bergmann
2011-06-01 22:24 ` Scott Wood
2011-06-03 15:28 ` Arnd Bergmann [this message]
2011-06-03 16:22 ` Scott Wood
2011-06-06 15:53 ` Arnd Bergmann
2011-06-06 18:15 ` Scott Wood
2011-06-06 19:48 ` Arnd Bergmann
2011-06-02 21:28 ` Timur Tabi
2011-06-03 15:24 ` Arnd Bergmann
2011-06-03 15:28 ` Timur Tabi
2011-06-06 15:42 ` Arnd Bergmann
2011-06-06 15:48 ` Timur Tabi
2011-06-06 16:03 ` Arnd Bergmann
2011-06-06 16:09 ` Timur Tabi
2011-06-06 16:24 ` Arnd Bergmann
2011-06-06 16:27 ` Timur Tabi
2011-06-06 21:01 ` Chris Metcalf
2011-06-06 21:23 ` Konrad Rzeszutek Wilk
2011-06-06 23:04 ` Chris Metcalf
2011-06-07 7:08 ` Arnd Bergmann
2011-06-07 16:49 ` Chris Metcalf
2011-06-07 19:16 ` Arnd Bergmann
2011-06-07 19:20 ` Timur Tabi
2011-06-07 19:34 ` Arnd Bergmann
2011-06-03 14:44 ` Timur Tabi
2011-06-03 15:17 ` Arnd Bergmann
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=201106031728.43707.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=akpm@kernel$(echo .)org \
--cc=greg@kroah$(echo .)com \
--cc=kumar.gala@freescale$(echo .)com \
--cc=linux-console@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=scottwood@freescale$(echo .)com \
--cc=timur@freescale$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox