Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751337AbdFYRH0 (ORCPT ); Sun, 25 Jun 2017 13:07:26 -0400 Received: from a2nlsmtp01-03.prod.iad2.secureserver.net ([198.71.225.37]:33980 "EHLO a2nlsmtp01-03.prod.iad2.secureserver.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751140AbdFYRHY (ORCPT ); Sun, 25 Jun 2017 13:07:24 -0400 x-originating-ip: 107.180.71.197 From: kys@exchange.microsoft.com To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com, vkuznets@redhat.com, jasowang@redhat.com, leann.ogasawara@canonical.com, marcelo.cerri@canonical.com, sthemmin@microsoft.com Cc: "K. Y. Srinivasan" Subject: [PATCH 00/10] Hyper-V: paravirtualized remote TLB flushing and hypercall improvements Date: Sun, 25 Jun 2017 10:06:20 -0700 Message-Id: <1498410380-30955-1-git-send-email-kys@exchange.microsoft.com> X-Mailer: git-send-email 1.7.1 Reply-To: kys@microsoft.com X-CMAE-Envelope: MS4wfL8asURYhWUkHrWvyxr0zLSWyrSmUk/ir6XkDI4PH80CAW63GLQsVilPqGCs0k5Cy0PUBXVrO+MRj4sCb4UPDYvE4KD8xSYWC1dzTRs+r5QcmvwyOhFw C6Ef1/j816TYgX0YeQ23DwEe0SvfvILBayyz9GFN0t2qDISJtiLWFqB7GdCKmqZTozWhzZd2kq7bRPYj/1WL9SVdU66LkWpxxVEc0tAfRLRv/MZCSkBm7gZf ZEwy7HI+jG09CuNciX1WSQ6MguBaqwEMsOwhwlrR3VApgFlpEvOASkUexdbWaoTBgCBEksVMCgFxQL6Gvw60UmiLPlzcvv157NY3ottyoLcEIYP7aHFsGLd7 sK15nr/LDalod9M2GKj31ZHKXWOb+iS8Y9wPYnl8K5xWA0BAn9aM+U/+zkkYtJ0MDBCe6SEKXXjYF3paw5RSl1fKAjZ1Ai5RZoThlWyvJxUEeTOSL80dxx06 CgLDuZ2egOb03xl4yQISx/ZtqhQ8bAdOWpuRDm+NlLyhYBf6tTjRDveNYxkJZnNSW8gWTd+o1SblS60g Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2477 Lines: 63 From: K. Y. Srinivasan 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 | 2 +- arch/x86/hyperv/Makefile | 2 +- arch/x86/hyperv/hv_init.c | 90 +++++------- arch/x86/hyperv/mmu.c | 268 +++++++++++++++++++++++++++++++++++ arch/x86/include/asm/mshyperv.h | 149 +++++++++++++++++++- arch/x86/include/asm/trace/hyperv.h | 38 +++++ arch/x86/include/uapi/asm/hyperv.h | 17 +++ arch/x86/kernel/cpu/mshyperv.c | 13 ++- drivers/hv/channel_mgmt.c | 20 +-- drivers/hv/connection.c | 7 +- drivers/hv/hv.c | 9 -- drivers/hv/hyperv_vmbus.h | 11 -- drivers/hv/vmbus_drv.c | 17 --- drivers/pci/host/pci-hyperv.c | 10 +- include/linux/hyperv.h | 17 +-- 16 files changed, 540 insertions(+), 131 deletions(-) create mode 100644 arch/x86/hyperv/mmu.c create mode 100644 arch/x86/include/asm/trace/hyperv.h