From: Paolo Bonzini <pbonzini@redhat.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>,
Siddharth Chandrasekaran <sidcha@amazon.de>
Cc: Alexander Graf <graf@amazon.com>,
Evgeny Iakovlev <eyakovl@amazon.de>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sean Christopherson <seanjc@google.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 3/4] KVM: x86: kvm_hv_flush_tlb use inputs from XMM registers
Date: Thu, 8 Apr 2021 14:37:45 +0200 [thread overview]
Message-ID: <01fc0ac9-f159-d3df-6c8c-8f8122fe31ea@redhat.com> (raw)
In-Reply-To: <87eefl7zp4.fsf@vitty.brq.redhat.com>
On 08/04/21 14:01, Vitaly Kuznetsov wrote:
>
> Also, we can probably defer kvm_hv_hypercall_read_xmm() until we know
> how many regs we actually need to not read them all (we will always
> need xmm[0] I guess so we can as well read it here).
The cost is get/put FPU, so I think there's not much to gain from that.
Paolo
next prev parent reply other threads:[~2021-04-08 12:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210407211954.32755-1-sidcha@amazon.de>
2021-04-07 21:19 ` [PATCH 1/4] KVM: x86: Move FPU register accessors into fpu.h Siddharth Chandrasekaran
2021-04-07 21:19 ` [PATCH 2/4] KVM: hyper-v: Collect hypercall params into struct Siddharth Chandrasekaran
2021-04-07 21:19 ` [PATCH 3/4] KVM: x86: kvm_hv_flush_tlb use inputs from XMM registers Siddharth Chandrasekaran
2021-04-08 12:01 ` Vitaly Kuznetsov
2021-04-08 12:37 ` Paolo Bonzini [this message]
2021-04-08 12:52 ` Vitaly Kuznetsov
2021-04-07 21:19 ` [PATCH 4/4] KVM: hyper-v: Advertise support for fast XMM hypercalls Siddharth Chandrasekaran
2021-04-08 12:05 ` Vitaly Kuznetsov
2021-04-08 14:20 ` Siddharth Chandrasekaran
2021-04-08 14:44 ` Vitaly Kuznetsov
2021-04-08 15:52 ` Siddharth Chandrasekaran
2021-04-09 7:38 ` Vitaly Kuznetsov
2021-04-09 7:55 ` Siddharth Chandrasekaran
2021-04-12 8:11 ` Siddharth Chandrasekaran
2021-04-12 11:29 ` Vitaly Kuznetsov
2021-04-08 15:44 ` Wei Liu
2021-04-08 15:56 ` Siddharth Chandrasekaran
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=01fc0ac9-f159-d3df-6c8c-8f8122fe31ea@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=eyakovl@amazon.de \
--cc=graf@amazon.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=seanjc@google.com \
--cc=sidcha@amazon.de \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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.