Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1381622yba;
        Sat, 6 Apr 2019 10:43:22 -0700 (PDT)
X-Google-Smtp-Source: APXvYqx69NF4+TglwjO5f+FvEMdW5cFZvoMb6Ysua8IUXwNKpsOjRZ5oiEar4OZmuYQMgAImKekT
X-Received: by 2002:a63:5b4b:: with SMTP id l11mr18485602pgm.95.1554572602787;
        Sat, 06 Apr 2019 10:43:22 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1554572602; cv=none;
        d=google.com; s=arc-20160816;
        b=GBc4EOl2UIdHPHkcbTaISstkdBTkthYie09xEMxVIhLojZfLnWIqYyG+Wi1PH1gJng
         KPRHGBFDi6vya4SMGi0BWCgGFuqVrwG6KFubq2pUJvwlrx49gZ3ve66UnZFXMDxLUTF8
         Okt9YN5m96M+WCCKSChshuBZRT5u5uBsrxvz23cYXPUPRnsi/wFfWgqu300SnxiV/Qcz
         juXfaQ4Pt3SUhjgSL3eTTQ5zcWVC3M8/9atP8wJJBQSowqBhtucFWSGPhSF7gJFLkr7b
         z1wvZzaiT622MZABHLdfhpb6s6mOCE5ND3ATm578oMc5wjgLdH+OJzwJWAEbl+MmYDhY
         tPrg==
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;
        bh=WsLu237ZMm6t4oaB0C7WrpDI6rE2dRmv0yGKW/np6go=;
        b=iRyu29AvuTZRPtPt9d7N0supLd6KUBw+abj1bElVEw88E+lwujNzG8avocVvS1ccfv
         CRVaZj+s+ws+eSMA099oz+vSzLwyEt4/zfdryxA+CBzzYqmauO7Y7RV/FVvSi9XcBYuS
         v9A4LErhulnIBXmqK24ZP6qJanXsR3C/kTY4m7EboJf2/ERoEPneJaqP+jOAwLWzCPCO
         wU8517qO6IE4xRkjGPuhGeWEbvss3ghuCetcNEWKnAn1w1VnVEWbHjqnsCn/yYi5blSm
         +T5x6BV/KwToyNcfTc2G+3EP4btsZfXGW1t0JpqvULeJKZz1dRvGD/O3GKckTieH3jrg
         VVeg==
ARC-Authentication-Results: i=1; mx.google.com;
       dkim=pass header.i=@duncanthrax.net header.s=dkim header.b=GzlDuGFI;
       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
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67])
        by mx.google.com with ESMTP id q1si18509391pgh.396.2019.04.06.10.43.05;
        Sat, 06 Apr 2019 10:43: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=pass header.i=@duncanthrax.net header.s=dkim header.b=GzlDuGFI;
       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
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1726580AbfDFRm3 (ORCPT <rfc822;haroldgmz11@gmail.com>
        + 99 others); Sat, 6 Apr 2019 13:42:29 -0400
Received: from smtp.duncanthrax.net ([89.31.1.170]:40672 "EHLO
        smtp.duncanthrax.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1726531AbfDFRm3 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Sat, 6 Apr 2019 13:42:29 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
        d=duncanthrax.net; s=dkim; h=In-Reply-To:Content-Type:MIME-Version:References
        :Message-ID:Subject:Cc:To:From:Date;
        bh=WsLu237ZMm6t4oaB0C7WrpDI6rE2dRmv0yGKW/np6go=; b=GzlDuGFID6tsZ/+joc3/hz6lo2
        4drLVX5PI4CzxM5bZSBZ7h6vx2WuNbb9C7k6BquZg81XuBF3uxTA44L9Fvr3jDQ8DYsQFdoFzeHC4
        N6ECbYPun6nxQLbnjMIRm6w91CW5zmej9FX8a9r5y1+INV6Z/qb9zwM1LSX6Eg020GuY=;
Received: from [134.3.47.207] (helo=t470p.stackframe.org)
        by smtp.eurescom.eu with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
        (Exim 4.86_2)
        (envelope-from <svens@stackframe.org>)
        id 1hCpKj-0000l7-Tc; Sat, 06 Apr 2019 19:42:26 +0200
Date:   Sat, 6 Apr 2019 19:42:24 +0200
From:   Sven Schnelle <svens@stackframe.org>
To:     "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Cc:     linux-kernel@vger.kernel.org,
        Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
        "David S. Miller" <davem@davemloft.net>,
        Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH] kprobes: fix compilation when KPROBE_EVENTS is enabled
 without kretpobes
Message-ID: <20190406174224.GB5538@t470p.stackframe.org>
References: <20190406155543.15353-1-svens@stackframe.org>
 <1554570896.uirb80qggp.naveen@linux.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1554570896.uirb80qggp.naveen@linux.ibm.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Naveen,

On Sat, Apr 06, 2019 at 10:52:47PM +0530, Naveen N. Rao wrote:
> Sven Schnelle wrote:
> > While implementing kprobes on PA-RISC (without kretprobes) compilation
> > fails when CONFIG_KPROBE_EVENTS is enabled:
> 
> Thanks for working on that! Is there a specific reason kretprobes is not
> being enabled on parisc?

Reason is that i just started to add kprobes support to PA-RISC. I'm planning
doing kretprobes as a second step and have separate patches for kprobe and
kretprobe to keep things small.

Regards
Sven