From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 79E5DC32751 for ; Wed, 31 Jul 2019 23:09:58 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id A8B8920657 for ; Wed, 31 Jul 2019 23:09:57 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="H7B8fYCB" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org A8B8920657 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 45zTfC1H7LzDqnF for ; Thu, 1 Aug 2019 09:09:55 +1000 (AEST) Authentication-Results: lists.ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=gmail.com (client-ip=2607:f8b0:4864:20::441; helo=mail-pf1-x441.google.com; envelope-from=npiggin@gmail.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="H7B8fYCB"; dkim-atps=neutral Received: from mail-pf1-x441.google.com (mail-pf1-x441.google.com [IPv6:2607:f8b0:4864:20::441]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 45zTbf6z1xzDqmX for ; Thu, 1 Aug 2019 09:07:40 +1000 (AEST) Received: by mail-pf1-x441.google.com with SMTP id u14so32710702pfn.2 for ; Wed, 31 Jul 2019 16:07:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:subject:to:cc:references:in-reply-to:mime-version :user-agent:message-id:content-transfer-encoding; bh=5xkYYWFUJIGhYM2fFqk+xJx9QlaJV4qyP7MvDXs3VJM=; b=H7B8fYCBMlcSaq3TS6JFo6g6OuYJCB0xVAwCo3RnbdPMLxnz57bHxot5y8qLSjXSCT LbtZfFaFTldYeMipVcZ6E6TMg2H03ojXz6EocNmhL7y1bwzqGTKCpcQe11onclyt7AUu YbYCp9KQ/HbBCKpzv6wzA9TceVkR4jWbhOXUWFL+UhNXQzYTgDVZI1gCXZ7Sqzekp1p+ mw8DHrrsV/GtZQw/UKzQ/3bfmlYyVjk2ghlGyYQJZrAGqVnF2XKI21V1m+T6DsKOz0Je zYpZSq+z+d6bSXa+sd74Xx4MdGGXaCcFkK9wOUi+IyzOVN9UIo6Kwgg5ZDjGzCvECGIT 9Gpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:subject:to:cc:references:in-reply-to :mime-version:user-agent:message-id:content-transfer-encoding; bh=5xkYYWFUJIGhYM2fFqk+xJx9QlaJV4qyP7MvDXs3VJM=; b=DhwM1RQZlPfo5rJ8geV9SIPusXbT+qvU63ECLLo2aPhEF3k1hG2cThwGq16jaJ6OGD ey+5C9rp1Sn/FCwhnM1MrMIPBA5r6FbF87xN0bDs2gl2ACsM7uv/cjAlCG9JJiV23kw2 y2xsbCpqee56OeS2J0un3ftoojZSME97JGR19iZObArDIW9ycjXdlZMlzNa1PAuKOp2C u+Bnln3wscAlVsq0OGyD8t/utG0567iIrRM9UnzhJnwoVXZM331YOLYL2ZOGnhC6I5d+ eReNOUQxZIyEuR4NB+zpjKSQEMs0CaHYbT8epXB1OotniNZSmimDf3ENYAx2nZYHh+k3 289Q== X-Gm-Message-State: APjAAAW1TIUAL8TliDBEB0psK9m3PSQtmttdo5GqT1feSfL/1GWbpkdE yElN6QryaLeZSvgw8c6hDBY= X-Google-Smtp-Source: APXvYqxTtXhMznTnaW549CxpKCl6nL/8QkUHFO3fOBv1rVGdANcxuDKxOgtKIhoU2PxcraqK4+aSkg== X-Received: by 2002:a17:90a:fa07:: with SMTP id cm7mr5065190pjb.138.1564614456719; Wed, 31 Jul 2019 16:07:36 -0700 (PDT) Received: from localhost ([61.69.185.217]) by smtp.gmail.com with ESMTPSA id i3sm75438531pfo.138.2019.07.31.16.07.35 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Wed, 31 Jul 2019 16:07:36 -0700 (PDT) Date: Thu, 01 Aug 2019 09:05:51 +1000 From: Nicholas Piggin Subject: Re: [RFC PATCH] powerpc/64s/radix: introduce option to disable broadcast tlbie To: Christophe Leroy , linuxppc-dev@lists.ozlabs.org References: <20190731123203.6370-1-npiggin@gmail.com> <188d2d1d-a254-d00c-eee4-dd71e01b443f@c-s.fr> In-Reply-To: <188d2d1d-a254-d00c-eee4-dd71e01b443f@c-s.fr> MIME-Version: 1.0 User-Agent: astroid/0.15.0 (https://github.com/astroidmail/astroid) Message-Id: <1564613600.hm3hrx4s31.astroid@bobo.none> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "Aneesh Kumar K . V" , Paul Mackerras Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" Christophe Leroy's on July 31, 2019 11:56 pm: >=20 >=20 > Le 31/07/2019 =C3=A0 14:32, Nicholas Piggin a =C3=A9crit=C2=A0: >> This is an initial hack of a quick option to disable use of the tlbie >> instruction. This takes the simplest possible initial pass of just >> replacing low level tlbie functions with IPIs. This means it's not as >> performant as it could be if we spend some time optmizing it, but on >> the other hand having a 1:1 replacement of tlbie is simple and can be >> useful for comparisons so I think it's the right initial approach. >=20 > Can you explain why we want to optionnaly disable use of tlbie ? It's something we've wanted to have more control of for a while. One is for testing performance, especially on large systems it is not always best to use tlbie. For example if you have threaded apps that only run on a few CPUs (e.g., process * thread hybrid process model server). There is also concern about coherent accelerators may have high latency to respond to tlbie, which can block the resource for others. And we did have a hardware errata with early POWER9 it would have been nice to disable it until the kernel could be updated with the workaround. Thanks, Nick =