[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <53F06B6D.7050103@redhat.com>
Date: Sun, 17 Aug 2014 10:44:29 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Andy Lutomirski <luto@...capital.net>,
Theodore Ts'o <tytso@....edu>,
"H. Peter Anvin" <hpa@...or.com>, kvm list <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Kees Cook <keescook@...omium.org>, X86 ML <x86@...nel.org>,
Daniel Borkmann <dborkman@...hat.com>,
Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>,
Raghavendra K T <raghavendra.kt@...ux.vnet.ibm.com>,
Gleb Natapov <gleb@...nel.org>, Bandan Das <bsd@...hat.com>,
Andrew Honig <ahonig@...gle.com>,
KY Srinivasan <kys@...rosoft.com>
Subject: Re: [PATCH v5 0/5] random,x86,kvm: Rework arch RNG seeds and get
some from kvm
Il 13/08/2014 20:33, Andy Lutomirski ha scritto:
> 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.
Migration doesn't need an arch_random_init, only cloning does.
MS has an ACPI-based specification for this they call the "VM Generation
ID", which QEMU should be implementing it sooner rather than later. In
Linux we could add a generic notifier, and an x86 platform driver that
implements the VM Generation ID specification and invokes the notifier.
http://go.microsoft.com/fwlink/p/?LinkID=260709 (warning, .docx ahead)
KY, would you be interested in looking at this?
Paolo
--
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