public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: pbonzini@redhat.com, Hao Peng <flyingpenghao@gmail.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] KVM: X86: Reduce size of kvm_vcpu_arch structure when CONFIG_KVM_XEN=n
Date: Wed, 4 Oct 2023 12:28:28 -0700	[thread overview]
Message-ID: <ZR283JqDK3vLEt5A@google.com> (raw)
In-Reply-To: <169592099261.2962597.3938666115023271118.b4-ty@google.com>

On Thu, Sep 28, 2023, Sean Christopherson wrote:
> On Tue, 05 Sep 2023 09:07:09 +0800, Hao Peng wrote:
> > When CONFIG_KVM_XEN=n, the size of kvm_vcpu_arch can be reduced
> > from 5100+ to 4400+ by adding macro control.
> 
> Applied to kvm-x86 misc.  Please fix whatever mail client you're using to send
> patches, the patch was heavily whitespace damaged.  I fixed up this one because
> it was easy to fix and a straightforward patch.
> 
> [1/1] KVM: X86: Reduce size of kvm_vcpu_arch structure when CONFIG_KVM_XEN=n
>       https://github.com/kvm-x86/linux/commit/fd00e095a031

FYI, I've moved this to "kvm-x86 xen".  There are enough Xen patches coming in
that I didn't want to dump them all in "misc", and I also didn't want to have
one lone Xen patch in a different pull request.

[1/1] KVM: X86: Reduce size of kvm_vcpu_arch structure when CONFIG_KVM_XEN=n
      https://github.com/kvm-x86/linux/commit/ee11ab6bb04e

      reply	other threads:[~2023-10-04 19:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-05  1:07 [PATCH RESEND] KVM: X86: Reduce size of kvm_vcpu_arch structure when CONFIG_KVM_XEN=n Hao Peng
2023-09-29  2:21 ` Sean Christopherson
2023-10-04 19:28   ` Sean Christopherson [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=ZR283JqDK3vLEt5A@google.com \
    --to=seanjc@google.com \
    --cc=flyingpenghao@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    /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