Re: [patch] Mark rdtsc as sync only for netburst, not for core2

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...

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [patch] Mark rdtsc as sync only for netburst, not for core2
    • From: "Zhang, Yanmin" <[email protected]>

• References:
  • [patch] Mark rdtsc as sync only for netburst, not for core2
    • From: Arjan van de Ven <[email protected]>
  • Re: [patch] Mark rdtsc as sync only for netburst, not for core2
    • From: Andi Kleen <[email protected]>
  • Re: [patch] Mark rdtsc as sync only for netburst, not for core2
    • From: Arjan van de Ven <[email protected]>

• Prev by Date: Re: A commit between 2.6.16.4 and 2.6.16.5 failed crashme
• Next by Date: Re: [PATCH] lockdep: fix sk->sk_callback_lock locking
• Previous by thread: Re: [patch] Mark rdtsc as sync only for netburst, not for core2
• Next by thread: Re: [patch] Mark rdtsc as sync only for netburst, not for core2
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]