mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Greg KH <greg@kroah.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
	akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 6/7] s390: ipl device.
Date: Fri, 16 Sep 2005 09:14:44 +0200	[thread overview]
Message-ID: <20050916071444.GA11851@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20050915171718.GA9833@kroah.com>

> > 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.

> >    Contains a string in on of the following formats:
> >    1) "ccw <bus_id>", or 2) "fcp <bus_id>,<wwpn>,<lun>".
> >  * /sys/kernel/ipl_parameter
> >    is a binary interface that exports the ipl  parameter block for
> >    scsi ipl. For non-scsi ipl the ipl_paramter is irrelevant.
> Again, put this in your device directory, not in /sys/kernel/

Same here.

> > +static ssize_t
> > +ipl_device_show(struct subsystem *subsys, char *page)
> > +{
> > +	struct ipl_parameter_block *ipl = IPL_PARMBLOCK_START;
> > +
> > +	if (!IPL_DEVNO_VALID)
> > +		goto type_unknown;
> > +	if (!IPL_PARMBLOCK_VALID)
> > +		goto type_ccw;
> > +	if (ipl->hdr.header.version > IPL_MAX_SUPPORTED_VERSION)
> > +		goto type_unknown;
> > +	if (ipl->fcp.pbt != IPL_TYPE_FCP)
> > +		goto type_unknown;
> > +
> > +	return sprintf(page, "fcp 0.0.%04x,0x%016llx,0x%016llx\n",
> > +		       ipl->fcp.devno,
> > +		       (unsigned long long) ipl->fcp.wwpn,
> > +		       (unsigned long long) ipl->fcp.lun);
> > + type_unknown:
> > +	return sprintf(page, "unknown\n");
> > + type_ccw:
> > +	return sprintf(page, "ccw 0.0.%04x\n",ipl_devno);
> 
> That doesn't look like a "single value" from a single file there.  Can't
> you break that up into individual files, based on what exactly is
> present at the time?

Sure, so I would end up with quite a few files:
always a file which tells the type of ipl e.g. ipl_type and dependent
on that additionally:
- in case of ccw ipl:
   just the bus_id of the ipl device (e.g. ipl_bus_id).
- in case of fcp ipl:
   the bus_id, the wwpn and the fcp_lun all exported via different files.

Does that sound reasonable?

Heiko

  reply	other threads:[~2005-09-16  7:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-14 15:55 Martin Schwidefsky
2005-09-15 17:17 ` Greg KH
2005-09-16  7:14   ` Heiko Carstens [this message]
2005-09-16  8:39     ` Martin Schwidefsky
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=20050916071444.GA11851@osiris.boeblingen.de.ibm.com \
    --to=heiko.carstens@de.ibm.com \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --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®