From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 8319B75809 for ; Fri, 17 Apr 2026 08:41:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.140.110.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776415283; cv=none; b=nzrglMB3K6k3rXQumpt4x4SLVZaYhcfiY6WVm07+/NNHfD49osSdQG3E37lYvCqHoD7Mk6+MwOVsENiu7e7/78J83lqHV6X2QXgrc3+J274Ic4As+vBXuz6SQ7+wHrt4ZlbX1nyOBEBF2icXnnVr+wcEhKnl0YnBUnwQ5FFvpP0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776415283; c=relaxed/simple; bh=AE9tGvDnku39vfxAUF/4mX5MIkxJb3p3tylUEbtf31E=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=eg38KTXN9j0RU/Yiyz1ccxNKuXww/RYFU69wYB9IgP7rW9iNFafhOz/xCzp4cO0Uzjxq7pwtXppiCVQ+05xhHwuqJH71d+41HCr3JPcaqCMouK24dMAh2tTXXL4Pb8UcsXTKOGC8NJ95OXAJ0WIZ72R095j1CINr5/fE/11rLlI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com; spf=pass smtp.mailfrom=arm.com; dkim=pass (1024-bit key) header.d=arm.com header.i=@arm.com header.b=oqqZ49dC; arc=none smtp.client-ip=217.140.110.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arm.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=arm.com header.i=@arm.com header.b="oqqZ49dC" Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 3882A1E7D; Fri, 17 Apr 2026 01:41:15 -0700 (PDT) Received: from localhost (e132581.arm.com [10.1.196.87]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 667673F641; Fri, 17 Apr 2026 01:41:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=arm.com; s=foss; t=1776415280; bh=AE9tGvDnku39vfxAUF/4mX5MIkxJb3p3tylUEbtf31E=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=oqqZ49dCyA2UnmFgbaQIh5ScjTi1wPbBSHQHRFYpY2xu7Ane3PVMjz+x3aMVxdJHw zaWLmbeH+Y1r9Vc7WMYlFbPLgJme/0Yrzgt6hmgXiyArjMc3E4zM/SxfhENJJJ7O+b oVxFtPI/+V6W1kKyKMqGEPU8lQAG/6grpzzuwuRQ= Date: Fri, 17 Apr 2026 09:41:18 +0100 From: Leo Yan To: Jie Gan Cc: Yeoreum Yun , coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, suzuki.poulose@arm.com, mike.leach@arm.com, james.clark@linaro.org, alexander.shishkin@linux.intel.com Subject: Re: [PATCH v5 06/12] coresight: etm4x: fix leaked trace id Message-ID: <20260417084118.GP356832@e132581.arm.com> References: <20260415165528.3369607-1-yeoreum.yun@arm.com> <20260415165528.3369607-7-yeoreum.yun@arm.com> <20260416165541.GN356832@e132581.arm.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Hi Jie, On Fri, Apr 17, 2026 at 09:01:17AM +0800, Jie Gan wrote: [...] > ... we still need support static trace ID allocation in parallel for > the dummy sources and we should not break this logic in future refactor. Just confirm what is the reason you need to use static trace ID for the dummy sources? I am wandering if we could use dev->devt as trace ID for dummy devices. Since the device's MAJOR number is non-zero and occupies the upper bits (see MINORBITS), it is naturally separated from the hardware trace ID range. If so, we even don't need to bother ID alloc/release. Thanks, Leo