From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+w=401wt.eu-S1753017AbXCaNPY@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753017AbXCaNPY (ORCPT <rfc822;w@1wt.eu>);
	Sat, 31 Mar 2007 09:15:24 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753011AbXCaNPY
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Sat, 31 Mar 2007 09:15:24 -0400
Received: from verein.lst.de ([213.95.11.210]:51243 "EHLO mail.lst.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1753000AbXCaNPX (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Sat, 31 Mar 2007 09:15:23 -0400
Date: Sat, 31 Mar 2007 15:15:22 +0200
From: Christoph Hellwig <hch@lst.de>
To: hskinnemoen@atmel.com, davem@davemloft.net
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: missing kretprobes support on avr32 and sparc64
Message-ID: <20070331131522.GA15148@lst.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
X-Spam-Score: -0.001 () BAYES_44
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

Currently all avr32 and sparc64 don't support kretprobes unlike all
other kprobes supporting architectures.  This is not nice from the
user interface point of view and from the ugly ifdefs point of view.
Is there a reason these ports can't support kretprobes or was this
simply an oversight / lazyness?