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: <6bffcb0e0704251355r6de26273s47ba5c857ed0f129@mail.gmail.com>
Date:	Wed, 25 Apr 2007 22:55:36 +0200
From:	"Michal Piotrowski" <michal.k.k.piotrowski@...il.com>
To:	"Andi Kleen" <ak@...e.de>
Cc:	"Jeremy Fitzhardinge" <jeremy@...p.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Ingo Molnar" <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: mm snapshot broken-out-2007-04-25-02-49.tar.gz uploaded

On 25/04/07, Andi Kleen <ak@...e.de> wrote:
> On Wednesday 25 April 2007 22:42:44 Jeremy Fitzhardinge wrote:
> > Michal Piotrowski wrote:
> > > Timing information is broken
> > >
> >
> > This looks like Andi's sched_clock stuff hitting: it returns an
> > inherently per-cpu result, so using it for printk timestamps isn't very
> > useful.
>
> It should actually roughly work. There can be some drift, but there shouldn't
> be that much error. All CPUs should tick at roughly the same rate because
> it's scaled to nanoseconds
>
> If the drift is a big issue it would also be possible to resync every minute
> or so, but I haven't implemented that.
>
> There will be always some minor monotonicities because it won't try
> to stop the CPU from reordering instructions.
>
> I don't know why it is that off in your case.

Maybe because it's P4 HT?

Regards,
Michal

-- 
Michal K. K. Piotrowski
LTG - Linux Testers Group (PL)
(http://www.stardust.webpages.pl/ltg/)
LTG - Linux Testers Group (EN)
(http://www.stardust.webpages.pl/linux_testers_group_en/)
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ