From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [PATCH v5 0/5] random,x86,kvm: Rework arch RNG seeds and get some from kvm Date: Wed, 13 Aug 2014 19:41:37 -0700 Message-ID: <53EC21E1.80502@zytor.com> References: <20140812191723.GI12871@thunk.org> <53EB1859.6030800@zytor.com> <20140813143209.GD6437@thunk.org> <53EBA435.3020207@zytor.com> <20140813182219.GE6437@thunk.org> <53EBB214.4030102@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit To: Andy Lutomirski , "Theodore Ts'o" , kvm list , "linux-kernel@vger.kernel.org" , Kees Cook , X86 ML , Daniel Borkmann , Srivatsa Vaddagiri , Raghavendra K T , Gleb Natapov , Paolo Bonzini , Bandan Das , Andrew Honig Return-path: In-Reply-To: <53EBB214.4030102@zytor.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 08/13/2014 11:44 AM, H. Peter Anvin wrote: > On 08/13/2014 11:33 AM, Andy Lutomirski wrote: >> >> As for doing arch_random_init after clone/migration, I think we'll >> need another KVM extension for that, since, AFAIK, we don't actually >> get notified that we were cloned or migrated. That will be >> nontrivial. Maybe we can figure that out at KS, too. >> > > We don't need a reset when migrated (although it might be a good idea > under some circumstances, i.e. if the pools might somehow have gotten > exposed) but definitely when cloned. > But yes, we need a notification. For obvious reasons there is no suspend event (one can snapshot a running VM) but we need to be notified upon wakeup, *or* we need to give KVM a way to update the necessary state. -hpa