From: "mhiramat at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/9820] New: discontiguous cpu-mapping support
Date: Wed, 04 Feb 2009 19:09:00 -0000 [thread overview]
Message-ID: <20090204183102.9820.mhiramat@redhat.com> (raw)
When using cpu-hotplug, cpus are not mapped continuously(this means it is
possible that only cpu0 and cpu3 exist on the system).
For example,
# echo 0 > /sys/devices/system/cpu/cpu1/online
(offline 1-3)
# echo 1 > /sys/devices/system/cpu/cpu3/online
(online 3 again)
makes only cpu0 and cpu3 online.
systemtap module already supported this situation.
# ls /sys/kernel/debug/systemtap/stap_4b2957991db0f88f66cd013b330b963f_173/
dropped trace0 trace3
However, stapio doesn't.
--
Summary: discontiguous cpu-mapping support
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: mhiramat at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=9820
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
reply other threads:[~2009-02-04 18:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090204183102.9820.mhiramat@redhat.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.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).