From: Steve Kenton <skenton@ou.edu>
To: lkml <linux-kernel@vger.kernel.org>
Subject: pointer to .subsection and .previous usage in kernel?
Date: Thu, 27 Feb 2003 08:58:41 -0600 [thread overview]
Message-ID: <3E5E27A1.70BE4B30@ou.edu> (raw)
Anyone have a pointer to what we are really trying to accomplish
with .subsection and .previous in the in-line and asm stuff?
Like maybe a readme or coding style doc for in-line and asm code?
That was the main thing I tripped over while trying to build
a 2.5 kernel using the cygwin toolchain with an eye towards
uml under windows. I found very little documentation about
the directives themselves even in the gnu info stuff and nada,
except one thread about abstracting them in spinlocks,
bout how/why they are used in the kernel. They appear to be
elf specific which is why the i386pe stuff puked on them. I
assume that most of this is to maximize cache hits, but that's
just a guess. There are a largish handful of them scattered
around the kernel outside of locks. Any pointers would be appreciated.
Steve
next reply other threads:[~2003-02-27 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 14:58 Steve Kenton [this message]
2003-02-27 15:46 ` pointer to .subsection and .previous usage in kernel? Richard B. Johnson
-- strict thread matches above, loose matches on Subject: below --
2003-02-27 22:20 Steve Kenton
2003-02-28 15:59 Jeff Dike
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=3E5E27A1.70BE4B30@ou.edu \
--to=skenton@ou.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.