linux-kernel - Re: [tip:perf/core] perf/x86: Add generic Intel uncore PMU support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20120621155159.239aa972.akpm@linux-foundation.org>
Date:	Thu, 21 Jun 2012 15:51:59 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	mingo@...nel.org, linux-kernel@...r.kernel.org,
	a.p.zijlstra@...llo.nl, torvalds@...ux-foundation.org,
	zheng.z.yan@...el.com, tglx@...utronix.de,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] perf/x86: Add generic Intel uncore PMU support

On Thu, 21 Jun 2012 15:47:49 -0700
"H. Peter Anvin" <hpa@...or.com> wrote:

> On 06/21/2012 03:43 PM, Andrew Morton wrote:
> > 
> > Regardless of that, we have some head-scratching to do:
> > 
> > 
> > #define UNCORE_PMU_HRTIMER_INTERVAL       (60 * NSEC_PER_SEC)
> > 
> > and
> > 
> > #define NSEC_PER_SEC    1000000000L
> > 
> > and 60 billion doesn't fit in 32 bits.  So do we fix the
> > perf_event_intel_uncore.c callsites?  Or do we fix the
> > UNCORE_PMU_HRTIMER_INTERVAL definition?  Or do we fix the NSEC_PER_SEC
> > definition?
> > 
> > I'm thinking perhaps the latter.  What *is* the type of a nanosecond in
> > Linux?  include/linux/ktime.h is pretty insistent that it is u64.  If
> > so, NSEC_PER_SEC should logically have type ULL.  But changing both its
> > size and signedness is a pretty big change.
> 
> We could change the size only.  The range from 9223372036.854775808 to
> 18446744073.709551615 seconds (292-584 years) isn't really that significant.
> 

What *is* significant is the effect of a signedness change upon
arithmetic, conversions, warnings, etc.  And whether such a change
might actually introduce bugs.


Back away and ask the broader questions: why did ktime_t choose
unsigned?  Is time a signed concept?  What is the right thing to do
here, from a long-term design perspective?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/