From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/5194] IO problem on begin/end probes; need
Date: Mon, 21 Jan 2008 18:13:00 -0000 [thread overview]
Message-ID: <20080121181221.4177.qmail@sourceware.org> (raw)
In-Reply-To: <20071018140048.5194.hunt@redhat.com>
------- Additional Comments From fche at redhat dot com 2008-01-21 18:12 -------
(In reply to comment #6)
> (In reply to comment #5)
> > I'm not clear about whether there actually exists a bug described
> > in comment #0, in that we do not enable sleeping or preemption
> > during begin/end probes, so we can't switch CPUs.
>
> We don't? News to me. It's easy to test.
> [...]
> in_interrupt:0, irqs_disabled:0, preempt_count:0
Thanks for running the test.
The preempt_count should not be 0.
The generated code in enter_begin_probe clearly contains
a preempt_disable(), so the question is why this does not
appear to have effect.
--
What |Removed |Added
----------------------------------------------------------------------------
Summary|IO problem on begin/end |IO problem on begin/end
|probes |probes; need
http://sourceware.org/bugzilla/show_bug.cgi?id=5194
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2008-01-21 18:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 14:01 [Bug runtime/5194] New: IO problem on begin/end probes hunt at redhat dot com
2007-10-18 14:10 ` [Bug runtime/5194] " fche at redhat dot com
2007-10-18 14:11 ` fche at redhat dot com
2007-10-18 14:25 ` hunt at redhat dot com
2007-10-18 15:19 ` fche at redhat dot com
2008-01-21 17:42 ` fche at redhat dot com
2008-01-21 17:56 ` hunt at redhat dot com
2008-01-21 18:13 ` fche at redhat dot com [this message]
2008-01-21 18:37 ` [Bug runtime/5194] IO problem on begin/end probes; need fche at redhat dot com
2008-01-29 16:40 ` fche at redhat dot com
2008-01-29 17:08 ` hunt at redhat dot com
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=20080121181221.4177.qmail@sourceware.org \
--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).