From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Mike Galbraith <efault@gmx.de>
Subject: Re: [git pull] scheduler updates
Date: Sat, 8 Nov 2008 20:40:55 +0100 [thread overview]
Message-ID: <20081108194055.GA30892@elte.hu> (raw)
In-Reply-To: <alpine.LFD.2.00.0811081115290.3468@nehalem.linux-foundation.org>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Sat, 8 Nov 2008, Ingo Molnar wrote:
> >
> > So that's why my change moves it from the __native_read_tsc() over
> > to _only_ the vget_cycles().
>
> Ahh. I was looking at native_read_tscp(). Which has no barriers. But
> then we don't actually save the actual TSC, we only end up using the
> "p" part, so we don't care..
sidenote #3: RDTSCP is a relatively new instruction, and has implicit
barrier properties: it is a serializing instruction.
Ingo
next prev parent reply other threads:[~2008-11-08 19:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 17:02 [git pull] scheduler updates Ingo Molnar
2008-11-08 18:28 ` Linus Torvalds
2008-11-08 18:38 ` Linus Torvalds
2008-11-08 18:41 ` Arjan van de Ven
2008-11-08 19:00 ` Linus Torvalds
2008-11-08 19:05 ` Ingo Molnar
2008-11-08 19:20 ` Linus Torvalds
2008-11-08 19:29 ` Ingo Molnar
2008-11-17 22:43 ` Venki Pallipadi
2008-11-17 22:50 ` Ingo Molnar
2008-11-17 23:04 ` Venki Pallipadi
2008-11-17 23:13 ` Ingo Molnar
2008-11-08 19:40 ` Ingo Molnar [this message]
2008-11-08 19:10 ` Ingo Molnar
2008-11-08 18:52 ` Ingo Molnar
2008-11-08 18:57 ` Ingo Molnar
2008-11-08 19:32 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2018-02-06 21:38 [GIT PULL] " Ingo Molnar
2008-03-21 16:23 [git pull] " Ingo Molnar
2008-02-29 18:04 Ingo Molnar
2008-02-13 15:58 Ingo Molnar
2008-01-31 21:54 Ingo Molnar
2007-12-30 16:45 Ingo Molnar
2007-10-24 16:39 Ingo Molnar
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=20081108194055.GA30892@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox