From: Joerg Roedel <joro@8bytes.org>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Andi Kleen <andi@firstfloor.org>,
Joerg Roedel <joerg.roedel@amd.com>,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, benjamin.serebrin@amd.com
Subject: Re: Whats the purpose of get_cycles_sync()
Date: Wed, 31 Oct 2007 11:23:46 +0100 [thread overview]
Message-ID: <20071031102346.GE29700@8bytes.org> (raw)
In-Reply-To: <20071030220209.GA21142@suse.cz>
Hi Vojtech,
On Tue, Oct 30, 2007 at 11:02:09PM +0100, Vojtech Pavlik wrote:
> The K8's still guarantee that subsequent RDTSCs return increasing
> values, even if the processor reorders them.
>
> What could have been happening then was that the RDTSC instruction might
> have been reordered by the CPU out of the seqlock, causing trouble in
> the calculation.
>
> Anyway, adding the CPUID didn't solve all the problems we've seen back
> then, and so far none of the approaches for using TSC without acquiring
> a spinlock on multi-socket AMD boxes worked 100% correctly.
Can you tell me more about the problems you have seen or give me a
pointer to a mail discussion regarding that problems? Can you also
provide your test program to me please? I want to understand these
problems a bit better.
Joerg
next prev parent reply other threads:[~2007-10-31 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 17:44 Whats the purpose of get_cycles_sync() Joerg Roedel
2007-10-30 20:21 ` Andi Kleen
2007-10-30 22:02 ` Vojtech Pavlik
2007-10-30 22:42 ` Andi Kleen
2007-10-31 10:23 ` Joerg Roedel [this message]
2007-10-31 10:18 ` Joerg Roedel
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=20071031102346.GE29700@8bytes.org \
--to=joro@8bytes.org \
--cc=andi@firstfloor.org \
--cc=benjamin.serebrin@amd.com \
--cc=hpa@zytor.com \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vojtech@suse.cz \
/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).