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 Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id D80B9C43334 for ; Fri, 22 Jul 2022 12:07:30 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id E8BF790CDC; Fri, 22 Jul 2022 12:07:29 +0000 (UTC) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by gabe.freedesktop.org (Postfix) with ESMTPS id A591F908CD; Fri, 22 Jul 2022 12:07:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1658491648; x=1690027648; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=7csoj11Ngte1VsV9j1GfxOWnYiT9h3Gecw0LVntMgDk=; b=mb3+C2IqsNWuRPn4vI7jYCGCjcYmZtyW3jtLMKA9qYd5YBtdwD3ltQPC P3DHdyjimB9VNMPpJMfv852D4UB5qfOphez5zfZZWhrEQVESyV9pOa1/y gOEdTZ2JaEJ9dVdoPoCB20mQgRapXQ4gwE9KaIzw6IRO2vLW8M2LmV/zE eburlZkIcp9Z6wUwUW9mmTUQLNXUpUbAGXufDWSCfd8gqOdF8D7USuakd Ol6eQgfNH2fNhPhGTJiidZ9YdiXXjFSb8Nsm9fp+JED1L+ytke/svgcRj mK9++c14UBdzVU0sxWDZ00of2d1Wdu7WhNB1xUsczhBJLyTh+k2h470hQ A==; X-IronPort-AV: E=McAfee;i="6400,9594,10415"; a="288055103" X-IronPort-AV: E=Sophos;i="5.93,185,1654585200"; d="scan'208";a="288055103" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Jul 2022 05:07:28 -0700 X-IronPort-AV: E=Sophos;i="5.93,185,1654585200"; d="scan'208";a="657191932" Received: from dstoll-mobl.ger.corp.intel.com (HELO intel.com) ([10.252.44.132]) by fmsmga008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Jul 2022 05:07:22 -0700 Date: Fri, 22 Jul 2022 14:07:22 +0200 From: Andi Shyti To: Mauro Carvalho Chehab Subject: Re: [PATCH v2 08/21] drm/i915/gt: Move TLB invalidation to its own file Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Jason Ekstrand , David Airlie , dri-devel@lists.freedesktop.org, Daniele Ceraolo Spurio , Fei Yang , Chris Wilson , Matthew Auld , Andi Shyti , Tomas Winkler , Thomas =?iso-8859-15?Q?Hellstr=F6m?= , Casey Bowman , Lucas De Marchi , intel-gfx@lists.freedesktop.org, Rodrigo Vivi , Tvrtko Ursulin , linux-kernel@vger.kernel.org, Prathap Kumar Valsan Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" Hi Mauro, On Thu, Jul 14, 2022 at 01:06:13PM +0100, Mauro Carvalho Chehab wrote: > From: Chris Wilson > > Prepare for supporting more TLB invalidation scenarios by moving > the current MMIO invalidation to its own file. > > Signed-off-by: Chris Wilson > Cc: Fei Yang > Signed-off-by: Mauro Carvalho Chehab Just a copy paste, I checked line by line and it looked all correct: Reviewed-by: Andi Shyti Thanks, Andi