public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [patch] Mark rdtsc as sync only for netburst, not for core2
Date: Wed, 29 Nov 2006 17:07:48 +0800	[thread overview]
Message-ID: <1164791268.2873.5.camel@ymzhang> (raw)
In-Reply-To: <456D4648.7000509@linux.intel.com>

On Wed, 2006-11-29 at 09:35 +0100, Arjan van de Ven wrote:
> Zhang, Yanmin wrote:
> >> but second of all, the core2 cpus are dual core so.. .what does it 
> >> bring you at all?
> > 
> > When there is only one cpu (or UP), the go backwards issue doesn't exist,
> 
> it does exist for single-socket dual core already. And core2 is dual 
> core...
> 
> > so
> > don't use cpuid here for UP. Another function init_amd already does so.
> > 
> not anymore.. that got fixed very recently...
Thanks.

> (but you are right; on AMD the speculation is even bigger so there 
> even on single core you need cpuid)

      reply	other threads:[~2006-11-29  9:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-28 10:28 [patch] Mark rdtsc as sync only for netburst, not for core2 Arjan van de Ven
2006-11-28 10:36 ` Andi Kleen
     [not found]   ` <1164774239.15257.5.camel@ymzhang>
2006-11-29  7:30     ` Arjan van de Ven
2006-11-29  8:05       ` Nick Piggin
2006-11-29  9:04         ` Zhang, Yanmin
     [not found]       ` <1164787104.2899.7.camel@ymzhang>
2006-11-29  8:35         ` Arjan van de Ven
2006-11-29  9:07           ` Zhang, Yanmin [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=1164791268.2873.5.camel@ymzhang \
    --to=yanmin_zhang@linux.intel.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=arjan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /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