[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181008173216.GJ6490@zn.tnic>
Date: Mon, 8 Oct 2018 19:32:16 +0200
From: Borislav Petkov <bp@...e.de>
To: "Singh, Brijesh" <brijesh.singh@....com>
Cc: Paolo Bonzini <pbonzini@...hat.com>,
Guenter Roeck <linux@...ck-us.net>,
Radim Krčmář <rkrcmar@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"x86@...nel.org" <x86@...nel.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] KVM: X86: Add missing KVM_AMD dependency
On Mon, Oct 08, 2018 at 02:52:46PM +0000, Singh, Brijesh wrote:
> Does it make sense to move all the SEV specific code in svm-sev.c ?
> I am looking to add SEV migration support very soon, and can see
> myself adding more SEV command handling which will grow svm.c further.
Amen to that - svm.c is pretty huge already. And if you end up moving
facilities, you can simply call it sev.c
Just my 2¢.
Thx.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
Powered by blists - more mailing lists