Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp19130pxf; Wed, 24 Mar 2021 19:30:37 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzPipK8Uvn7jHIbNJUP68qDRRBcOzKKlj9m9NiYwjUc/a1imE1LIpvhmQaBIzH9tmt/2qMX X-Received: by 2002:a17:907:211b:: with SMTP id qn27mr6846395ejb.203.1616639437363; Wed, 24 Mar 2021 19:30:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616639437; cv=none; d=google.com; s=arc-20160816; b=CQ28eA/Xdw4bo/uQzTrMoXPdwNl/5O8TmMjLgha5LFaTWgJQfqy7gQ2bkFFiY9WNKx wFIvGZY3rhRwZWxkAP1YiKSg9Ranf7UAOHsj2zaYOWV/GLWfiloU+raQzQdxOG5V2V4n 8/3EuiQoF1Psicit7CyDrUnrKVbA9lrmdwcaGb1rvpXTpAqG5Yk089EvqjbHmIjvV9Ux tEiD22VTsRFw9NKKdOtu6kBrQPo97RAxLucDe/ltfDQEXdAWPmLFcOlpSrS4qZyJOFiB vtVFPajCxn6u6pjT3CeybYZ/qXH/QiN73hJKENa4t4R6TgNiArw/aVjkb0MVhGwrN/y/ 5shg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=MUPB/DOGr7AitSZ9XoZZdv0x3XFY/RHpBMnqRyxMpTo=; b=Zvcjjwi+1iItUMvZmsBRF/mVS12ELnspUSHwEoOg1RR4ydmxx5JKBACwSihWhkKUlG Ix4k8aRc0hGXuRMnyQ+4JIqGQJF4rv7xMnz8rHvxYVttmiTOh0murIUgTfhy+efhJFSa h4vpdoH/bbObhendav4CKciVDTpxYD5hQ3LyoA/7g6i1FAZd41tBx7T29luanIOHTNpr malhpy4SXNV35E6d25ahPtnlFFhP8LNyMYsnlmkCYZK9332qdOBrfAfxHIqk6EjsrDNR Woyx+skJdo4mxcyQZlMy+GS0RO1HBS51lR/6nFiu3+PiP/dM1oJEcGo5w1qv8gj0vtX/ 1hiA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f24si2998392ejz.234.2021.03.24.19.30.14; Wed, 24 Mar 2021 19:30:37 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236252AbhCXJjp (ORCPT + 99 others); Wed, 24 Mar 2021 05:39:45 -0400 Received: from foss.arm.com ([217.140.110.172]:59162 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236168AbhCXJjR (ORCPT ); Wed, 24 Mar 2021 05:39:17 -0400 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 09E301FB; Wed, 24 Mar 2021 02:39:17 -0700 (PDT) Received: from [10.57.55.187] (unknown [10.57.55.187]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 39BA73F718; Wed, 24 Mar 2021 02:39:15 -0700 (PDT) Subject: Re: [PATCH v5 05/19] arm64: Add support for trace synchronization barrier To: Catalin Marinas , Mathieu Poirier , Marc Zyngier Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, coresight@lists.linaro.org, mathieu.poirier@linaro.org, mike.leach@linaro.org, leo.yan@linaro.org, anshuman.khandual@arm.com, maz@kernel.org, Will Deacon References: <20210323120647.454211-1-suzuki.poulose@arm.com> <20210323120647.454211-6-suzuki.poulose@arm.com> <20210323182142.GA16080@arm.com> From: Suzuki K Poulose Message-ID: <7675ab71-c2ff-91e0-5728-fcb216ac1e0d@arm.com> Date: Wed, 24 Mar 2021 09:39:13 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <20210323182142.GA16080@arm.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 23/03/2021 18:21, Catalin Marinas wrote: > Hi Suzuki? > > On Tue, Mar 23, 2021 at 12:06:33PM +0000, Suzuki K Poulose wrote: >> tsb csync synchronizes the trace operation of instructions. >> The instruction is a nop when FEAT_TRF is not implemented. >> >> Cc: Mathieu Poirier >> Cc: Mike Leach >> Cc: Catalin Marinas >> Cc: Will Deacon >> Signed-off-by: Suzuki K Poulose > > How do you plan to merge these patches? If they go via the coresight > tree: > Ideally all of this should go via the CoreSight tree to have the dependencies solved at one place. But there are some issues : If this makes to 5.13 queue for CoreSight, 1) CoreSight next is based on rc2 at the moment and we have fixes gone into rc3 and later, which this series will depend on. (We could move the next tree forward to a later rc to solve this). 2) There could be conflicts with the kvmarm tree for the KVM host changes (That has dependency on the TRBE definitions patch). If it doesn't make to 5.13 queue, it would be good to have this patch, the TRBE defintions and the KVM host patches queued for 5.13 (not sure if this is acceptable) and we could rebase the CoreSight changes on 5.13 and push it to next release. I am open for other suggestions. Marc, Mathieu, Thoughts ? > Acked-by: Catalin Marinas > Thanks Suzuki