From: Wenji Huang <wenji.huang@oracle.com>
To: Masami Hiramatsu <mhiramat@redhat.com>
Cc: SystemTAP <systemtap@sources.redhat.com>
Subject: Re: tsc_khz export problem
Date: Thu, 18 Oct 2007 01:47:00 -0000 [thread overview]
Message-ID: <4716BA3B.2030401@oracle.com> (raw)
In-Reply-To: <4716B344.6020202@oracle.com>
Sorry for the noise, just update the source and find the change.
The error no longer occurs.
Thanks,
Wenji
Wenji Huang wrote:
> Hi masami-san,
>
> But the error indeed occurs in my box (i386 - 2.6.22.1/2.6.22.9).
> For any script, the compilation pass since there is extern
> declaration of tsc_khz in tsc.h.
> Finally fail in loading modules.
>
> Regards,
> Wenji
>
> Masami Hiramatsu wrote:
>
>> Hi Wenji,
>>
>> Thank you so much for reporting it.
>> In that case, compilation of autoconf-tsc-khz.c must be failed.
>>
>> Wenji Huang wrote:
>>
>>
>>> Hi,
>>>
>>> In latest systemtap source, CONFIG_TSC_KHZ is added. But, find one
>>> problem about tsc_khz.
>>> -----------------------------------------------------
>>> kernel exported declaration(tsc.h)
>>> i386 2.6.18 - 2.6.22 no yes
>>> i386 2.6.23 yes yes
>>>
>>> x86_64 2.6.22 yes yes
>>> x86_64 2.6.23 yes yes
>>> ------------------------------------------------------
>>> So, for i386. in 2.6.18 - 2.6.22. There will be an error reporting
>>> "Unknown symbol tsc_khz" when executing any stap script.
>>>
>>> Regards,
>>> wenji
>>>
>>>
>>>
>>>
>>
>>
>> Regards,
>>
>>
>>
>
prev parent reply other threads:[~2007-10-18 1:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 2:58 Wenji Huang
2007-10-17 15:02 ` Masami Hiramatsu
2007-10-18 1:18 ` Wenji Huang
2007-10-18 1:47 ` Wenji Huang [this message]
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=4716BA3B.2030401@oracle.com \
--to=wenji.huang@oracle.com \
--cc=mhiramat@redhat.com \
--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).