From: Carl Spalletta <cspalletta@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 'fscope': a new debugging tool
Date: Mon, 26 May 2003 16:09:56 -0700 (PDT) [thread overview]
Message-ID: <20030526230956.65746.qmail@web41504.mail.yahoo.com> (raw)
Output from 'fscope -func=add_to_swap_cache -cycles',
questions follow:
1 cycle detected add_to_swap_cache read_swap_cache_async
do_swap_page handle_pte_fault handle_mm_fault get_user_pages
make_pages_present find_extend_vma get_user_pages
2 cycle detected add_to_swap_cache read_swap_cache_async
do_swap_page handle_pte_fault handle_mm_fault __verify_write
access_ok clear_user __do_clear_user clear_user
3 cycle detected add_to_swap_cache read_swap_cache_async
do_swap_page handle_pte_fault handle_mm_fault __verify_write
access_ok clear_user __do_clear_user __clear_user clear_user
4 cycle detected add_to_swap_cache read_swap_cache_async
do_swap_page handle_pte_fault handle_mm_fault __verify_write
access_ok copy_from_user ax25_rt_ioctl ax25_protocol_function
ax25_rx_iframe ax25_ds_state3_machine ax25_ds_frame_in
ax25_process_rx_frame ax25_rcv ax25_kiss_rcv ax25_protocol_function
5 cycle detected add_to_swap_cache read_swap_cache_async
do_swap_page handle_pte_fault handle_mm_fault __verify_write
access_ok copy_from_user ax25_rt_ioctl ax25_protocol_function
ax25_rx_iframe ax25_protocol_function
6 cycle detected add_to_swap_cache read_swap_cache_async
do_swap_page handle_pte_fault handle_mm_fault __verify_write
access_ok copy_from_user command ACOMMAND com90xx_probe arcnet_init
com90xx_probe
7 cycle detected add_to_swap_cache read_swap_cache_async
do_swap_page handle_pte_fault handle_mm_fault __verify_write
access_ok copy_from_user __copy_from_user copy_from_user
8-104 cycle detected add_to_swap_cache read_swap_cache_async
do_swap_page handle_pte_fault handle_mm_fault __verify_write
access_ok copy_from_user COPY_FROM_USER write
acpi_os_write_pci_configuration acpi_hw_low_level_write
acpi_hw_disable_gpe_block .. [too many variants to list]
QUESTIONS
0) The fields go from innermost frame to outermost frame.
The last field is the outermost. So read them backwards,
until the last field repeats - there's your cycle.
1) These are merely _potentially_ dangerous cycles in the
code - so what is a good heuristic to decide which ones
to investigate?
2) Why in this case are there 12 times as many instances
found for the ACPI stuff as for the rest of the kernel?
Is ACPI a can of worms or what?
next reply other threads:[~2003-05-26 22:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 23:09 Carl Spalletta [this message]
2003-05-28 21:33 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-05-26 22:27 Carl Spalletta
2003-05-26 19:50 Carl Spalletta
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=20030526230956.65746.qmail@web41504.mail.yahoo.com \
--to=cspalletta@yahoo.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®