Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp1368372pxf; Fri, 9 Apr 2021 06:50:42 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwligndkh2uoYDG+kBKP8ImHvZ/vwwteQUBoXZ9eke5s1ANVGwli1LV9sCC1bbN6QDWMcp5 X-Received: by 2002:a05:6402:8c2:: with SMTP id d2mr17975768edz.4.1617976241962; Fri, 09 Apr 2021 06:50:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617976241; cv=none; d=google.com; s=arc-20160816; b=WLGR9K17TN3NTaOaMS4lf8wjMJ0q72NKnS9hOYqgEjDsrZWiZNnFHXiYTixeMYzrQc 2UJTiE+q9HtQl6yK6yeTkv/R+pppzrLgZqi6fvAY/8Nx/BPlkrYCN8X/Dk3JHECFOaeJ AEcZaaNIxkyOyG6aOv5JJ//8x50EwM4DlrKC1Zvej7WpyUrnJE39MPyKNthgQhPYTZAa pbo3XQ1cn9k8qEDh1eVls7yOwfkEkS9I3v3SWXl6je5pus2OuwDro5P3Itf5X00t9Lpn hY5jiET3AMxIhjFw4TbLRsxahT+WV81Yl64OY9JmVFpSMSr5UrBPRGojhyG+K6Wn5w8o rN5w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=cpTfXGFKyz1diVOzgdPAPH9E7hvu3BcDdZAa4ecGkbE=; b=PjyvgTWW56T5QVx5sZFr4shgKS8UzaFjCzacZ5nsJdSZ68Ioq5Rrd1r4WaIw0LKfQR kXHN7CIXxBxdeVt//iqBoeCQlKXkDOq6HfV5tBhvHWXkdn9WZFi3n5Pr/nkHwj/Fy/K7 inYfllQr1ZmOr20Z8hlSnQt5Q7tUrwP0bS1VQns3SZk4Omqii/6oiT2QDy3G/rYqdfpn I9RpgedYj3GDHEwWiFM5COGxQQMRHsIJ35FTlTZEJyKYQcE5gQQzT0kgeY/ftt123TV5 tg94d/33DRFF1kpLfKGDp2tqiR+bd9Ts3Pch5RwAsaHHig74uWj/OIY15MWXyxKA4OBN +1vg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=PROsX8E8; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id se21si603439ejb.176.2021.04.09.06.50.16; Fri, 09 Apr 2021 06:50:41 -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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=PROsX8E8; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232892AbhDINr2 (ORCPT + 99 others); Fri, 9 Apr 2021 09:47:28 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:32565 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231599AbhDINrX (ORCPT ); Fri, 9 Apr 2021 09:47:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1617976030; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=cpTfXGFKyz1diVOzgdPAPH9E7hvu3BcDdZAa4ecGkbE=; b=PROsX8E8fRvVtf8N5qknjMxZ+p+gT7LiSJn6bgNmLm67D5UlNFVoujDDza328v4L9SAeCu QdXGjDTlRGcWcI0mVEEh+JrcMo+mtLYJhQiURAe7dccPGWBtjQRjUztWVaj1gn4SUvzozG 1WMdYBj1j7zJEkt+l9lLhIV/RcIuUvs= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-375-9hNmXChQM3OTNXwc2RZD-g-1; Fri, 09 Apr 2021 09:47:08 -0400 X-MC-Unique: 9hNmXChQM3OTNXwc2RZD-g-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id ADB1A107ACCD; Fri, 9 Apr 2021 13:47:06 +0000 (UTC) Received: from krava (unknown [10.40.195.216]) by smtp.corp.redhat.com (Postfix) with SMTP id 812C85D9E3; Fri, 9 Apr 2021 13:47:04 +0000 (UTC) Date: Fri, 9 Apr 2021 15:47:03 +0200 From: Jiri Olsa To: Jin Yao Cc: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com, alexander.shishkin@linux.intel.com, Linux-kernel@vger.kernel.org, ak@linux.intel.com, kan.liang@intel.com, yao.jin@intel.com Subject: Re: [PATCH v3 12/27] perf parse-events: Support no alias assigned event inside hybrid PMU Message-ID: References: <20210329070046.8815-1-yao.jin@linux.intel.com> <20210329070046.8815-13-yao.jin@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210329070046.8815-13-yao.jin@linux.intel.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 29, 2021 at 03:00:31PM +0800, Jin Yao wrote: SNIP > + struct parse_events_state *parse_state) > { > struct perf_event_attr attr; > LIST_HEAD(config_terms); > @@ -521,7 +526,7 @@ int parse_events_add_cache(struct list_head *list, int *idx, > > i = parse_events__add_cache_hybrid(list, idx, &attr, > config_name ? : name, &config_terms, > - &hybrid); > + &hybrid, parse_state); > if (hybrid) > return i; > > @@ -1481,7 +1486,7 @@ int parse_events_add_pmu(struct parse_events_state *parse_state, > struct perf_pmu *pmu; > struct evsel *evsel; > struct parse_events_error *err = parse_state->error; > - bool use_uncore_alias; > + bool use_uncore_alias, found = false; > LIST_HEAD(config_terms); > > if (verbose > 1) { > @@ -1530,8 +1535,28 @@ int parse_events_add_pmu(struct parse_events_state *parse_state, > } > } > > - if (!parse_state->fake_pmu && perf_pmu__check_alias(pmu, head_config, &info)) > + if (!parse_state->fake_pmu && > + perf_pmu__check_alias(pmu, head_config, &info, &found)) { > return -EINVAL; > + } > + ok, let's not polute surronding functions and make strict check on what we want in here.. we are after following events: cpu_xxx/L1-dcache/ cpu_xxx/l1-d|/ ... right? so we are after events with single term in head_config that has name in: L1-dcache|l1-d|l1d|L1-data | L1-icache|l1-i|l1i|L1-instruction | LLC|L2 | dTLB|d-tlb|Data-TLB | iTLB|i-tlb|Instruction-TLB | branch|branches|bpu|btb|bpc | node I think that with such direct check the code will be more straight forward, also let's move it to parse-events-hybrid > + if (!parse_state->fake_pmu && head_config && !found && > + perf_pmu__is_hybrid(name)) { > + struct parse_events_term *term; > + int ret; > + > + list_for_each_entry(term, head_config, list) { > + if (!term->config) > + continue; > + > + ret = parse_events__with_hybrid_pmu(parse_state, > + term->config, > + name, &found, > + list); do we need to call the parsing again? could we just call parse_events__add_cache_hybrid? jirka > + if (found) > + return ret; > + } > + } > > if (verbose > 1) { > fprintf(stderr, "After aliases, add event pmu '%s' with '", > @@ -1605,6 +1630,15 @@ int parse_events_multi_pmu_add(struct parse_events_state *parse_state, > struct perf_pmu *pmu = NULL; > int ok = 0; > SNIP