Received: by 10.192.165.148 with SMTP id m20csp719481imm; Fri, 4 May 2018 05:28:22 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqVgwPUy+I4l72BftQAQbBFIMRl2PwTxIzp6twQu0ubRzBaK8cGV+WWy/wIwk9hozeXot5k X-Received: by 2002:a63:345:: with SMTP id 66-v6mr22229462pgd.98.1525436902632; Fri, 04 May 2018 05:28:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525436902; cv=none; d=google.com; s=arc-20160816; b=twaF1RmDg6W6TDXeZ6KPsdm31XNmPHKnQAlXFgoIT9O2urxlIvUYHPVgLK3oMK433e bpJ0ZV+BiLdSTU9GVl5mTxXY6exf/SGC8rtOW85Y8EtuB82E93ltmTNop4wfS9HeTxx+ 80RX7CSYf2aj3KU/FdDWfqAV5VqYZnmd1NbppP87PhUAcfsmE+Mmz0uh6Mv2/O+miO5K adFGyzEXVS9/CJ/ZTAt8Kqw0wtnLwiUkM0E54UKT8d/oxQNaEdkd/IjaQUdQX9AG1UnD NwlP2D5fi4NfssnEyrwzvBf+JxMP1nSUNlISr35EfRe2tqudnOeVs/TnnLh0Dl4Xm0Fa H0pg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:arc-authentication-results; bh=bg0zRws3bmwlUdbJMEiWwnBUG1Kpfw+8l7KAdhGWjm8=; b=P1NIitNkcLC2i/l05vNFptNv4W+3C0furF6RUlthfh9CCkSTWptk/mS+uorH/QVJSZ sJkZxENDnsDLKSkRumfn9HVADqMOvSHW/aSE1y+uBuibp/fvTTrYauochkmSxrOWeFGB ssZtBOAnKxIiszhkXrzGK2Zoz6TQ/x7CnhFX5GlDpS6+7LvK6vMc+Qps6/nuZsunXakO S8bO6bkOlmvNADLwNqsOBZ/e5xs3pjTZnUc2WJL8XA1qfK0vqH8bv0vDrbGFF6U/OD2C kDNT0BR+ukx4n1IWmZnb+gCUs38M6JcFaPZrEUX2tFgo7tRGfMXua/KcJORqO8zCjz6m thaA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=S9aHhC50; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t1-v6si16175096plb.90.2018.05.04.05.28.08; Fri, 04 May 2018 05:28:22 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=S9aHhC50; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751349AbeEDM14 (ORCPT + 99 others); Fri, 4 May 2018 08:27:56 -0400 Received: from mail-wm0-f65.google.com ([74.125.82.65]:53275 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751262AbeEDM1z (ORCPT ); Fri, 4 May 2018 08:27:55 -0400 Received: by mail-wm0-f65.google.com with SMTP id a67so3745547wmf.3 for ; Fri, 04 May 2018 05:27:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=bg0zRws3bmwlUdbJMEiWwnBUG1Kpfw+8l7KAdhGWjm8=; b=S9aHhC50r0ZoDfhdqwNcej25ok/IbuVWlScCHDYR8z05mY2BJY0Tu3IhbMq1S3S8P7 LhKQMAaqy8s0CVkHQJL37FZvg/COad6sWGg1M97KaZZP8v3IODetIqprhIxGysIzw850 WeC51w+bdYAdvunF0yZjRaFHQnBtjCPQDRZixdSFy139j9Gxl2quexw8JYq5mHxKsCIA iOewhNNn9GEeUyw58Gnmazv7Qoa2gBQP4VEWymThzMQKmq2d/RifCtK1DtIRDa73y8MI 72oVNKSK8yrFLPFeY7kDGdY8sTBd76rjDWunjEOdFcomZLlGd3ctxlrDx87b6wvSZWib 4Eng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=bg0zRws3bmwlUdbJMEiWwnBUG1Kpfw+8l7KAdhGWjm8=; b=RXUoa5VgYL78qhQmlI4WA3aq1pusz1rPIg/kwO4DHjSdiLCXq1aFECasFuDLSMbrlZ OjfiEGSrSmhV6dL4BRzhyxFvlqELVHflmxYVJTgn5Jq1OGkEsoOoTwtdEvuFolHkt5B8 KlzkeY/i7yCwClyEF6kukPR091L2Ansy4Z1XxsHc7IsC345bOLkw4bRiYf4kdLlOqvUY KzgOkyDvwinnf3Q5pDaUxG+2opwFehzReOOdDexOlP5qcwUiZUqz6TCVBIUAhlMJ6Hta C0kNmBPtt0n2BJ2gcR4PaU6o6dWQUvaaUG2b7U/7zHv7zmSNXHXpRtbiFikwxmRun7OU frLw== X-Gm-Message-State: ALQs6tDen8NBCYi3djCX/yinlIhaQdvSDZ0z89oYKbDJbYvh9lohBtTr vyIlHTJL6z0r9blFjKNhu9o= X-Received: by 10.28.225.86 with SMTP id y83mr11765204wmg.92.1525436874150; Fri, 04 May 2018 05:27:54 -0700 (PDT) Received: from rric.localdomain (x4e37fc4f.dyn.telefonica.de. [78.55.252.79]) by smtp.gmail.com with ESMTPSA id n143-v6sm2329581wmd.29.2018.05.04.05.27.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 04 May 2018 05:27:53 -0700 (PDT) Date: Fri, 4 May 2018 14:27:51 +0200 From: Robert Richter To: Matt Redfearn Cc: James Hogan , Ralf Baechle , linux-mips@linux-mips.org, Huacai Chen , linux-kernel@vger.kernel.org, Jiaxun Yang , Krzysztof Kozlowski , oprofile-list@lists.sf.net Subject: Re: [RFC PATCH] MIPS: Oprofile: Drop support Message-ID: <20180504122750.GE4493@rric.localdomain> References: <1524574554-7451-1-git-send-email-matt.redfearn@mips.com> <20180424130511.GB28813@saruman> <5e464a40-4e4d-dde4-b5b5-ceb637dc5f38@mips.com> <20180504093002.GC4493@rric.localdomain> <20180504102600.GD4493@rric.localdomain> <294858af-9164-f0c3-62d3-d6b643e89e09@mips.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <294858af-9164-f0c3-62d3-d6b643e89e09@mips.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04.05.18 12:03:12, Matt Redfearn wrote: > >As said, oprofile version 0.9.x is still available for cpus that do > >not support perf. What is the breakage? > > The breakage I originally set out to fix was the MT support in perf. > https://www.linux-mips.org/archives/linux-mips/2018-04/msg00259.html > > Since the perf code shares so much copied code from oprofile, those same > issues exist in oprofile and ought to be addressed. But as newer oprofile > userspace does not use the (MIPS) kernel oprofile code, then we could, > perhaps, just remove it (as per the RFC). That would break legacy tools > (0.9.x) though... Those support perf: (CPU_MIPS32 || CPU_MIPS64 || CPU_R10000 || CPU_SB1 || CPU_CAVIUM_OCTEON || CPU_XLP || CPU_LOONGSON3) Here is the total list of CPU_*: $ git grep -h config.CPU_ arch/mips/ | sort -u | wc -l 79 The comparisation might not be accurate, but at least gives a hint that there are many cpus not supporting perf. You would drop profiling support at al to them. If it is too hard to also fix the oprofile code (code duplication seems the main issue here), then it would be also ok to blacklist newer cpus to enable oprofile kernel code (where it is broken). -Robert