| 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
| ||
|
Message-ID: <4A5F81BF.5000301@acm.org> Date: Thu, 16 Jul 2009 13:38:39 -0600 From: Zan Lynx <zlynx@....org> To: Gregory Haskins <ghaskins@...ell.com> CC: 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 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@....org "Knowledge is Power. Power Corrupts. Study Hard. Be Evil." -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists