Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp245690ybd; Tue, 25 Jun 2019 20:39:00 -0700 (PDT) X-Google-Smtp-Source: APXvYqwd/aCagKTaiPvCBE1/NDsbYATwa8cDGbBQUQX4GZj9qEA0W64plel9f/gK69XL3DHSWfpj X-Received: by 2002:a17:90a:dd42:: with SMTP id u2mr1778694pjv.118.1561520340547; Tue, 25 Jun 2019 20:39:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561520340; cv=none; d=google.com; s=arc-20160816; b=vygex3AWSpTBXjdEjEy+fjqiNEHNFaLvBWlY3nn6x50vILwq86cjdZAzLkU4Yj6+Li SPqVcA0PDakPT8ElMkribAKkzUxicsidy3ycVEA7GjdRZQ3JPN/maHXKPlbst6cSYAQc fvbcclqRCJRI02o6D7FdKulVoKpcAe4nFS4fWl3gdPns6NXqT5YtxrOoHakbK2YjQfCH rLPuwAcZkiNbz2tyXucl5DZZe/drh4lLg8iwljC1fYFY3TCS+Ty96J4PLSie+I4hTjzz I5s7AAbaRYO6A9oudA/tcqnFmrORnII0uZx+8ZB5xQ3aWsJGfYiO9uRyNTUMkyfwoPHI Px4A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=JmzGPKsmUvSdNsSmIymUCFxAhA+cTqqTboCcY+e/GPI=; b=FfSOxzo+e3ySw48wh1f3zUqqk/8W/ksNp2Lkfbop/q13I2973wDEn9LpCm9pvUOa3B Z5nMWOA2iksY5EX5PZKlAkGXzJJOFitynakAtcgwGe9XWfDXfInGFn7P2Q7eeEZG/4Se T4I7BzcA1Lywa5VgY1uK1WUKjX87+1dWCr8pXLVA5aRUYfghpcB/aGyZE/XX6KeYH4ID 8hHxUgiX55Dz9+IYRNadZ39IHPjCK73U4AWLe8CgfsRKRjfz2LMYYlMwB1HmVf4V9wfS etE8OaKyRMwOIZ8AaS9JryhTJDgg6VDKfcMEFZH8OxQUsvZH/2OyOekjH4veFqrr6vwo ESbQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=mpIGug1B; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u33si14688437pgn.253.2019.06.25.20.38.44; Tue, 25 Jun 2019 20:39:00 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=mpIGug1B; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726686AbfFZDhM (ORCPT + 99 others); Tue, 25 Jun 2019 23:37:12 -0400 Received: from mail.kernel.org ([198.145.29.99]:48354 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726077AbfFZDhM (ORCPT ); Tue, 25 Jun 2019 23:37:12 -0400 Received: from mail-wr1-f51.google.com (mail-wr1-f51.google.com [209.85.221.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 4D71420659 for ; Wed, 26 Jun 2019 03:37:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1561520231; bh=JmzGPKsmUvSdNsSmIymUCFxAhA+cTqqTboCcY+e/GPI=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=mpIGug1BN7TkavcEanSgy9S5TtgTAZM159v3f/R0RGk2ktaFcZBiwXCLs/azsmbLf uUPFAtrSsYkESs/Ex05eq88JFcXbg2ESx8nqbaF8XaupoKVIi7fl+KcUqLwW38K/ma gTC6bPVOCj3EOyALXyVKo6/zCvdWEcp4HhF6RByI= Received: by mail-wr1-f51.google.com with SMTP id f9so856395wre.12 for ; Tue, 25 Jun 2019 20:37:11 -0700 (PDT) X-Gm-Message-State: APjAAAXwDQ7OgcRhF6zt215anGHocojlqFUN2xc7tffxWjc4nbjAz/io ttmbJMugtyc0jPd9Aju4GQeA29MDqC8FALJ/nWjcjw== X-Received: by 2002:adf:f28a:: with SMTP id k10mr1277832wro.343.1561520229959; Tue, 25 Jun 2019 20:37:09 -0700 (PDT) MIME-Version: 1.0 References: <20190613064813.8102-1-namit@vmware.com> <20190613064813.8102-5-namit@vmware.com> In-Reply-To: <20190613064813.8102-5-namit@vmware.com> From: Andy Lutomirski Date: Tue, 25 Jun 2019 20:36:59 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 4/9] x86/mm/tlb: Flush remote and local TLBs concurrently To: Nadav Amit Cc: Peter Zijlstra , Andy Lutomirski , LKML , Ingo Molnar , Borislav Petkov , X86 ML , Thomas Gleixner , Dave Hansen , "K. Y. Srinivasan" , Haiyang Zhang , Stephen Hemminger , Sasha Levin , Juergen Gross , Paolo Bonzini , Boris Ostrovsky , linux-hyperv@vger.kernel.org, Linux Virtualization , kvm list , xen-devel Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 12, 2019 at 11:49 PM Nadav Amit wrote: > > To improve TLB shootdown performance, flush the remote and local TLBs > concurrently. Introduce flush_tlb_multi() that does so. The current > flush_tlb_others() interface is kept, since paravirtual interfaces need > to be adapted first before it can be removed. This is left for future > work. In such PV environments, TLB flushes are not performed, at this > time, concurrently. Would it be straightforward to have a default PV flush_tlb_multi() that uses flush_tlb_others() under the hood?