From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: devel@linuxdriverproject.org, x86@kernel.org
Cc: linux-kernel@vger.kernel.org,
"K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Steven Rostedt <rostedt@goodmis.org>,
Jork Loeser <Jork.Loeser@microsoft.com>,
Simon Xiao <sixiao@microsoft.com>,
Andy Lutomirski <luto@kernel.org>
Subject: [PATCH v4 00/10] Hyper-V: praravirtualized remote TLB flushing and hypercall improvements
Date: Wed, 24 May 2017 14:03:55 +0200 [thread overview]
Message-ID: <20170524120405.19079-1-vkuznets@redhat.com> (raw)
Changes since v3:
- Force a stack frame in hv_do_hypercall()/hv_do_fast_hypercall8()
[Andy Lutomirski] (Patches 3,4). K. Y., I'm keeping your Acked-by and
Tested-by tags on these patches as I think the adjustment is minor.
I smoke tested both i586 and x86_64 builds and no issues were noticed.
There is a discussion if this need to go through char-misc or x86 tree. The
majority of the stuff in the series is Hyper-V related so char-misc looks
appropriate but Andy noticed that we're clashing with his PCID series so
it may make sense to have everything in x86.
Original descriptions:
Hyper-V supports hypercalls for doing local and remote TLB flushing and
gives its guests hints when using hypercall is preferred. While doing
hypercalls for local TLB flushes is probably not practical (and is not
being suggested by modern Hyper-V versions) remote TLB flush with a
hypercall brings significant improvement.
To test the series I wrote a special 'TLB trasher': on a 16 vCPU guest I
was creating 32 threads which were doing 100000 mmap/munmaps each on some
big file. Here are the results:
Before:
# time ./pthread_mmap ./randfile
real 3m33.118s
user 0m3.698s
sys 3m16.624s
After:
# time ./pthread_mmap ./randfile
real 2m19.920s
user 0m2.662s
sys 2m9.948s
This series brings a number of small improvements along the way: fast
hypercall implementation and using it for event signaling, rep hypercalls
implementation, hyperv tracing subsystem (which only traces the newly added
remote TLB flush for now).
Vitaly Kuznetsov (10):
x86/hyper-v: include hyperv/ only when CONFIG_HYPERV is set
x86/hyper-v: stash the max number of virtual/logical processor
x86/hyper-v: make hv_do_hypercall() inline
x86/hyper-v: fast hypercall implementation
hyper-v: use fast hypercall for HVCALL_SIGNAL_EVENT
x86/hyper-v: implement rep hypercalls
hyper-v: globalize vp_index
x86/hyper-v: use hypercall for remote TLB flush
x86/hyper-v: support extended CPU ranges for TLB flush hypercalls
tracing/hyper-v: trace hyperv_mmu_flush_tlb_others()
MAINTAINERS | 1 +
arch/x86/Kbuild | 4 +-
arch/x86/hyperv/Makefile | 2 +-
arch/x86/hyperv/hv_init.c | 90 ++++++------
arch/x86/hyperv/mmu.c | 270 ++++++++++++++++++++++++++++++++++++
arch/x86/include/asm/mshyperv.h | 152 +++++++++++++++++++-
arch/x86/include/asm/trace/hyperv.h | 34 +++++
arch/x86/include/uapi/asm/hyperv.h | 36 +++++
arch/x86/kernel/cpu/mshyperv.c | 14 +-
drivers/hv/channel_mgmt.c | 22 ++-
drivers/hv/connection.c | 8 +-
drivers/hv/hv.c | 9 --
drivers/hv/hyperv_vmbus.h | 11 --
drivers/hv/vmbus_drv.c | 17 ---
drivers/pci/host/pci-hyperv.c | 4 +-
include/linux/hyperv.h | 21 ++-
16 files changed, 571 insertions(+), 124 deletions(-)
create mode 100644 arch/x86/hyperv/mmu.c
create mode 100644 arch/x86/include/asm/trace/hyperv.h
--
2.9.4
next reply other threads:[~2017-05-24 12:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 12:03 Vitaly Kuznetsov [this message]
2017-05-24 12:03 ` [PATCH v4 01/10] x86/hyper-v: include hyperv/ only when CONFIG_HYPERV is set Vitaly Kuznetsov
2017-05-24 12:03 ` [PATCH v4 02/10] x86/hyper-v: stash the max number of virtual/logical processor Vitaly Kuznetsov
2017-05-27 17:43 ` Andy Shevchenko
2017-06-05 15:24 ` Steven Rostedt
2017-06-05 15:30 ` Stephen Hemminger
2017-05-24 12:03 ` [PATCH v4 03/10] x86/hyper-v: make hv_do_hypercall() inline Vitaly Kuznetsov
2017-05-27 17:46 ` Andy Shevchenko
2017-05-24 12:03 ` [PATCH v4 04/10] x86/hyper-v: fast hypercall implementation Vitaly Kuznetsov
2017-05-27 17:49 ` Andy Shevchenko
2017-05-24 12:04 ` [PATCH v4 05/10] hyper-v: use fast hypercall for HVCALL_SIGNAL_EVENT Vitaly Kuznetsov
2017-05-27 17:50 ` Andy Shevchenko
2017-05-24 12:04 ` [PATCH v4 06/10] x86/hyper-v: implement rep hypercalls Vitaly Kuznetsov
2017-05-24 12:04 ` [PATCH v4 07/10] hyper-v: globalize vp_index Vitaly Kuznetsov
2017-05-24 12:04 ` [PATCH v4 08/10] x86/hyper-v: use hypercall for remote TLB flush Vitaly Kuznetsov
2017-05-24 12:04 ` [PATCH v4 09/10] x86/hyper-v: support extended CPU ranges for TLB flush hypercalls Vitaly Kuznetsov
2017-05-27 18:13 ` Andy Shevchenko
2017-05-24 12:04 ` [PATCH v4 10/10] tracing/hyper-v: trace hyperv_mmu_flush_tlb_others() Vitaly Kuznetsov
2017-06-05 15:50 ` Steven Rostedt
2017-06-05 16:19 ` Vitaly Kuznetsov
2017-06-07 13:52 ` Steven Rostedt
2017-06-07 14:03 ` Vitaly Kuznetsov
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=20170524120405.19079-1-vkuznets@redhat.com \
--to=vkuznets@redhat.com \
--cc=Jork.Loeser@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=sixiao@microsoft.com \
--cc=sthemmin@microsoft.com \
--cc=tglx@linutronix.de \
--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
Powered by JetHome