linux-hyperv.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Siddharth Chandrasekaran <sidcha@amazon.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "K. Y. Srinivasan" <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Stephen Hemminger <sthemmin@microsoft.com>,
	Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
	Sean Christopherson <seanjc@google.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	Wanpeng Li <wanpengli@tencent.com>,
	Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
	Siddharth Chandrasekaran <sidcha.dev@gmail.com>,
	Alexander Graf <graf@amazon.com>,
	Evgeny Iakovlev <eyakovl@amazon.de>,
	Liran Alon <liran@amazon.com>,
	Ioannis Aslanidis <iaslan@amazon.de>,
	<linux-hyperv@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<kvm@vger.kernel.org>
Subject: Re: [PATCH v4 0/4] Add support for XMM fast hypercalls
Date: Tue, 6 Jul 2021 17:15:36 +0200	[thread overview]
Message-ID: <20210706151535.GA28697@u366d62d47e3651.ant.amazon.com> (raw)
In-Reply-To: <f318fd42-6b98-1a82-f334-d05f4e6cb715@redhat.com>

On Tue, Jul 06, 2021 at 05:04:59PM +0200, Paolo Bonzini wrote:
> On 30/06/21 13:56, Siddharth Chandrasekaran wrote:
> > On Wed, May 26, 2021 at 10:56:07AM +0200, Siddharth Chandrasekaran wrote:
> > > Hyper-V supports the use of XMM registers to perform fast hypercalls.
> > > This allows guests to take advantage of the improved performance of the
> > > fast hypercall interface even though a hypercall may require more than
> > > (the current maximum of) two general purpose registers.
> > > 
> > > The XMM fast hypercall interface uses an additional six XMM registers
> > > (XMM0 to XMM5) to allow the caller to pass an input parameter block of
> > > up to 112 bytes. Hyper-V can also return data back to the guest in the
> > > remaining XMM registers that are not used by the current hypercall.
> > > 
> > > Although the Hyper-v TLFS mentions that a guest cannot use this feature
> > > unless the hypervisor advertises support for it, some hypercalls which
> > > we plan on upstreaming in future uses them anyway. This patchset adds
> > > necessary infrastructure for handling input/output via XMM registers and
> > > patches kvm_hv_flush_tlb() to use xmm input arguments.
> > 
> > Hi Paolo,
> > 
> > Are you expecting more reviews on these patches?
> 
> They are part of 5.14 already. :)

Ahh, I see them now. I was expecting them to show up in master - that was
the confusion.

Thanks! :)

~ Sid



Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879




  reply	other threads:[~2021-07-06 15:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26  8:56 [PATCH v4 0/4] Add support for XMM fast hypercalls Siddharth Chandrasekaran
2021-05-26  8:56 ` [PATCH v4 1/4] KVM: x86: Move FPU register accessors into fpu.h Siddharth Chandrasekaran
2021-05-26  8:56 ` [PATCH v4 2/4] KVM: hyper-v: Collect hypercall params into struct Siddharth Chandrasekaran
2021-05-26  8:56 ` [PATCH v4 3/4] KVM: x86: kvm_hv_flush_tlb use inputs from XMM registers Siddharth Chandrasekaran
2021-05-26  9:03 ` [PATCH v4 4/4] KVM: hyper-v: Advertise support for fast XMM hypercalls Siddharth Chandrasekaran
2021-06-30 11:56 ` [PATCH v4 0/4] Add support for XMM fast hypercalls Siddharth Chandrasekaran
2021-07-06 15:04   ` Paolo Bonzini
2021-07-06 15:15     ` Siddharth Chandrasekaran [this message]
2021-07-06 16:36       ` 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=20210706151535.GA28697@u366d62d47e3651.ant.amazon.com \
    --to=sidcha@amazon.de \
    --cc=bp@alien8.de \
    --cc=decui@microsoft.com \
    --cc=eyakovl@amazon.de \
    --cc=graf@amazon.com \
    --cc=haiyangz@microsoft.com \
    --cc=hpa@zytor.com \
    --cc=iaslan@amazon.de \
    --cc=jmattson@google.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liran@amazon.com \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=sidcha.dev@gmail.com \
    --cc=sthemmin@microsoft.com \
    --cc=tglx@linutronix.de \
    --cc=vkuznets@redhat.com \
    --cc=wanpengli@tencent.com \
    --cc=wei.liu@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).