linux-kernel - Re: [KVM PATCH] KVM: introduce "xinterface" API for external interaction with guests

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 16 Jul 2009 15:48:20 -0400
From:	Gregory Haskins <gregory.haskins@...il.com>
To:	Zan Lynx <zlynx@....org>
CC:	Gregory Haskins <ghaskins@...ell.com>,
	Arnd Bergmann <arnd@...db.de>, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org, avi@...hat.com, glommer@...hat.com,
	aliguori@...ibm.com
Subject: Re: [KVM PATCH] KVM: introduce "xinterface" API for external interaction
 with guests

Zan Lynx wrote:
> 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?
>

Heh, I totally agree.  That was just pseudo-naming, anyway. ;)

If it was going to be generic, I would do something like
"virt-xinterface.ko".

Kind Regards,
-Greg


Download attachment "signature.asc" of type "application/pgp-signature" (267 bytes)