public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "Stone, Joshua I" <joshua.i.stone@intel.com>
To: "William Cohen" <wcohen@redhat.com>
Cc: "Roland McGrath" <roland@redhat.com>,
		"SystemTap" <systemtap@sources.redhat.com>
Subject: RE: SystemTap vs. FC5 Xen kernels  (was: 03-23-2006 Meeting minutes)
Date: Fri, 31 Mar 2006 20:38:00 -0000	[thread overview]
Message-ID: <CBDB88BFD06F7F408399DBCF8776B3DC06D0218D@scsmsx403.amr.corp.intel.com> (raw)

William Cohen wrote:
> On the earlier s390 kernels the regular timer interrupt was
> eliminated. This was done for efficiency. The s390 has had
> virtualization for years. Having the Linux kernels do the timer
> interrupt was unwanted overhead. I wonder if the xen kernel is doing
> the same, only have timer interrupt 
> when something really needs to get run at a certain time.
> 
> http://lwn.net/Articles/138969/

One of the comments after this article specifically mentions that
"similar patches" are in xen as well.  I find it odd that the
timer.ms/jiffies probes still work fine, but timer.profile gets no
probes at all.  It may just be that the dynamic-ticks patch changes the
timer path, so the softIRQ timers still happen, but the hard IRQ timers
used for timer.profile are sidestepped.

It may turn out that timer.profile will have to be emulated using PMU
sampling on clockticks...

> Do we need variations on the timer probe,  wall clock time and
> virtual time? 

Possibly - do you have a suggestion for how to accomplish this?  The
current timer probes are using the {add,mod,del}_timer interface, which
is based purely on jiffies.


Josh

             reply	other threads:[~2006-03-31 20:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31 20:38 Stone, Joshua I [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-31  2:36 Stone, Joshua I
2006-03-31 14:07 ` William Cohen
2006-03-30 21:18 Stone, Joshua I
2006-03-30  1:05 Stone, Joshua I
2006-03-30 14:44 ` William Cohen

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=CBDB88BFD06F7F408399DBCF8776B3DC06D0218D@scsmsx403.amr.corp.intel.com \
    --to=joshua.i.stone@intel.com \
    --cc=roland@redhat.com \
    --cc=systemtap@sources.redhat.com \
    --cc=wcohen@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).