All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org
Subject: Re: P6 NOPs again: MPSC?
Date: Tue, 11 Mar 2008 07:43:25 +0100	[thread overview]
Message-ID: <47D62A0D.3070107@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0803102142440.2464@blonde.site>

Hugh Dickins wrote:
> 
> Yup, I realized that (with || in place of &&): I meant that perhaps
> it was supposed to say X86_64 || (!X86_GENERIC && (M686 || ....))
> since quite a lot of other options there have "|| X86_64" to cover
> all the 64-bit possibilities at once i.e. is it only MPSC that
> needs to be added, or both MPSC and CPU_GENERIC?
> 

No.  The left-hand clause (X86_64 || !X86_GENERIC) indicates when using 
these NOPs are *permitted*; the right-hand clause indicates when doing 
so is *desirable*.  The latter isn't, for example, for K8, even on 64 bits.

	-hpa


  reply	other threads:[~2008-03-11  6:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-04 19:33 [PATCH] x86: a P4 is a P6 not an i486 Hugh Dickins
2008-03-04 21:01 ` Ingo Molnar
2008-03-04 21:24   ` H. Peter Anvin
2008-03-04 21:32     ` Ingo Molnar
2008-03-10 19:14     ` P6 NOPs again: MPSC? Hugh Dickins
2008-03-10 20:17       ` H. Peter Anvin
2008-03-10 22:02         ` Hugh Dickins
2008-03-11  6:43           ` H. Peter Anvin [this message]
2008-03-11 14:00             ` Hugh Dickins
2008-03-11  9:28           ` Ingo Molnar
2008-03-11 13:45             ` Hugh Dickins

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=47D62A0D.3070107@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.