From: Mahesh Jagannath Salgaonkar <mahesh@linux.vnet.ibm.com>
To: linux-s390@vger.kernel.org
Subject: Re: [patch 1/3] S390-HWBKPT: Prepare s390 for hardware breakpoint
Date: Mon, 04 Jan 2010 10:21:34 +0000 [thread overview]
Message-ID: <4B41BE5E.3040009@linux.vnet.ibm.com> (raw)
In-Reply-To: <20091218215655.GA13103@osiris.boeblingen.de.ibm.com>
Heiko Carstens wrote:
> On Mon, Dec 14, 2009 at 07:27:24PM +0530, Mahesh Salgaonkar wrote:
>> Prepare the s390 code for HW Breakpoint infrastructure patches by including
>> relevant constant definitions and function declarations.
>
> Why split this? Especially it would be nice to have function declarations and
> the functions in the same patch :)
>
Sure, will merge the first 2 patches.
>> Index: linux-2.6-tip/arch/s390/include/asm/hw_breakpoint.h
>> ===================================================================
>> --- /dev/null
>> +++ linux-2.6-tip/arch/s390/include/asm/hw_breakpoint.h
>> @@ -0,0 +1,65 @@
>> + */
>> +#ifndef _S390_HW_BREAKPOINT_H
>> +#define _S390_HW_BREAKPOINT_H
>> +
>> +#ifdef __KERNEL__
>
> This header isn't exported, so the ifdef seems to be unnecessary.
>
>> +#define __ARCH_HW_BREAKPOINT_H
>
> Seems to be unnecessary as well.
>
>> +extern int hw_breakpoint_exceptions_notify(struct notifier_block *unused,
>> + unsigned long val, void *data);
>> +
>> +int arch_install_hw_breakpoint(struct perf_event *bp);
>> +void arch_uninstall_hw_breakpoint(struct perf_event *bp);
>> +void hw_breakpoint_pmu_read(struct perf_event *bp);
>> +void hw_breakpoint_pmu_unthrottle(struct perf_event *bp);
>> +
>> +extern void arch_fill_perf_breakpoint(struct perf_event *bp);
>
> At least this function doesn't exist in your second patch.
>
Will remove it.
>> Index: linux-2.6-tip/kernel/hw_breakpoint.c
>> ===================================================================
>> --- linux-2.6-tip.orig/kernel/hw_breakpoint.c
>> +++ linux-2.6-tip/kernel/hw_breakpoint.c
>> @@ -30,6 +30,9 @@
>> * This file contains the arch-independent routines.
>> */
>>
>> +#ifdef CONFIG_S390
>> +#include <asm/bitsperlong.h>
>> +#endif
>
> Please don't add CONFIG_S390 ifdefs in common code, unless it cannot be
> avoided. Why is this needed?
>
>> #include <linux/irqflags.h>
This was included to avoid compilation errors. The 'asm/irqflags.h'
included from 'linux/irqflags' uses "BITS_PER_LONG" #def which is
declared in 'asm/bitsperlong.h'.
>> #include <linux/kallsyms.h>
>> #include <linux/notifier.h>
prev parent reply other threads:[~2010-01-04 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091214135724.GB21568@in.ibm.com>
2009-12-18 21:56 ` [patch 1/3] S390-HWBKPT: Prepare s390 for hardware breakpoint Heiko Carstens
2010-01-04 10:21 ` Mahesh Jagannath Salgaonkar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B41BE5E.3040009@linux.vnet.ibm.com \
--to=mahesh@linux.vnet.ibm.com \
--cc=linux-s390@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.