[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180622170625.30688-1-vkuznets@redhat.com>
Date: Fri, 22 Jun 2018 19:06:21 +0200
From: Vitaly Kuznetsov <vkuznets@...hat.com>
To: x86@...nel.org
Cc: devel@...uxdriverproject.org, linux-kernel@...r.kernel.org,
"K. Y. Srinivasan" <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Tianyu Lan <Tianyu.Lan@...rosoft.com>,
"Michael Kelley (EOSG)" <Michael.H.Kelley@...rosoft.com>
Subject: [PATCH 0/4] x86/hyper-v: optimize PV IPIs
When reviewing my "x86/hyper-v: use cheaper HVCALL_FLUSH_VIRTUAL_ADDRESS_
{LIST,SPACE} hypercalls when possible" patch Michael suggested to apply the
same idea to PV IPIs. Here we go!
Despite what Hyper-V TLFS says about HVCALL_SEND_IPI hypercall, it can
actually be 'fast' (passing parameters through registers). Use that too.
This series can collide with my "KVM: x86: hyperv: PV IPI support for
Windows guests" series as I rename ipi_arg_non_ex/ipi_arg_ex structures
there. Depending on which one gets in first we may need to do tiny
adjustments.
Vitaly Kuznetsov (4):
x86/hyper-v: implement hv_do_fast_hypercall16
x86/hyper-v: use 'fast' hypercall for HVCALL_SEND_IPI
x86/hyper-v: use cheaper HVCALL_SEND_IPI hypercall when possible
x86/hyper-v: trace PV IPI send
arch/x86/hyperv/hv_apic.c | 57 ++++++++++++++++++++-----------------
arch/x86/include/asm/mshyperv.h | 34 ++++++++++++++++++++++
arch/x86/include/asm/trace/hyperv.h | 15 ++++++++++
3 files changed, 80 insertions(+), 26 deletions(-)
--
2.14.4
Powered by blists - more mailing lists