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: Sun, 07 Oct 2012 11:51:35 +0200 From: Avi Kivity <avi@...hat.com> To: Raghavendra K T <raghavendra.kt@...ux.vnet.ibm.com> CC: Gleb Natapov <gleb@...hat.com>, Jiannan Ouyang <ouyang@...pitt.edu>, Peter Zijlstra <peterz@...radead.org>, Rik van Riel <riel@...hat.com>, "H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>, Marcelo Tosatti <mtosatti@...hat.com>, Srikar <srikar@...ux.vnet.ibm.com>, "Nikunj A. Dadhania" <nikunj@...ux.vnet.ibm.com>, KVM <kvm@...r.kernel.org>, chegu vinod <chegu_vinod@...com>, "Andrew M. Theurer" <habanero@...ux.vnet.ibm.com>, LKML <linux-kernel@...r.kernel.org>, Srivatsa Vaddagiri <srivatsa.vaddagiri@...il.com> Subject: Re: [PATCH RFC 1/2] kvm: Handle undercommitted guest case in PLE handler On 10/05/2012 10:36 AM, Raghavendra K T wrote: >>> >>> You can store i in the vcpu itself: >>> >>> set_bit(vcpu->index, &kvm->preempted); >>> >> This will make the fact that vcpus are stored in an array into API >> instead of implementation detail :( There were patches for vcpu >> destruction that changed the array to rculist. Well, it will be still >> possible to make the array rcu protected and copy it every time vcpu is >> deleted/added I guess. >> > > If IUC, summary is, we are going with > - Let vcpu array be rcu protected. That's for the future. For now ->vcpus[] is statically allocated. > - we use index inside vcpu and should be updated when a vcpu is > added/deleted. Yes. -- error compiling committee.c: too many arguments to function -- 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