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
| ||
|
Date: Fri, 02 Dec 2011 19:26:57 +0100 From: Jan Kiszka <jan.kiszka@...mens.com> To: Liu Ping Fan <kernelfans@...il.com> CC: avi@...hat.com, kvm@...r.kernel.org, linux-kernel@...r.kernel.org, aliguori@...ibm.com, gleb@...hat.com Subject: Re: [PATCH] kvm: make vcpu life cycle separated from kvm instance On 2011-12-02 07:26, Liu Ping Fan wrote: > From: Liu Ping Fan <pingfank@...ux.vnet.ibm.com> > > Currently, vcpu can be destructed only when kvm instance destroyed. > Change this to vcpu's destruction taken when its refcnt is zero, > and then vcpu MUST and CAN be destroyed before kvm's destroy. I'm lacking the big picture yet (would be good to have in the change log - at least I'm too lazy to read the code): What increments the refcnt, what decrements it again? IOW, how does user space controls the life-cycle of a vcpu after your changes? Thanks, Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux -- 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