Received: by 2002:a05:6358:e9c4:b0:b2:91dc:71ab with SMTP id hc4csp877618rwb; Thu, 4 Aug 2022 12:39:16 -0700 (PDT) X-Google-Smtp-Source: AA6agR7wl2srCYMJdpR8U2AlJZxp3mA2YA7t9Oku6RDjc169w8obGt8H0pZq+neU+NKtw7qxsbQ9 X-Received: by 2002:a17:907:272a:b0:72b:8cd9:9ddd with SMTP id d10-20020a170907272a00b0072b8cd99dddmr2480067ejl.299.1659641955875; Thu, 04 Aug 2022 12:39:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1659641955; cv=none; d=google.com; s=arc-20160816; b=WXgbiat0EtAj1K5DN4ldAkmYfzSBrG4UEhgvdyWwHtpagVgUgcmn3eK2C4zf2UT9YF o9S6WjV52fD8ht0EeH1mK65Tgkw8CbQYiCWtPOk+HqaSD0Iv0abRdez01YNKl8y31R7r uUI2iDZfHddp0qdOJOjclnilOsyARBFZPhrKrpt1AO6Qlko7o8DSEkInKAvKk8QZGyFk xXVyWutP3rilVzNeq95t7XqaXAMbb8y1l11U3YWgg8JEn10OWLx8qhXPbUe9VMyyaUrp TzKvHQA66pthPLD8F5ixJocz1aEzyxu/zD1ck08mi81PUuyjSqbfZw5PQkFojtPTzT4b qiRQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=9an68t6elSEcOxsuHOeSkwUdZXoYQKoxZyn8P9hztAI=; b=qoClroOizgE49M+AFpv24aJ99lA6c3MqAiSgtfhDdHJBMz06xrtA7boOTiWjE57EuQ SRaPccOCR/rxOs7q7bV/osgNQKO1KUyHWki6+hHba/bklipjCe9rthIYyX0gbhrt3y93 Btn6DJneclV8FWKxbUNyFzbdiH3Qo5hmUkx5c44NQuOMP1cBO5NKetgOjaO87Tnxh4WB N7phm+YbZnlq/X8/fM5dmmRX3Lk8pmDk3+wrIUFkIPSLk/+gi29xZAI6WeVBPWQdu3oY bOMfwJYEPXp+b4s4GO2D7cfStq0SrWLlSBlrtiT1jCyuiyj85Fcq6BJt4VHDMr7sKY3h juQg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@infradead.org header.s=bombadil.20210309 header.b=HCuiLBk7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hd40-20020a17090796a800b0072b97b3288dsi157165ejc.510.2022.08.04.12.38.49; Thu, 04 Aug 2022 12:39:15 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@infradead.org header.s=bombadil.20210309 header.b=HCuiLBk7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236858AbiHDTAj (ORCPT + 99 others); Thu, 4 Aug 2022 15:00:39 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50654 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229678AbiHDTAi (ORCPT ); Thu, 4 Aug 2022 15:00:38 -0400 Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:3::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 36C113138D; Thu, 4 Aug 2022 12:00:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=Content-Transfer-Encoding: Content-Type:In-Reply-To:From:References:Cc:To:Subject:MIME-Version:Date: Message-ID:Sender:Reply-To:Content-ID:Content-Description; bh=9an68t6elSEcOxsuHOeSkwUdZXoYQKoxZyn8P9hztAI=; b=HCuiLBk7YM6RDFcdi3JYetDCyB NDuwb/yZ2K8aMah3/uI8gMzJ60yAbY1qmiefbsrKvkQOp684ftVjAZfgJvbYPfl4w4odz1P7cUb78 ZR+Z92l79j+5neCTzVefLEU5klvKgrmI/vpjL/4t5yWoC9T/04YDoVj9n7KYjsO9vw6Dmzz/GH1XE 1F50Mbkp5HEs1cBSWW4ekedmFq/otFqGs4wWVoD06nhCnhs4Jv/lKPYZe2ysV4mK9OQ1QoQlNKy1D qs+3Was90u4oPEwk80aveBjRTM5e1UNpcUc4dlWGnmBoUPBuYQx/ozeAxit+qHLuH4OpYHtj9XO6y dQAaI0hQ==; Received: from [2601:1c0:6280:3f0::a6b3] by bombadil.infradead.org with esmtpsa (Exim 4.94.2 #2 (Red Hat Linux)) id 1oJg52-008PmV-0P; Thu, 04 Aug 2022 19:00:24 +0000 Message-ID: <0698c5a5-3bf2-daa4-e10e-2715f9b0d080@infradead.org> Date: Thu, 4 Aug 2022 12:00:22 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: [PATCH v3 3/3] drm/i915/gt: document TLB cache invalidation functions Content-Language: en-US To: Mauro Carvalho Chehab , Jonathan Corbet Cc: Niranjana Vishwanathapura , Andi Shyti , Tvrtko Ursulin , Chris Wilson , Daniel Vetter , David Airlie , Jani Nikula , Joonas Lahtinen , Maarten Lankhorst , Maxime Ripard , Rodrigo Vivi , Thomas Zimmermann , dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org References: From: Randy Dunlap In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Mauro, On 8/4/22 00:37, Mauro Carvalho Chehab wrote: > Add a description for the TLB cache invalidation algorithm and for > the related kAPI functions. > > Signed-off-by: Mauro Carvalho Chehab > --- > > To avoid mailbombing on a large number of people, only mailing lists were C/C on the cover. > See [PATCH v3 0/3] at: https://lore.kernel.org/all/cover.1659598090.git.mchehab@kernel.org/ > > Documentation/gpu/i915.rst | 7 ++ > drivers/gpu/drm/i915/gt/intel_tlb.c | 25 ++++++++ > drivers/gpu/drm/i915/gt/intel_tlb.h | 99 +++++++++++++++++++++++++++++ > 3 files changed, 131 insertions(+) > > diff --git a/drivers/gpu/drm/i915/gt/intel_tlb.c b/drivers/gpu/drm/i915/gt/intel_tlb.c > index af8cae979489..16b918ffe824 100644 > --- a/drivers/gpu/drm/i915/gt/intel_tlb.c > +++ b/drivers/gpu/drm/i915/gt/intel_tlb.c > @@ -145,6 +145,18 @@ static void mmio_invalidate_full(struct intel_gt *gt) > intel_uncore_forcewake_put_delayed(uncore, FORCEWAKE_ALL); > } > > +/** > + * intel_gt_invalidate_tlb_full - do full TLB cache invalidation > + * @gt: GT structure In multiple places (here and below) it would be nice to know what a GT structure is. I looked thru multiple C and header files yesterday and didn't find any comments about it. Just saying that @gt is a GT structure isn't very helpful, other than making kernel-doc shut up. > + * @seqno: sequence number > + * > + * Do a full TLB cache invalidation if the @seqno is bigger than the last > + * full TLB cache invalidation. > + * > + * Note: > + * The TLB cache invalidation logic depends on GEN-specific registers. > + * It currently supports MMIO-based TLB flush for GEN8 to GEN12. > + */ > void intel_gt_invalidate_tlb_full(struct intel_gt *gt, u32 seqno) > { > intel_wakeref_t wakeref; > @@ -171,12 +183,25 @@ void intel_gt_invalidate_tlb_full(struct intel_gt *gt, u32 seqno) > } > } > > +/** > + * intel_gt_init_tlb - initialize TLB-specific vars > + * @gt: GT structure > + * > + * TLB cache invalidation logic internally uses some resources that require > + * initialization. Should be called before doing any TLB cache invalidation. > + */ > void intel_gt_init_tlb(struct intel_gt *gt) > { > mutex_init(>->tlb.invalidate_lock); > seqcount_mutex_init(>->tlb.seqno, >->tlb.invalidate_lock); > } > > +/** > + * intel_gt_fini_tlb - free TLB-specific vars > + * @gt: GT structure > + * > + * Frees any resources needed by TLB cache invalidation logic. > + */ > void intel_gt_fini_tlb(struct intel_gt *gt) > { > mutex_destroy(>->tlb.invalidate_lock); > diff --git a/drivers/gpu/drm/i915/gt/intel_tlb.h b/drivers/gpu/drm/i915/gt/intel_tlb.h > index 46ce25bf5afe..2838c051f872 100644 > --- a/drivers/gpu/drm/i915/gt/intel_tlb.h > +++ b/drivers/gpu/drm/i915/gt/intel_tlb.h > @@ -11,16 +11,115 @@ > > #include "intel_gt_types.h" > > +/** > + * DOC: TLB cache invalidation logic > + * ... > + > void intel_gt_invalidate_tlb_full(struct intel_gt *gt, u32 seqno); > > void intel_gt_init_tlb(struct intel_gt *gt); > void intel_gt_fini_tlb(struct intel_gt *gt); > > +/** > + * intel_gt_tlb_seqno - Returns the current TLB invlidation sequence number > + * @gt: GT structure > + * > + * There's no need to lock while calling it, as seqprop_sequence is thread-safe > + */ > static inline u32 intel_gt_tlb_seqno(const struct intel_gt *gt) > { > return seqprop_sequence(>->tlb.seqno); > } > > +/** > + * intel_gt_next_invalidate_tlb_full - Returns the next TLB full invalidation > + * sequence number > + * @gt: GT structure > + * > + * There's no need to lock while calling it, as seqprop_sequence is thread-safe > + */ > static inline u32 intel_gt_next_invalidate_tlb_full(const struct intel_gt *gt) > { > return intel_gt_tlb_seqno(gt) | 1; thanks. -- ~Randy