All of lore.kernel.org
 help / color / mirror / Atom feed
From: Uros Bizjak <ubizjak@gmail.com>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] KVM/nVMX: Use __vmx_vcpu_run in nested_vmx_check_vmentry_hw
Date: Thu, 17 Dec 2020 19:12:50 +0100	[thread overview]
Message-ID: <CAFULd4YXPzOqL3Dc-OzoQ_quPZr--Q1t7hKVLsHPXKxFw9byPw@mail.gmail.com> (raw)
In-Reply-To: <X9udlkYvuaMme5pj@google.com>

On Thu, Dec 17, 2020 at 7:04 PM Sean Christopherson <seanjc@google.com> wrote:
>
> For future patches, please Cc LKML (in additional to KVM) so that the automatic
> archiving and patchwork stuff kicks in.  Thanks!
>
> On Wed, Dec 16, 2020, Uros Bizjak wrote:
> > Ping.  This patch didn't receive any feedback.
> >
> > On Thu, Oct 29, 2020 at 2:41 PM Uros Bizjak <ubizjak@gmail.com> wrote:
> > >
> > > Replace inline assembly in nested_vmx_check_vmentry_hw
> > > with a call to __vmx_vcpu_run.  The function is not
> > > performance critical, so (double) GPR save/restore
> > > in __vmx_vcpu_run can be tolerated, as far as performance
> > > effects are concerned.
> > >
> > > Cc: Paolo Bonzini <pbonzini@redhat.com>
> > > Cc: Sean Christopherson <sean.j.christopherson@intel.com>
> > > Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
> > > ---
>
> vmx_vmenter() in vmx/vmenter.S can and should now use SYM_FUNC_START_LOCAL
> instead of SYM_FUNC_LOCAL.  Other than that nit:
>
> Reviewed-and-tested-by: Sean Christopherson <seanjc@google.com>

Thanks!

I'll prepare a v2 (and added LKML, as you suggested).

Uros.

  reply	other threads:[~2020-12-17 18:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 13:41 [PATCH] KVM/nVMX: Use __vmx_vcpu_run in nested_vmx_check_vmentry_hw Uros Bizjak
2020-12-16  9:24 ` Uros Bizjak
2020-12-16 20:15   ` Krish Sadhukhan
2020-12-16 21:05     ` Sean Christopherson
2020-12-17 18:04   ` Sean Christopherson
2020-12-17 18:12     ` Uros Bizjak [this message]
2020-12-17 18:44 Uros Bizjak
2020-12-18  9:52 ` Paolo Bonzini

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=CAFULd4YXPzOqL3Dc-OzoQ_quPZr--Q1t7hKVLsHPXKxFw9byPw@mail.gmail.com \
    --to=ubizjak@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.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 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.