From: "Stone, Joshua I" <joshua.i.stone@intel.com>
To: "Li Guanglei" <guanglei@cn.ibm.com>
Cc: <systemtap@sourceware.org>
Subject: RE: [UPDATE] Linux Kernel Event Trace tool(LKET)
Date: Fri, 02 Jun 2006 00:44:00 -0000 [thread overview]
Message-ID: <CBDB88BFD06F7F408399DBCF8776B3DC075CCEB1@scsmsx403.amr.corp.intel.com> (raw)
On Sunday, May 28, 2006 11:27 PM, Li Guanglei wrote:
> Li Guanglei ??:
>>
>>
>> I don't have a x86_64 at hand. I tried
>> __switch_to(scheduler.ctxswitch in src/tapset/schedule.stp) and it
>> will cause kernel panic. I will take a further look at this and will
>> open a bug for this if needed.
>
> I tested again with 2.6.16.16 & 2.6.16-1.2211_FC6 on x86, _switch_to
> won't cause kernel panic any more. So I think this bug has been fixed
> in latest kernel.
Probes on __switch_to are disallowed on x86_64 -- see bug #2068.
http://sources.redhat.com/bugzilla/show_bug.cgi?id=2068
Josh
next reply other threads:[~2006-06-02 0:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 0:44 Stone, Joshua I [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-02 0:48 Stone, Joshua I
2006-06-02 1:56 ` Li Guanglei
2006-05-15 21:09 Stone, Joshua I
2006-05-12 22:34 Stone, Joshua I
2006-05-15 6:34 ` Li Guanglei
2006-05-19 4:09 ` Li Guanglei
2006-05-23 23:33 ` Li Guanglei
2006-05-24 15:27 ` William Cohen
2006-05-25 0:21 ` Li Guanglei
2006-05-27 2:35 ` Guang Lei Li
2006-05-25 8:23 ` Li Guanglei
2006-05-29 6:26 ` Li Guanglei
2006-05-24 15:43 ` Frank Ch. Eigler
2006-05-25 14:03 ` Li Guanglei
2006-05-11 8:26 Li Guanglei
[not found] ` <446A2BB6.4040700@lanl.gov>
2006-05-17 0:18 ` Li Guanglei
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=CBDB88BFD06F7F408399DBCF8776B3DC075CCEB1@scsmsx403.amr.corp.intel.com \
--to=joshua.i.stone@intel.com \
--cc=guanglei@cn.ibm.com \
--cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).