All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Sebastian Wankerl <sisewank@cip.cs.fau.de>
Cc: 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: Sat, 06 Apr 2013 15:01:43 +1030	[thread overview]
Message-ID: <87zjxcjn4g.fsf@rustcorp.com.au> (raw)
In-Reply-To: <515EE63A.6050307@cip.cs.fau.de>

Sebastian Wankerl <sisewank@cip.cs.fau.de> writes:
> On 04/05/13 06:00, Rusty Russell wrote:
>> Sebastian Wankerl <sisewank@cip.cs.fau.de> writes:
>>> 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.
>
> We worked on that topic further. Now we have another suggestion: would
> it be okay to add a field to struct module for use by kgdb where we save
> the section names for our use. This seems to be the most valuable
> solution as solving the sysfs stuff is rather hard.

It is hard.  But being a kernel hacker isn't just about making newbies
eat flaming death; sometimes we need to solve problems.

We'll see what we can do; but we'll continue this in the branch of the
thread that cc's linux-parisc...

Thanks,
Rusty.

      reply	other threads:[~2013-04-06  5:18 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
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 [this message]

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