All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andi Kleen <ak@suse.de>
Cc: Benjamin LaHaise <bcrl@kvack.org>,
	Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	Chuck Ebbert <76306.1226@compuserve.com>,
	In Cognito <defend.the.world@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: Sysenter crash with Nested Task Bit set
Date: Mon, 18 Sep 2006 12:01:00 -0700	[thread overview]
Message-ID: <450EECEC.207@goop.org> (raw)
In-Reply-To: <200609181839.45546.ak@suse.de>

Andi Kleen wrote:
> Yes it's never fast, but on basically all non P4 CPUs it is still fast enough
> to not be a problem. I suppose it causes a trace cache flush or something like
> that there.

I don't think it's that bad, but it might cause a full pipeline flush.  
I seem to remember measuring its cost at about 50 cycles.

    J


  reply	other threads:[~2006-09-18 19:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-18  3:51 Sysenter crash with Nested Task Bit set Chuck Ebbert
2006-09-18  5:25 ` Andrew Morton
2006-09-18  8:44   ` Mike Galbraith
2006-09-18 15:11   ` Linus Torvalds
2006-09-18 15:06     ` Ingo Molnar
2006-09-18 15:29     ` Andi Kleen
2006-09-18 15:24       ` Ingo Molnar
2006-09-18 16:02       ` Linus Torvalds
2006-09-18 16:10         ` Linus Torvalds
2006-09-18 16:24           ` Jeremy Fitzhardinge
2006-09-18 16:12       ` Benjamin LaHaise
2006-09-18 16:39         ` Andi Kleen
2006-09-18 19:01           ` Jeremy Fitzhardinge [this message]
     [not found] <5a20704e0609171603s55ca52bap71dc2fa2c05d6741@mail.gmail.com>
2006-09-17 23:08 ` In Cognito

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=450EECEC.207@goop.org \
    --to=jeremy@goop.org \
    --cc=76306.1226@compuserve.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=bcrl@kvack.org \
    --cc=defend.the.world@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@osdl.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.