mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: akpm@osdl.org, torvalds@osdl.org,
	linuxppc64-dev@lists.linuxppc.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dynamic addition of virtual disks on PPC64 iSeries
Date: Mon, 24 May 2004 17:36:16 +1000	[thread overview]
Message-ID: <20040524173616.3e8e3676.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1085383408.20577.7.camel@nighthawk>

[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]

On Mon, 24 May 2004 00:23:28 -0700 Dave Hansen <haveblue@us.ibm.com> wrote:
>
> On Mon, 2004-05-24 at 00:05, Stephen Rothwell wrote:
> > On Sun, 23 May 2004 23:29:20 -0700 Andrew Morton <akpm@osdl.org> wrote:
> > > Or to generate a hotplug event when a disk is added?  Even if there's no
> > > notification to the kernel, it should be possible to generate the hotplug
> > > events in response to a /proc-based trigger.
> > 
> > I guess that would be possible.  In this case I am trying to do the
> > minimum change.
> 
> I think this would be a worthy change.  It's the same kind of thing that
> we're planning for memory hotplug on ppc64: initiate a probe in /sys
> somewhere, and get a few hotplug events in short order.  The only
> difference is that we'll probably require a write for the probe to
> trigger.  You don't want a 'grep -r foo /sys' to cause probes, do you?

OK, I am convinced.  :-)  Now to learn about hotplug. :-(

> > +       printk(VIOD_KERN_INFO "disk %d: %lu sectors (%lu MB) "
> > +                       "CHS=%d/%d/%d sector size %d%s\n",
> > +                       dev_no, (unsigned long)(d->size >> 9),
> > +                       (unsigned long)(d->size >> 20),
> > +                       (int)d->cylinders, (int)d->tracks,
> > +                       (int)d->sectors, (int)d->bytes_per_sector,
> > +                       d->read_only ? " (RO)" : "");
> > +
> 
> Isn't it a little naughty to be spitting out so many values in a /sys
> file?  

Thats not the sys file ...

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-05-24  7:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-24  6:20 Stephen Rothwell
     [not found] ` <20040523232920.2fb0640a.akpm@osdl.org>
2004-05-24  7:05   ` Stephen Rothwell
2004-05-24  7:23     ` Dave Hansen
2004-05-24  7:36       ` Stephen Rothwell [this message]
2004-05-24  8:41   ` Stephen Rothwell
2004-05-24  8:49     ` Andrew Morton
2004-05-24 10:22       ` Stephen Rothwell
2004-05-24 11:50         ` Stephen Rothwell

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=20040524173616.3e8e3676.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@osdl.org \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@lists.linuxppc.org \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®