From: bjorn@mork.no (Bjørn Mork)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Question about assembly in set bit function for x86 architecture
Date: Mon, 20 Apr 2015 18:29:12 +0200 [thread overview]
Message-ID: <87bniircfb.fsf@nemi.mork.no> (raw)
In-Reply-To: <6508.1429544797@turing-police.cc.vt.edu> (Valdis Kletnieks's message of "Mon, 20 Apr 2015 11:46:37 -0400")
Valdis.Kletnieks at vt.edu writes:
> On Sun, 19 Apr 2015 19:08:17 -0400, Nicholas Krause said:
>
>> The reason I am asking is that is assembly worth my time to learn for this
>> part of the kernel, I understand it's use in boot code but outside of that and
>> cache memory lines in architecture directories there is very little, 95 percent
>> of the kernel is written in C. In addition due to this the only practical
>> reason I can thing of is for debugging, how useful is assembly for kernel
>> debugging is my other question about this topic.
>
> We're not going to bail you out here, Nick. Either learn enough assembly
> to answer your question, or don't obsess over one line of code and assume
> it works.
It's not necessary to limit this advice by language or specific lines of
code.
NO part of the kernel can be understood without investing some time
trying to learn. But fear not - there is a shortcut available for those
(assuming there might be more than one) who refuse to learn:
Assume it works.
OK, I'll admit taking that route more than once myself :-)
Bj?rn
next prev parent reply other threads:[~2015-04-20 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-19 20:51 Question about assembly in set bit function for x86 architecture nick
2015-04-19 21:13 ` Anuz Pratap Singh Tomar
2015-04-19 23:08 ` Nicholas Krause
2015-04-19 23:11 ` Anuz Pratap Singh Tomar
2015-04-20 8:05 ` Alexander Kuleshov
2015-04-20 15:46 ` Valdis.Kletnieks at vt.edu
2015-04-20 16:29 ` Bjørn Mork [this message]
2015-04-20 16:27 ` Jeff Haran
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=87bniircfb.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=kernelnewbies@lists.kernelnewbies.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.