From: Stephane Eranian <eranian@hpl.hp.com>
To: "Bryan O'Sullivan" <bos@serpentine.com>
Cc: linux-kernel@vger.kernel.org, perfmon@napali.hpl.hp.com,
perfctr-devel@lists.sourceforge.net, linux-ia64@vger.kernel.org
Subject: Re: perfmon2 code review: 32-bit ABI on 64-bit OS
Date: Mon, 13 Feb 2006 12:34:03 -0800 [thread overview]
Message-ID: <20060213203403.GK11285@frankl.hpl.hp.com> (raw)
In-Reply-To: <1139596023.9646.111.camel@serpentine.pathscale.com>
Bryan,
On Fri, Feb 10, 2006 at 10:27:02AM -0800, Bryan O'Sullivan wrote:
>
> On some 64-bit arches (e.g. x86_64), most userspace code is 64-bit,
> while on others (e.g. powerpc), most is 32-bit. Reducing the number of
> things that a userspace tool or library writer can trip over seems like
> a good thing here, even if it slightly complicates perfmon's internals.
>
> > Note that there are similar issues with the remapped sampling buffer.
> > There, you need to explicitly compile your tool with a special option
> > to force certain types to be 64-bit (size_t, void *).
>
> It's pretty normal to just use 64-bit quantities in these cases, and
> cast appropriately.
>
So if I understand you correctly, you are saying it is best to have bitmasks
hardcoded to u64 and have the kernel cast to match the bitmap_*() interface.
This would not cause any alignment problems on neither 32-bit nor 64-bit system.
--
-Stephane
prev parent reply other threads:[~2006-02-13 20:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 18:37 [perfmon] Re: quick overview of the perfmon2 interface Truong, Dan
2006-01-20 22:22 ` Andrew Morton
2006-01-25 20:33 ` Bryan O'Sullivan
2006-01-25 22:28 ` [Perfctr-devel] " Stephane Eranian
2006-01-25 22:46 ` Bryan O'Sullivan
2006-01-26 7:48 ` Stephane Eranian
2006-01-26 18:26 ` Bryan O'Sullivan
[not found] ` <1138649612.4077.50.camel@localhost.localdomain>
[not found] ` <1138651545.4487.13.camel@camp4.serpentine.com>
[not found] ` <1139155731.4279.0.camel@localhost.localdomain>
[not found] ` <1139245253.27739.8.camel@camp4.serpentine.com>
2006-02-10 15:36 ` perfmon2 code review: 32-bit ABI on 64-bit OS Stephane Eranian
2006-02-10 18:27 ` Bryan O'Sullivan
[not found] ` <1139681785.4316.33.camel@localhost.localdomain>
2006-02-11 22:33 ` [perfmon] " Stephane Eranian
2006-02-12 23:46 ` [Perfctr-devel] " David Gibson
2006-02-13 0:03 ` Eric Gouriou
2006-02-13 20:31 ` Stephane Eranian
[not found] ` <1139857076.4342.10.camel@localhost.localdomain>
2006-02-14 23:41 ` [Perfctr-devel] " Stephane Eranian
2006-02-20 17:54 ` Stephane Eranian
2006-02-13 20:34 ` 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=20060213203403.GK11285@frankl.hpl.hp.com \
--to=eranian@hpl.hp.com \
--cc=bos@serpentine.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perfctr-devel@lists.sourceforge.net \
--cc=perfmon@napali.hpl.hp.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;
as well as URLs for NNTP newsgroup(s).