From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: dake@staszic.waw.pl, linux-kernel@vger.kernel.org
Subject: Re: Patch(?): linux-2.4.0-test11-pre4/drivers/sound/yss225.c compilefailure
Date: Wed, 15 Nov 2000 00:29:15 -0500 [thread overview]
Message-ID: <3A121F2B.21DB3265@mandrakesoft.com> (raw)
In-Reply-To: <200011150102.RAA00924@adam.yggdrasil.com>
"Adam J. Richter" wrote:
> If a programmer errs in favor of __devinit, the result is
> extra memory consumption under CONFIG_HOTPLUG. If a programmer
> errs in favor of __init, the result is a crash during hot p
> ug insertion. Avoiding crashes at the expensive of a pretty small
> amount of memory usage is the more "conservative" way to err.
You suggest avoiding correctness in order to protect against dumb
programmers. That path leads to Windows.
> >Otherwise, you rob CONFIG_HOTPLUG people of some memory that could
> >otherwise be freed at boot. And the number of CONFIG_HOTPLUG people is
> >not small, it includes not only the CardBus users but USB users too...
>
> We have been discussing this on linux-devel-usb. The
> latest patches submitted to Linus and in 2.4.0-test10-pre{3,4}
> support USB hot plugging regardless of whether CONFIG_HOTPLUG is
> specified.
>
> bash% find linux-2.4.0-test11-pre4/drivers/usb -type f | xargs egrep HOTPLUG
Read the code. test11-pre[34] was broken due to my recent
CONFIG_KMOD/CONFIG_HOTPLUG separation, and should have had
CONFIG_HOTPLUG. test11-pre5 has CONFIG_HOTPLUG. As it should.
> Having USB hot plugging without needing to build in PCI
> hot plugging is useful,
Of course. But CONFIG_HOTPLUG does not mean PCI hotplugging. It means
any hotplug support in the kernel. That is why __devinit exists and is
used in a generic fashion.
> After 2.4.0, [...] we may
> want to explore adding __usbdevinit{,data} defines in include/linux/init.h
> that would be controlled by a new CONFIG_USB_HOTPLUG option, as in
> the patches that I posted for this to linux-usb-devel.
This is not just a USB issue. Please discuss this on linux-kernel, so
we can have a coherent hotplug strategy for the entire kernel.
If we are going to create CONFIG_USB_HOTPLUG, we must -eliminate-
CONFIG_HOTPLUG, and create CONFIG_PCI_HOTPLUG, and
CONFIG_ANOTHERBUS_HOTPLUG and so on, for each hotplug bus.
Jeff
--
Jeff Garzik |
Building 1024 | The chief enemy of creativity is "good" sense
MandrakeSoft | -- Picasso
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-15 6:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-15 1:02 Patch(?): linux-2.4.0-test11-pre4/drivers/sound/yss225.c compilefailure Adam J. Richter
2000-11-15 5:29 ` Jeff Garzik [this message]
2000-11-15 5:43 ` Greg KH
2000-11-15 5:54 ` Jeff Garzik
2000-11-15 6:03 ` College of Cardinals Vote!!! Andre Hedrick
2000-11-15 6:52 ` Patch(?): linux-2.4.0-test11-pre4/drivers/sound/yss225.c compilefailure Greg KH
-- strict thread matches above, loose matches on Subject: below --
2000-11-15 8:32 Adam J. Richter
2000-11-15 7:58 Adam J. Richter
2000-11-14 22:56 Patch(?): linux-2.4.0-test11-pre4/drivers/sound/yss225.c compile failure Bartlomiej Zolnierkiewicz
2000-11-14 23:01 ` Patch(?): linux-2.4.0-test11-pre4/drivers/sound/yss225.c compilefailure Jeff Garzik
2000-11-14 23:17 ` Bartlomiej Zolnierkiewicz
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=3A121F2B.21DB3265@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=adam@yggdrasil.com \
--cc=dake@staszic.waw.pl \
--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