All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <sean.j.christopherson@intel.com>
To: "Singh, Brijesh" <brijesh.singh@amd.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"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: Re: [PATCH 0/2] KVM: SVM: move the SEV command handling into a separate file
Date: Fri, 1 Feb 2019 10:20:40 -0800	[thread overview]
Message-ID: <20190201182040.GD12454@linux.intel.com> (raw)
In-Reply-To: <20190201164654.3888-1-brijesh.singh@amd.com>

On Fri, Feb 01, 2019 at 04:47:12PM +0000, Singh, Brijesh wrote:
> 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.

Any reason not to create arch/x86/kvm/svm/ before introducing sev.c? 

> 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
> 

  parent reply	other threads:[~2019-02-01 18:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-01 16:47 [PATCH 0/2] KVM: SVM: move the SEV command handling into a separate file Singh, Brijesh
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 ` Sean Christopherson [this message]
2019-02-04 17:17   ` [PATCH 0/2] KVM: SVM: move the SEV command handling into " 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=20190201182040.GD12454@linux.intel.com \
    --to=sean.j.christopherson@intel.com \
    --cc=Thomas.Lendacky@amd.com \
    --cc=bp@alien8.de \
    --cc=brijesh.singh@amd.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.