From: Avi Kivity <avi@qumranet.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kvm-devel@lists.sourceforge.net, Jeff Garzik <jeff@garzik.org>,
Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [kvm-devel] [RFC] Stable kvm userspace interface
Date: Thu, 11 Jan 2007 10:03:47 +0200 [thread overview]
Message-ID: <45A5EF63.3040601@qumranet.com> (raw)
In-Reply-To: <200701110834.43800.arnd@arndb.de>
Arnd Bergmann wrote:
> I still think that in the long term, we should migrate to
> new system calls and a special file system for kvm, which
> might be non-mountable.
The inode-per-vm and inode-per-vcpu approach sort-of-implies a
nonmountable special filesystem, so with the proposed change, we'll be
halfway there.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>,
linux-kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Jeff Garzik <jeff-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
Subject: Re: [RFC] Stable kvm userspace interface
Date: Thu, 11 Jan 2007 10:03:47 +0200 [thread overview]
Message-ID: <45A5EF63.3040601@qumranet.com> (raw)
In-Reply-To: <200701110834.43800.arnd-r2nGTMty4D4@public.gmane.org>
Arnd Bergmann wrote:
> I still think that in the long term, we should migrate to
> new system calls and a special file system for kvm, which
> might be non-mountable.
The inode-per-vm and inode-per-vcpu approach sort-of-implies a
nonmountable special filesystem, so with the proposed change, we'll be
halfway there.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-01-11 8:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 13:37 [RFC] Stable kvm userspace interface Avi Kivity
2007-01-09 13:37 ` Avi Kivity
2007-01-09 13:47 ` Jeff Garzik
2007-01-09 13:47 ` Jeff Garzik
2007-01-09 14:02 ` [kvm-devel] " James Morris
2007-01-09 14:02 ` James Morris
2007-01-09 14:11 ` Avi Kivity
2007-01-09 14:11 ` Avi Kivity
2007-01-11 7:34 ` [kvm-devel] " Arnd Bergmann
2007-01-11 7:34 ` Arnd Bergmann
2007-01-11 8:03 ` Avi Kivity [this message]
2007-01-11 8:03 ` Avi Kivity
2007-01-11 8:26 ` [kvm-devel] " Jeff Garzik
2007-01-11 8:26 ` Jeff Garzik
2007-01-11 8:32 ` [kvm-devel] " Avi Kivity
2007-01-11 8:32 ` Avi Kivity
2007-01-12 11:19 ` [kvm-devel] " Pavel Machek
2007-01-11 17:40 ` David Lang
2007-01-11 17:40 ` David Lang
2007-01-11 7:26 ` [kvm-devel] " Arnd Bergmann
2007-01-11 7:26 ` Arnd Bergmann
2007-01-11 8:02 ` [kvm-devel] " Avi Kivity
2007-01-11 8:02 ` Avi Kivity
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=45A5EF63.3040601@qumranet.com \
--to=avi@qumranet.com \
--cc=akpm@osdl.org \
--cc=arnd@arndb.de \
--cc=jeff@garzik.org \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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.