From: "stephane eranian" <eranian@googlemail.com>
To: "Paul Mackerras" <paulus@samba.org>
Cc: linux-kernel@vger.kernel.org, "Stephen Rothwell" <sfr@canb.auug.org.au>
Subject: Re: [patch 00/24] perfmon3: introduction
Date: Tue, 11 Nov 2008 01:29:28 +0100 [thread overview]
Message-ID: <7c86c4470811101629o69e7f012wd45cd1a58cf245b@mail.gmail.com> (raw)
In-Reply-To: <7c86c4470811100724y1f61086co6ced2510383c5ae2@mail.gmail.com>
Stephen,
I have updated the linux-next tree to fix the issue brought up
by Paul.
Please pull from linux-next tree.
Thanks.
On Mon, Nov 10, 2008 at 4:24 PM, stephane eranian
<eranian@googlemail.com> wrote:
> Paul,
>
> On Mon, Nov 10, 2008 at 3:41 AM, Paul Mackerras <paulus@samba.org> wrote:
>> Stephane,
>>
>> I have just looked through this set of patches and it mostly looks
>> fine to me. There is just one thing, and that is that the way you
>> access bitmaps using cast_ulp() won't work on 32-bit big-endian
>> machines such as 32-bit PowerPC. I suggest that instead of using
>> cast_ulp(), you have a set of abstracted bit-vector operations that
>> can be implemented by the arch code - and on x86/ia64, they would be
>> implemented with cast_ulp() + test_bit/__set_bit/etc. as at present.
>>
>
> Thanks for bringing this up. I think we had talked about this a while back.
>
> There is indeed a problem on big endian 32-bit machines The cast will
> pick up the wrong half of the u64. I think the best solution to this problem
> is as you suggested. Consequently, I have added a perfmon abstraction (bv)
> with its set of arch callbacks. The API takes u64 *.On x86, IA-64, it simply
> calls the bitmap_*() API. On PPC, it will have to adjust when compiling for
> 32 bits.
>
> Here is the example of __set_bit() on x86:
>
> static inline void pfm_arch_bv_set_bit(int b, u64 *a)
> {
> __set_bit(b, (unsigned long *)a);
> }
>
>
> I will push this into my linux-next tree and ask Stephen to pull from it again.
>
prev parent reply other threads:[~2008-11-11 0:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 15:05 eranian
2008-10-22 4:25 ` David Miller
2008-10-22 8:39 ` stephane eranian
2008-10-22 16:58 ` Jesse Barnes
2008-10-22 17:22 ` Andrew Morton
2008-10-23 7:19 ` stephane eranian
2008-11-10 2:41 ` Paul Mackerras
2008-11-10 15:24 ` stephane eranian
2008-11-11 0:29 ` stephane eranian [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=7c86c4470811101629o69e7f012wd45cd1a58cf245b@mail.gmail.com \
--to=eranian@googlemail.com \
--cc=eranian@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®