From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Greg KH <greg@kroah.com>, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 6/7] s390: ipl device.
Date: Fri, 16 Sep 2005 10:39:09 +0200 [thread overview]
Message-ID: <1126859949.4923.21.camel@localhost.localdomain> (raw)
In-Reply-To: <20050916071444.GA11851@osiris.boeblingen.de.ibm.com>
On Fri, 2005-09-16 at 09:14 +0200, Heiko Carstens wrote:
> > > Export the ipl device settings to userspace via the sysfs:
> > > * /sys/kernel/ipl_device
> > What? Why that location? Why not in the proper location for your
> > device, on your bus?
>
> This interface tells from where the kernel was booted from. I don't
> think a device should have an attribute where the meaning would be
> "the current running kernel came via this device into memory".
> IMHO this should be an attribute of the kernel and therefore I
> thought /sys/kernel would be a good idea.
If the additional ipl information is bound to the ipl device then we'd
have to search for the device if we'd want to get the ipl information.
And if we ever want to make /sys/kernel/ipl_device writable to be able
to change the ipl_device for a reboot then what? Have the ipl related
sysfs files for ALL devices you can ipl from to be able to move to
another device? I think we need a central place for this information.
--
blue skies,
Martin
Martin Schwidefsky
Linux for zSeries Development & Services
IBM Deutschland Entwicklung GmbH
next prev parent reply other threads:[~2005-09-16 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 15:55 [patch 6/7] s390: ipl device Martin Schwidefsky
2005-09-15 17:17 ` Greg KH
2005-09-16 7:14 ` Heiko Carstens
2005-09-16 8:39 ` Martin Schwidefsky [this message]
2005-09-16 21:39 ` Greg KH
2005-09-19 8:59 ` Heiko Carstens
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=1126859949.4923.21.camel@localhost.localdomain \
--to=schwidefsky@de.ibm.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=heiko.carstens@de.ibm.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