From: Avi Kivity <avi@qumranet.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
kvm-devel@lists.sourceforge.net, 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:32:22 +0200 [thread overview]
Message-ID: <45A5F616.3040305@qumranet.com> (raw)
In-Reply-To: <45A5F4A5.9000408@garzik.org>
Jeff Garzik wrote:
> Arnd Bergmann wrote:
>> On Tuesday 09 January 2007 14:47, Jeff Garzik wrote:
>>> Can we please avoid adding a ton of new ioctls? ioctls inevitably
>>> require 64-bit compat code for certain architectures, whereas
>>> sysfs/procfs does not.
>>
>> For performance reasons, an ascii string based interface is not
>> desireable here, some of these calls should be optimized to
>> the point of counting cycles.
>
> sysfs does not require ASCII...
>
The main kvm ioctl switches the execution mode to guest mode. Just like
a syscall enters kernel mode, ioctl(vcpu_fd, KVM_VCPU_RUN) enters the
guest address space and begins executing guest code.
I don't see how to model that with sysfs.
There are other objections as well. sysfs is a public interface, whereas
kvm is a process private attribute. These objections don't apply to
/proc though.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2007-01-11 8:32 UTC|newest]
Thread overview: 12+ 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:47 ` Jeff Garzik
2007-01-09 14:02 ` [kvm-devel] " James Morris
2007-01-09 14:11 ` Avi Kivity
2007-01-11 7:34 ` [kvm-devel] " Arnd Bergmann
2007-01-11 8:03 ` Avi Kivity
2007-01-11 8:26 ` Jeff Garzik
2007-01-11 8:32 ` Avi Kivity [this message]
2007-01-12 11:19 ` Pavel Machek
2007-01-11 17:40 ` David Lang
2007-01-11 7:26 ` Arnd Bergmann
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=45A5F616.3040305@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox