All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: xen-devel@lists.xensource.com
Subject: Linux questions
Date: Mon, 03 Dec 2007 11:24:35 +0000	[thread overview]
Message-ID: <4753F583.76E4.0078.0@novell.com> (raw)

1) Is there a particular reason Jeremy's sched_clock() variant isn't being
used in linux-2.6.18-hg? Specifically, are there any known downsides to
that approach?

2) What is the reason for the inconsistent use of rmb() vs. barrier() in
time-xen.c? It would seem to me that rmb() should be sufficient in all
cases.

3) Why is it that x86-64's __smp_call_function_single(), just like native,
uses cpu_relax() in its wait-for-response loops, while __smp_call_function()
as well as i386's smp_call_function() use barrier(), other than native?

Thanks, Jan

             reply	other threads:[~2007-12-03 11:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-03 11:24 Jan Beulich [this message]
2007-12-03 11:29 ` Linux questions Samuel Thibault
2007-12-03 11:40   ` Jan Beulich
2007-12-03 18:32     ` Keir Fraser
2007-12-04 10:23       ` Jan Beulich
2007-12-04 10:55         ` Keir Fraser
2007-12-04 11:13           ` Andi Kleen
2007-12-04 11:27             ` Keir Fraser
2007-12-04 11:44               ` Andi Kleen
2007-12-04 11:56                 ` Keir Fraser
2007-12-04 12:23                   ` Andi Kleen

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=4753F583.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=xen-devel@lists.xensource.com \
    /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.