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 0F320C2BD09 for ; Wed, 10 Jul 2024 01:22:53 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id B356110E0B8; Wed, 10 Jul 2024 01:22:53 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.b="KAz+yFHi"; dkim-atps=neutral Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.12]) by gabe.freedesktop.org (Postfix) with ESMTPS id B299310E0B8 for ; Wed, 10 Jul 2024 01:22:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1720574573; x=1752110573; h=date:message-id:from:to:cc:subject:in-reply-to: references:mime-version; bh=yEsX/xHXaWFrKQosMYeurceKdcEw1kHQjiN8sP1t8Mw=; b=KAz+yFHi1U3FBahrxJ/JJBmWnKaefC8kCtE6Pv3sq0GeV8EBhpeNcKW8 WbpKRx3fSgLEhTW+FiSV7w08FSDzPA3FDwoXHlLRYBADKYzfNsFgH7tz5 fM82Ytbqj2geZzXj2BSuAHxKUs2M7/Xy5RQKNla6Lu2qGWXAizVWpKtWq 5TfyQ/+m6De7t9bwDMQO2W5SLKaU2Sl7hCnya7GyBfG8pBcwHV6D0fVjY tPG3m981C60XSY8jre1p/iPHX+tiwH2AR4NfM+QAv/j3worlt+Dvl1IjS rHA2SMfoC9k6ZtI44aCJJDVcp2FXoP/q+CRkPzy7LWF5iYM5DmI/KL1Gb A==; X-CSE-ConnectionGUID: BOznKFRrRwO38+sOK19gFA== X-CSE-MsgGUID: QkVqZBOjSiqR6afuW+NuFw== X-IronPort-AV: E=McAfee;i="6700,10204,11128"; a="29268831" X-IronPort-AV: E=Sophos;i="6.09,196,1716274800"; d="scan'208";a="29268831" Received: from orviesa007.jf.intel.com ([10.64.159.147]) by orvoesa104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Jul 2024 18:22:53 -0700 X-CSE-ConnectionGUID: z6NAFWanTVCeC3T2G9FP0Q== X-CSE-MsgGUID: GGF7d2oWQBe86kerLkkLvA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.09,196,1716274800"; d="scan'208";a="48711639" Received: from jdicosol-mobl.amr.corp.intel.com (HELO adixit-arch.intel.com) ([10.125.0.11]) by orviesa007-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Jul 2024 18:22:52 -0700 Date: Tue, 09 Jul 2024 18:09:27 -0700 Message-ID: <87h6cyxdbs.wl-ashutosh.dixit@intel.com> From: "Dixit, Ashutosh" To: intel-xe@lists.freedesktop.org Cc: Lionel Landwerlin , Umesh Nerlige Ramappa , Robert Krzemien , Jose Souza Subject: Re: [PATCH] drm/xe/oa/uapi: Allow OA config's to have arbitrary names/id's In-Reply-To: <20240710011741.3589516-1-ashutosh.dixit@intel.com> References: <20240710011741.3589516-1-ashutosh.dixit@intel.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/29.4 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-BeenThere: intel-xe@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel Xe graphics driver List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-xe-bounces@lists.freedesktop.org Sender: "Intel-xe" On Tue, 09 Jul 2024 18:17:41 -0700, Ashutosh Dixit wrote: > > Added OA configs were previously identified by means of a uuid. Rather than > forcing userspace to use uuid, here we generalize this scheme to allow > userspace the flexibility to use whatever naming scheme (including uuid) > they may wish to use to identify and track OA config's. Names must still be > unique or will be rejected. To provide some additional context for the need for this patch: at present multiple UMD's can add OA configs. But these UMD's don't have a centralized place to manage OA config uuid's. Therefore, OA configs added by one UMD are incomprehensible to the other UMD (since they both use their own private uuid, even for the same OA config). So one solution to this problem is of course to have the UMD's coordinate and use global uuid's across all UMD's. If this is somehow not possible, originating OA config's do have another globally unique identifier, "metricset name" (such as RenderBasic, ComputeBasic, TestOA etc.). So if we allow UMD's to use this "metricset name" when adding OA configs to Xe KMD, UMD's will be able to identify an OA config added by a different UMD. So the "metricset name" can serve as a globally unique identifier for OA configs. This patch allows this second solution to be possible, without preventing the first solution. Thanks. -- Ashutosh