From: "Singh, Brijesh" <brijesh.singh@amd.com>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "x86@kernel.org" <x86@kernel.org>,
"Singh, Brijesh" <brijesh.singh@amd.com>,
"Borislav Petkov" <bp@alien8.de>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Joerg Roedel" <joro@8bytes.org>,
"Lendacky, Thomas" <Thomas.Lendacky@amd.com>
Subject: [PATCH 0/2] KVM: SVM: move the SEV command handling into a separate file
Date: Fri, 1 Feb 2019 16:47:12 +0000 [thread overview]
Message-ID: <20190201164654.3888-1-brijesh.singh@amd.com> (raw)
svm.c is pretty huge, before we add more SEV specific commands (e.g SEV-ES,
SEV-Migration etc) lets move the SEV command handling into a separate file.
There is no logical changes in this series.
The patch is based on motivation from this thread:
https://marc.info/?l=linux-kernel&m=153910240507399&w=2
Cc: Borislav Petkov <bp@alien8.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Radim Krčmář" <rkrcmar@redhat.com>
Cc: Joerg Roedel <joro@8bytes.org>
Cc: Tom Lendacky <Thomas.Lendacky@amd.com>
Brijesh Singh (2):
KVM: SVM: move common struct definitions to header file
KVM: SVM: move the SEV specific function in a separate file
arch/x86/include/asm/svm.h | 155 +++++
arch/x86/kvm/Makefile | 2 +
arch/x86/kvm/sev.c | 1076 +++++++++++++++++++++++++++++++
arch/x86/kvm/sev.h | 40 ++
arch/x86/kvm/svm.c | 1234 +-----------------------------------
5 files changed, 1296 insertions(+), 1211 deletions(-)
create mode 100644 arch/x86/kvm/sev.c
create mode 100644 arch/x86/kvm/sev.h
--
2.17.1
next reply other threads:[~2019-02-01 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 16:47 Singh, Brijesh [this message]
2019-02-01 16:47 ` [PATCH 1/2] KVM: SVM: move common struct definitions to header file Singh, Brijesh
2019-02-01 16:47 ` [PATCH 2/2] KVM: SVM: move the SEV specific function in a separate file Singh, Brijesh
2019-02-01 18:20 ` [PATCH 0/2] KVM: SVM: move the SEV command handling into " Sean Christopherson
2019-02-04 17:17 ` Singh, Brijesh
2019-03-28 14:08 ` Singh, Brijesh
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=20190201164654.3888-1-brijesh.singh@amd.com \
--to=brijesh.singh@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=bp@alien8.de \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--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®