public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@wildopensource.com>
To: davidm@hpl.hp.com
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [Patch] asm workarounds in generic header files
Date: 10 Sep 2003 12:22:37 -0400	[thread overview]
Message-ID: <m3d6e8ipf6.fsf@trained-monkey.org> (raw)
In-Reply-To: <16222.14136.21774.211178@napali.hpl.hp.com>

>>>>> "David" == David Mosberger <davidm@napali.hpl.hp.com> writes:

[trimmed the CC list since this is more at the preference level]

David> In my opinion, moving all the asm-stuff greatly improved
David> readability of the source code.  Especially for folks who are
David> not intimately familiar with GCC asm syntax (which is hairy
David> _and_ platform-specific).

Hi David,

I think this really depends on what you are trying to debug. If you
expect the macros to do exactly what they are described to be doing
then I'd agree. However every so often when you look up the macros you
really want to look at the details what they are actually doing or
even compare them to another arch's implementation to make sure they
are behaving the same. At least thats my experience.

I personally think it's unrealistic to think one can try and debug
things in include/asm without being able to read the assembly output
in the first place.

David> I think the jury is out on this one.  Clearly it's a huge
David> benefit if you can make do without inline asm.  GCC has to make
David> lots of worst-case assumptions whenever it encounters an asm
David> statement and, due to macros and inlining, the asm statements
David> are not just hidden in a few leaf routines.

Reducing the amount of inline asm in the kernel would be a good
thing. It is cetainly one of those things that have been abused way
beyond it's intent.

Cheers,
Jes

  parent reply	other threads:[~2003-09-10 16:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-09 19:34 [Patch] asm workarounds in generic header files Siddha, Suresh B
2003-09-09 19:51 ` Jes Sorensen
2003-09-09 20:25   ` David Mosberger
2003-09-09 20:33     ` Linus Torvalds
2003-09-09 21:16       ` Sam Ravnborg
2003-09-09 23:44       ` David Mosberger
2003-09-10 16:22     ` Jes Sorensen [this message]
2003-09-10 17:02       ` David Mosberger
  -- strict thread matches above, loose matches on Subject: below --
2003-09-10  5:51 Nakajima, Jun
2003-09-10  4:50 Siddha, Suresh B
2003-09-10  5:08 ` Andrew Morton
2003-09-09  1:04 Siddha, Suresh B
2003-09-09  2:27 ` Jes Sorensen
2003-09-09  6:40 ` Christoph Hellwig

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=m3d6e8ipf6.fsf@trained-monkey.org \
    --to=jes@wildopensource.com \
    --cc=davidm@hpl.hp.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