From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965407AbeALXM2 (ORCPT + 1 other); Fri, 12 Jan 2018 18:12:28 -0500 Received: from mail-io0-f196.google.com ([209.85.223.196]:34905 "EHLO mail-io0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965260AbeALXM1 (ORCPT ); Fri, 12 Jan 2018 18:12:27 -0500 X-Google-Smtp-Source: ACJfBotw54vVj0wkPC9atrl0eTScDy8Djs9/tcMb1ht5tlOeukZRUjkGLvqpUB2IOqnc9gesdyucAQ== From: Mathieu Poirier To: acme@kernel.org Cc: peterz@infradead.org, mingo@redhat.com, alexander.shishkin@linux.intel.com, jolsa@redhat.com, namhyung@kernel.org, yao.jin@linux.intel.com, linux-kernel@vger.kernel.org Subject: [PATCH 0/1] perf util: Do not reuse target->per_thread flag Date: Fri, 12 Jan 2018 16:12:22 -0700 Message-Id: <1515798743-2541-1-git-send-email-mathieu.poirier@linaro.org> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: Hi Arnaldo, Here is another stab at addressing the side effect introduced by commit ("73c0ca1eee3d perf thread_map: Enumerate all threads from /proc"). I have decided to add another variable to struct target, which keep things simple and doesn't touch the core. Another solution could have been to make target->per_thread an enumaration with values PER_THREAD and ALL_THREAD, something that could be switched on in function thread_map__new_str(). I opted for the first option as it makes the code easier to understand. Let me know what you prefer or get back to me with a better solution if you see one. Thanks, Mathieu Mathieu Poirier (1): perf util: Do not reuse target->per_thread flag tools/perf/builtin-stat.c | 2 +- tools/perf/util/evlist.c | 2 +- tools/perf/util/target.h | 1 + tools/perf/util/thread_map.c | 4 ++-- tools/perf/util/thread_map.h | 2 +- 5 files changed, 6 insertions(+), 5 deletions(-) -- 2.7.4