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
| ||
|
Date: Mon, 12 Sep 2011 23:18:04 -0400 From: Mark Salter <msalter@...hat.com> To: john stultz <johnstul@...ibm.com> Cc: linux-kernel <linux-kernel@...r.kernel.org>, "H. Peter Anvin" <hpa@...or.com> Subject: Re: [PATCH 10/24] C6X: time management On Mon, 2011-09-12 at 18:16 -0700, john stultz wrote: > On Wed, Aug 31, 2011 at 2:26 PM, Mark Salter <msalter@...hat.com> wrote: > > The C6X architecture includes a 64-bit free running core clock counter which > > is used as the clocksource. The SoCs have a number of 64-bit programmable > > timers. One of these is used as the clockevent timer. > > > > Signed-off-by: Mark Salter <msalter@...hat.com> > > Sort of a tangent to this specific patch, but since it came up > recently in the x32 discussion, I wanted to check if you were using a > 64bit definition of time_t? C6X uses the asm-generic definition which is a long, so 32-bits. --Mark -- 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/
Powered by blists - more mailing lists