From: Zan Lynx <zlynx@acm.org>
To: Gregory Haskins <ghaskins@novell.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
avi@redhat.com, glommer@redhat.com, aliguori@us.ibm.com
Subject: Re: [KVM PATCH] KVM: introduce "xinterface" API for external interaction with guests
Date: Thu, 16 Jul 2009 13:38:39 -0600 [thread overview]
Message-ID: <4A5F81BF.5000301@acm.org> (raw)
In-Reply-To: <4A5F773C.2020303@novell.com>
Gregory Haskins wrote:
> Gregory Haskins wrote:
>> Note that if we are going to generalize the interface to support other
>> guests as you may have been suggesting above, it should probably stay
>> statically linked (and perhaps live in ./lib or something)
>>
>
> More specifically, it can no longer live in kvm.ko. I guess it
> technically doesn't have to be statically linked, though (e.g.
> xinterface.ko is fine, too).
Speaking as someone who knows nothing about this, if this is going to be
a module and visible in places like lsmod, could you name it something else?
I see "xinterface.ko" and the first thing in my head is "something to do
with the X Window System."
How about kvm_xinterface or vguest_xinterface?
--
Zan Lynx
zlynx@acm.org
"Knowledge is Power. Power Corrupts. Study Hard. Be Evil."
next prev parent reply other threads:[~2009-07-16 19:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 15:19 [KVM PATCH] xinterface Gregory Haskins
2009-07-16 15:19 ` [KVM PATCH] KVM: introduce "xinterface" API for external interaction with guests Gregory Haskins
2009-07-16 15:30 ` Sam Ravnborg
2009-07-16 15:31 ` Gregory Haskins
2009-07-16 15:37 ` Anthony Liguori
2009-07-16 15:47 ` Gregory Haskins
2009-07-16 16:09 ` Anthony Liguori
2009-07-16 16:52 ` Arnd Bergmann
2009-07-16 18:22 ` Gregory Haskins
2009-07-16 18:53 ` Gregory Haskins
2009-07-16 19:38 ` Zan Lynx [this message]
2009-07-16 19:48 ` Gregory Haskins
2009-07-16 19:46 ` Arnd Bergmann
2009-07-17 0:25 ` Gregory Haskins
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=4A5F81BF.5000301@acm.org \
--to=zlynx@acm.org \
--cc=aliguori@us.ibm.com \
--cc=arnd@arndb.de \
--cc=avi@redhat.com \
--cc=ghaskins@novell.com \
--cc=glommer@redhat.com \
--cc=kvm@vger.kernel.org \
--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