mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: "Bjorn Helgaas" <bjorn.helgaas@hp.com>
Cc: linux-kernel@vger.kernel.org, ambx1@neo.rr.com,
	mm-commits@vger.kernel.org
Subject: Re: + pnp-mpu401-adjust-pnp_register_driver-signature.patch added  to -mm tree
Date: Thu, 02 Mar 2006 20:57:37 -0700	[thread overview]
Message-ID: <m1irqwgoy6.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <1084.24.9.204.52.1141357193.squirrel@mail.atl.hp.com> (Bjorn Helgaas's message of "Thu, 2 Mar 2006 20:39:53 -0700 (MST)")

"Bjorn Helgaas" <bjorn.helgaas@hp.com> writes:

>>> This series of patches removes the assumption that pnp_register_driver()
>>> returns the number of devices claimed.  Returning the count is
>>> unreliable
>>> because devices may be hot-plugged in the future.  (Many devices don't
>>> support
>>> hot-plug, of course, but PNP in general does.)
>>
>> Huh?
>>
>> How do onboard devices or ISA plug and play devices support hot-plug?
>>
>> Or what devices supported by the pnp subsystem support hot-plug?
>
> I don't know for sure whether ISAPNP or PNPBIOS support hot-plug,
> but ACPI does, and ACPI devices are being integrated into the
> PNP subsystem via PNPACPI.
>
> One example is HP sx2000 hardware that supports hot-plug of cells.
> Each cell contains CPUs, memory, I/O bridges, and some miscellaneous
> hardware like on-board serial devices.  All this stuff is described
> by ACPI, and we'd like to use PNP drivers like 8250_pnp.c when we can.

Ok, hot plug of motherboards.  The pieces fall together now for me.

Most things controlled by isapnp are either cold plug or not even
pluggable (like most serial ports).  So imaging them in a hot-plug
situation takes some effort.  But node/cell based NUMA systems
where you plug and unplug motherboards.  That make sense.

Eric


  reply	other threads:[~2006-03-03  4:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200603022340.k22Neq0o014875@shell0.pdx.osdl.net>
2006-03-03  0:55 ` Eric W. Biederman
2006-03-03  3:39   ` Bjorn Helgaas
2006-03-03  3:57     ` Eric W. Biederman [this message]
2006-03-03  6:58   ` Matthieu CASTET

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=m1irqwgoy6.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=ambx1@neo.rr.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@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

all inboxes | Powered by JetHome®