From: Arnd Bergmann <arnd@bergmann-dalldorf.de>
To: Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, schwidefsky@de.ibm.com
Subject: Re: [PATCH] s390 update (3/9): listing & kerntypes.
Date: Thu, 27 Mar 2003 00:20:07 +0100 [thread overview]
Message-ID: <200303262350.h2QNoqje015366@post.webmailer.de> (raw)
In-Reply-To: <20030326202006$09c8@gated-at.bofh.it>
Christoph Hellwig wrote:
> On Wed, Mar 26, 2003 at 05:32:12PM +0100, Martin Schwidefsky wrote:
>>
>> > No. Either we add Kerntypes to the architecture-independent code (I'm
>> all
>> > for it!) or not at all. Cludging this into s390-specific code is a very,
>> > very bad idea.
AFAIK, s390 is the only architecture that has hardware support for taking
system dumps without the lkcd patch. Since the lkcd patch does not
appear to be going into mainline linux and most s390 users want the
kerntypes anyway (every distributor includes them), arch/s390/boot
seems to be the right place to put them.
>> Well, even if the Kerntypes gets added to the architecture-independent code
>> we still would need some special s390 includes to get all the types we need.
>
> The patches from the lkcd folks don't seem to need additional includes.
> Please argue with them instead of trying to push such changes through the
> backdoor.
You need to include the struct definition for every data type that you
want lcrash to know about. E.g. if you want to analyse scsi structures
in a crash dump, you have to include drivers/scsi/scsi.h.
Most internal information about s390 devices is in structs defined
in drivers/s390/cio/, so we need them as well.
This is not an attempt to sneak the (mostly unrelated) lkcd patch in. If they
ever get included, we can still do a merge of the kerntypes file, but until
then it is just a tiny architecture special file that everybody else can
ignore.
Arnd <><
next parent reply other threads:[~2003-03-26 23:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030326164014$3fac@gated-at.bofh.it>
[not found] ` <20030326202006$09c8@gated-at.bofh.it>
2003-03-26 23:20 ` Arnd Bergmann [this message]
2003-03-27 8:44 ` Christoph Hellwig
2003-03-27 12:02 Martin Schwidefsky
-- strict thread matches above, loose matches on Subject: below --
2003-03-26 16:32 Martin Schwidefsky
2003-03-26 20:06 ` Christoph Hellwig
2003-03-26 15:07 Martin Schwidefsky
2003-03-26 15:42 ` 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=200303262350.h2QNoqje015366@post.webmailer.de \
--to=arnd@bergmann-dalldorf.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
/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
all inboxes | Powered by JetHome®