From: Pavel Machek <pavel@ucw.cz>
To: Jeff Garzik <jeff@garzik.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
kvm-devel@lists.sourceforge.net, Avi Kivity <avi@qumranet.com>,
Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [kvm-devel] [RFC] Stable kvm userspace interface
Date: Fri, 12 Jan 2007 11:19:27 +0000 [thread overview]
Message-ID: <20070112111927.GB7145@ucw.cz> (raw)
In-Reply-To: <45A5F4A5.9000408@garzik.org>
Hi!
> >>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...
Yep, but at that point you have 32 vs. 64bit nightmare back... and
stronger, because sysfs does not have compat handling.
--
Thanks for all the (sleeping) penguins.
next prev parent reply other threads:[~2007-01-12 11:19 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
[not found] ` <45A39A97.5060807-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-09 13:47 ` Jeff Garzik
[not found] ` <45A39D0D.7090007-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
2007-01-09 14:02 ` James Morris
2007-01-09 14:11 ` Avi Kivity
2007-01-11 7:34 ` Arnd Bergmann
[not found] ` <200701110834.43800.arnd-r2nGTMty4D4@public.gmane.org>
2007-01-11 8:03 ` Avi Kivity
2007-01-11 8:26 ` Jeff Garzik
[not found] ` <45A5F4A5.9000408-o2qLIJkoznsdnm+yROfE0A@public.gmane.org>
2007-01-11 8:32 ` Avi Kivity
2007-01-12 11:19 ` Pavel Machek [this message]
2007-01-11 17:40 ` David Lang
2007-01-11 7:26 ` Arnd Bergmann
[not found] ` <200701110826.28535.arnd-r2nGTMty4D4@public.gmane.org>
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=20070112111927.GB7145@ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=arnd@arndb.de \
--cc=avi@qumranet.com \
--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