public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Wankerl <sisewank@cip.cs.fau.de>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Sebastian Wankerl <sisewank@cip.cs.fau.de>,
	linux-kernel@vger.kernel.org,
	Philip Kranz <philip.kranz@googlemail.com>,
	i4passt@lists.informatik.uni-erlangen.de
Subject: Re: [PATCH] Add non-zero module sections to sysfs
Date: Thu, 04 Apr 2013 11:40:15 +0200	[thread overview]
Message-ID: <515D4A7F.5070102@cip.cs.fau.de> (raw)
In-Reply-To: <87mwtf3ya1.fsf@rustcorp.com.au>

On 04/04/13 03:00, Rusty Russell wrote:
> Sebastian Wankerl <sisewank@cip.cs.fau.de> writes:
>> Add non-zero module sections to sysfs on architectures unequal to PARISC.
>> KGDB needs all module sections for proper module debugging. Therefore, commit 
>> 35dead4235e2b67da7275b4122fed37099c2f462 is revoked except for PARISC
>> architecture.
> #ifdef CONFIG_PARISC in the middle of kernel/module.c is super-ugly, and
> wrong.

I don't see why this is wrong. It used to load all sections to sysfs
until the patch mentioned. Actually, it is the PARISC build chain which
is broken.

> My preference would be to fix kgdb.  If the section is empty, what need
> does it have to examine it?

GDB needs to know all sections of the binary and its addresses. It is
generally useful to be able to check up all sections of the binary
regardless if they are empty or not so one can see the binary's
structure. The alternative would be to redo the work by saving the ELF
header in an additional internal data structure that is not exported.
However, this approach is more ugly as it results in code which is
actually redundant.

Thanks,
Sebastian


  reply	other threads:[~2013-04-04  9:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03 13:08 [PATCH] Add non-zero module sections to sysfs Sebastian Wankerl
2013-04-04  1:00 ` Rusty Russell
2013-04-04  9:40   ` Sebastian Wankerl [this message]
2013-04-05  4:00     ` Rusty Russell
2013-04-05  9:40       ` Sebastian Wankerl
2013-04-05 10:07       ` James Bottomley
2013-04-06  4:52         ` Rusty Russell
2013-04-06 10:52           ` James Bottomley
2013-04-06 15:16             ` John David Anglin
2013-04-07  1:22               ` James Bottomley
2013-04-07  1:45                 ` John David Anglin
2013-04-06 10:40         ` Philip Kranz
2013-04-08  4:14           ` Rusty Russell
2013-04-08 11:55             ` Philip Kranz
2013-04-11 14:11             ` Philip Kranz
2013-04-05 14:56       ` Sebastian Wankerl
2013-04-06  4:31         ` Rusty Russell

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=515D4A7F.5070102@cip.cs.fau.de \
    --to=sisewank@cip.cs.fau.de \
    --cc=i4passt@lists.informatik.uni-erlangen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philip.kranz@googlemail.com \
    --cc=rusty@rustcorp.com.au \
    /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