From: Mahesh Jagannath Salgaonkar <mahesh@linux.vnet.ibm.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>, ffweisbec@gmail.com
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
schwidefsky@de.ibm.com, "K.Prasad" <prasad@linux.vnet.ibm.com>
Subject: Re: [patch 3/3] S390-HWBKPT v3: Modify ptrace to use Hardware Breakpoint interfaces.
Date: Thu, 21 Jan 2010 11:11:25 +0530 [thread overview]
Message-ID: <4B57E905.1060900@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100120110805.GD7619@osiris.boeblingen.de.ibm.com>
Heiko Carstens wrote:
> On Thu, Jan 14, 2010 at 11:58:59AM +0530, Mahesh Salgaonkar wrote:
>> Modify the ptrace code to use the hardware breakpoint interfaces for
>> user-space
>
> I didn't look too deep into this one. So actually only one trivial comment:
>
>> diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
>> index 9a1d276..cb74f24 100644
>> --- a/include/linux/perf_event.h
>> +++ b/include/linux/perf_event.h
>> @@ -215,7 +215,11 @@ struct perf_event_attr {
>>
>> __u64 bp_addr;
>> __u32 bp_type;
>> +#ifdef __s390x__
>> + __u64 bp_len;
>> +#else
>> __u32 bp_len;
>> +#endif
>> };
>>
>> /*
>>
>
> Any chance to change common code to change that to an __u64 (unconditional)
> or at least an unsigned long?
> I'd hate to see an ifdef __s390x__ in common code.
Can we have the above common code to change the type of 'bp_len' to
__u64? In s390x arch watch point length can be upto 2^64.
next parent reply other threads:[~2010-01-21 5:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100114061701.485284442@mars.in.ibm.com>
[not found] ` <20100114062859.GD1753@in.ibm.com>
[not found] ` <20100120110805.GD7619@osiris.boeblingen.de.ibm.com>
2010-01-21 5:41 ` Mahesh Jagannath Salgaonkar [this message]
2010-01-21 6:58 ` [patch 3/3] S390-HWBKPT v3: Modify ptrace to use Hardware Breakpoint interfaces Mahesh Jagannath Salgaonkar
2010-01-25 20:40 ` Frederic Weisbecker
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=4B57E905.1060900@linux.vnet.ibm.com \
--to=mahesh@linux.vnet.ibm.com \
--cc=ffweisbec@gmail.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prasad@linux.vnet.ibm.com \
--cc=schwidefsky@de.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox