From: Paolo Bonzini <pbonzini@redhat.com>
To: Borislav Petkov <bp@suse.de>, "Singh, Brijesh" <brijesh.singh@amd.com>
Cc: "Guenter Roeck" <linux@roeck-us.net>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
"x86@kernel.org" <x86@kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] KVM: X86: Add missing KVM_AMD dependency
Date: Tue, 9 Oct 2018 18:26:14 +0200 [thread overview]
Message-ID: <7c5f1b99-9556-09ee-93f4-3a36d43a9c8e@redhat.com> (raw)
In-Reply-To: <20181008173216.GJ6490@zn.tnic>
On 08/10/2018 19:32, Borislav Petkov wrote:
> 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
Creating arch/x86/kvm/{mmu,vmx,svm}/ has been on my todo list for a
while. If you would like to split the SEV bits, that would be a good start.
Paolo
prev parent reply other threads:[~2018-10-09 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 18:46 Guenter Roeck
2018-10-05 20:41 ` Paolo Bonzini
2018-10-05 22:03 ` Guenter Roeck
2018-10-05 22:18 ` Paolo Bonzini
2018-10-06 20:43 ` Guenter Roeck
2018-10-08 11:27 ` Paolo Bonzini
2018-10-08 14:52 ` Singh, Brijesh
2018-10-08 17:32 ` Borislav Petkov
2018-10-09 16:26 ` Paolo Bonzini [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7c5f1b99-9556-09ee-93f4-3a36d43a9c8e@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=brijesh.singh@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mingo@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®