Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933166AbbDJNH0 (ORCPT ); Fri, 10 Apr 2015 09:07:26 -0400 Received: from mx1.redhat.com ([209.132.183.28]:46533 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932556AbbDJNHQ (ORCPT ); Fri, 10 Apr 2015 09:07:16 -0400 From: Denys Vlasenko To: linux-kernel@vger.kernel.org Cc: Denys Vlasenko , Jiri Olsa , Peter Zijlstra , Paul Mackerras , Ingo Molnar , Arnaldo Carvalho de Melo , x86@kernel.org Subject: [PATCH 2/4] perf/x86_64: get_regs_user: Do report user_regs->cx while we are in syscall Date: Fri, 10 Apr 2015 15:06:57 +0200 Message-Id: <1428671219-29341-2-git-send-email-dvlasenk@redhat.com> In-Reply-To: <1428671219-29341-1-git-send-email-dvlasenk@redhat.com> References: <1428671219-29341-1-git-send-email-dvlasenk@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1266 Lines: 37 Yes, it is true that cx contains return address. It's not clear why we trash it. Stop doing that. Signed-off-by: Denys Vlasenko CC: Jiri Olsa CC: Peter Zijlstra CC: Paul Mackerras CC: Ingo Molnar CC: Arnaldo Carvalho de Melo CC: x86@kernel.org CC: linux-kernel@vger.kernel.org --- arch/x86/kernel/perf_regs.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/arch/x86/kernel/perf_regs.c b/arch/x86/kernel/perf_regs.c index 7ab198a..a8d4e48 100644 --- a/arch/x86/kernel/perf_regs.c +++ b/arch/x86/kernel/perf_regs.c @@ -177,8 +177,6 @@ void perf_get_regs_user(struct perf_regs *regs_user, * than just blindly copying user_regs. */ regs_user->abi = PERF_SAMPLE_REGS_ABI_64; - /* usually contains return address (same as ->ip) */ - regs_user_copy->cx = -1; } else { /* We're probably in an interrupt or exception. */ regs_user->abi = user_64bit_mode(user_regs) ? -- 1.8.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/