From cth@sac.sfbay.sun.com Sun Nov  2 18:23:19 2008
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mA32NIVX029038
	for <psarc-ext@sac.sfbay.sun.com>; Sun, 2 Nov 2008 18:23:18 -0800 (PST)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mA32NAMG018195;
	Mon, 3 Nov 2008 02:23:17 GMT
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K9Q00H07JYQBF00@nwk-avmta-2.sfbay.sun.com>; Sun,
 02 Nov 2008 18:23:14 -0800 (PST)
Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K9Q00FYLJYPFD90@nwk-avmta-2.sfbay.sun.com>; Sun,
 02 Nov 2008 18:23:13 -0800 (PST)
Received: from sac.sfbay.sun.com (new-sac.SFBay.Sun.COM [129.146.175.65])
	by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2)
 with ESMTP id mA32NDjV014679; Sun, 02 Nov 2008 18:23:13 -0800 (PST)
Received: from sac.sfbay.sun.com (localhost [127.0.0.1])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mA32NCle029012; Sun,
 02 Nov 2008 18:23:12 -0800 (PST)
Received: (from cth@localhost)	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit)
 id mA32NCAt029008; Sun, 02 Nov 2008 18:23:12 -0800 (PST)
Date: Sun, 02 Nov 2008 18:23:12 -0800 (PST)
From: Christopher Horne <cth@sac.sfbay.sun.com>
Subject: nulldriver [PSARC/2008/674 Self Review]
To: PSARC-ext@sun.com
Message-id: <200811030223.mA32NCAt029008@sac.sfbay.sun.com>
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
Status: RO
Content-Length: 6720

I am sponsoring the following fasttrack for myself.  Micro/patch
binding is requested.  I believe the case qualifies for self review,
and have filed it as Closed Approved Automatic.  If there is a request,
I'd be happy to convert it to a fasttrack and set the timer to enable
further discussion.

-Chris

1. Introduction
    1.1. Project/Component Working Name:
         nulldriver
    1.2. Name of Document Author/Supplier:
         Author:  Chris Horne
    1.3. Date of This Document:
	 Thu Oct 23 2008

4. Technical Description

4.1 Description

    A new 'nulldriver' driver is introduced. This driver succeeds
    probe(9E), attach(9E), and detach(9E) but provides no
    functionality.

    Only consolidation private use of this driver is proposed. Since no
    public use is proposed, this case is not providing a nulldriver(7D)
    manpage. Any future promotion of nulldriver will be responsible for
    documenting public use in nulldriver(7D).

    The nulldriver can be used in an number of private ways:

     A] To simplify nexus driver child discovery code: With nulldriver,
	a nexus driver's bus_config implementation [1] can implement
	dynamic child discovery by creating a child 'probe' devinfo
	node, bound to nulldriver, at the specific @unit-addresses
	associated with discovery. By promoting [2] this
	nulldriver-bound 'probe' node, nexus discovery code can reuse
	normal operation transport services for discovery. While
	nulldriver prevents external device access, a nexus driver can
	still internally use the transport services. Reuse of transport
	services for discovery results in significant simplification.

	In the case of SCSA, nulldriver enables nexus code to issue a
	REPORT_LUN command to lun 0 to discover luns. It also allows
	the discovery code to issue various forms of identity related
	INQUIRY commands (standard, page 0x80, and page 0x83) to
	determine the scsi(4) 'compatible' property forms [3] that
	apply to each reported lun, and lun devid/GUID information [4].

     B] Exclusions: Aliases that specify nulldriver can be used to
	represent exclusions. An example use would be to configure a
	system so a specific SCSI target driver remains unused on a
	given binding-set [3]: the ses(7D) driver should not be used on
	ATAPI.

		nulldriver "scsiclass,0d.batapi"

	The nulldriver allows exclusions to be implemented without
	incorporating that knowledge into target drivers.

     C] Hardware Disable: Access to a specific device can be disabled
	by establishing a path-oriented alias [5] to nulldriver.

	   # update_drv -a -i '"/pci@8,600000/SUNW,qlc@4"' nulldriver

	The above example would disable a specific Qlogic HBA.

     D] Accommodate Hardware Design Flaw: In this specific use, see [6]
	for details, a multi-function card was produced in a
	depopulated form, but the fact that the board was depopulated
	was not properly reflected in pci config space. While you could
	argue that this represents a hardware design flaw, such
	hardware was shipped before the flaw was noticed. The
	nulldriver could be used to siliently accommodate this type of
	errata.

     E] Aid: For some devices, the nulldriver can be used in
	conjunction with the lowest precedence 'compatible' form to
	ensure that devices lacking a driver binding still promote [2]
	above DS_LINKED.  Promotion causes the unit-address to be
	available in its more convenient string form: the @unit-address
	form used in /devices path components.  In this way,
	associating the lowest precedence alias with nulldriver can aid
	in establishing a more meaningful driver binding.

    The imminent intended private use of nulldriver is A]. The other
    use cases above are just informatinal at this point.

    Support for automatically changing driver binding as a result of
    alias additions (update_drv -a -i) and deletions (update_drv -d -i)
    without additional action (cfgadm(1M), modunload(1M), or reboot) is
    dependent on correct framework support. There have been issues in
    this area for a long time. While some progress has been made [5]
    (unbind_children), some issues still remain [8]. Ensuring complete
    correctness is beyond the scope of this proposal, but the remaining
    issues are being worked on.

    The nulldriver was previously proposed as part of [3], but there
    was some disagreement around its utility. I think that some of this
    resistance may have been related to framework deficiencies at the
    time related to dynamic alias modification support. In the interest
    of delivering on [3], and because nulldriver was not an integral
    part of that case, it was dropped from that proposal.

4.2 Proposed Interfaces

    ------------------------------------------------------------------
    Interface Name		Comm.Level	Comments
    ------------------------------------------------------------------

      nulldriver		Private		Driver that provides a
						'null' implementation.

      nulldriver_major		Private		major_t of nulldriver(7D).
						Used to suppress path_to_inst
						entries for nulldriver(7D)
						paths.

4.3 Release Binding

    Micro/patch binding is requested.

4.4 References

    [1] PSARC/2002/168	Bus Config
        http://sac.sfbay/PSARC/2002/168
        http://www.opensolaris.org/os/community/arc/caselog/2002/168

    [2] PSARC/2000/532	Devinfo State Model 
        http://sac.sfbay/PSARC/2000/532
        http://www.opensolaris.org/os/community/arc/caselog/2000/532

    [3] PSARC/2004/116	SCSI target compatible property
        http://sac.sfbay/PSARC/2004/116
        http://www.opensolaris.org/os/community/arc/caselog/2004/116

    [4] PSARC/2004/504	Common Devid/GUID Encode Interfaces for SCSI Devices
        http://sac.sfbay/PSARC/2004/504
        http://www.opensolaris.org/os/community/arc/caselog/2004/504

    [5] PSARC/2007/176	path-oriented driver alias
        http://sac.sfbay/PSARC/2007/176
        http://www.opensolaris.org/os/community/arc/caselog/2007/176

    [6] Bugs related to hardware that should not be used.
	5094257 No driver binding for X1033A during PCI hotplug
	http://monaco.sfbay.sun.com/detail.jsf?cr=5094257

    [7] Prtconf display of 'compatible'
	6502202 prtconf should display 'compatible'
	http://monaco.sfbay.sun.com/detail.jsf?cr=6502202

    [8] Bugs related to update_drv operation.
	4854243 update_drv -d requires reboot
	6464765 update_drv -d can remove other etnries than one specified
	6198348 update_drv: needs -n option
	http://monaco.sfbay.sun.com/detail.jsf?cr=4854243,6464765,6198348


6. Resources and Schedule
    6.4. Steering Committee requested information
   	6.4.1. Consolidation C-team Name:
		ON
    6.5. ARC review type: Automatic
    6.6. ARC Exposure: open


From gdamore@sun.com Sun Nov  2 21:34:27 2008
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mA35YRdn002552
	for <psarc-ext@sac.sfbay.sun.com>; Sun, 2 Nov 2008 21:34:27 -0800 (PST)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mA35YPxx024458
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Mon, 3 Nov 2008 05:34:26 GMT
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K9Q00407STAQP00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@Sun.Com); Sun, 02 Nov 2008 21:34:22 -0800 (PST)
Received: from sca-es-mail-1.sun.com ([192.18.43.132])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K9Q00055STAZE40@nwk-avmta-2.sfbay.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Sun,
 02 Nov 2008 21:34:22 -0800 (PST)
Received: from fe-sfbay-10.sun.com ([192.18.43.129])
	by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mA35YMrI001564	for
 <PSARC-ext@Sun.Com>; Sun, 02 Nov 2008 21:34:22 -0800 (PST)
Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0K9Q00601ST7UH00@fe-sfbay-10.sun.com> (original mail from gdamore@sun.com)
 for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Sun,
 02 Nov 2008 21:34:22 -0800 (PST)
Received: from [10.7.251.172] by fe-sfbay-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0K9Q00E68ST9R8E0@fe-sfbay-10.sun.com>; Sun,
 02 Nov 2008 21:34:21 -0800 (PST)
Date: Sun, 02 Nov 2008 21:29:34 -0800
From: "Garrett D'Amore" <gdamore@sun.com>
Subject: Re: nulldriver [PSARC/2008/674 Self Review]
In-reply-to: <200811030223.mA32NCAt029008@sac.sfbay.sun.com>
Sender: Garrett.Damore@sun.com
To: Christopher Horne <cth@sac.sfbay.sun.com>
Cc: PSARC-ext@sun.com
Message-id: <490E8C3E.2020806@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200811030223.mA32NCAt029008@sac.sfbay.sun.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080616)
Status: RO
Content-Length: 7776

+1

It turns out that I have used this approach for another use case, which 
is development of device drivers.  Having a driver like nulldriver in 
place (but suitably renamed) allows me to have enough stuff present to 
meet add_drv requirements, but doesn't require me to put stuff of 
questionable quality (e.g. early debug bits) on the filesystem itself.  
This can prevent a situation where a crash in the driver results in 
requiring external media (or fail-safe boot) ... because the "real" 
driver is loaded only from NFS after doing modunload of the null driver.

The details are probably beyond the scope of what we want to discuss in 
detail, but just thought it might provide an interesting data point.

    -- Garrett

Christopher Horne wrote:
> I am sponsoring the following fasttrack for myself.  Micro/patch
> binding is requested.  I believe the case qualifies for self review,
> and have filed it as Closed Approved Automatic.  If there is a request,
> I'd be happy to convert it to a fasttrack and set the timer to enable
> further discussion.
>
> -Chris
>
> 1. Introduction
>     1.1. Project/Component Working Name:
>          nulldriver
>     1.2. Name of Document Author/Supplier:
>          Author:  Chris Horne
>     1.3. Date of This Document:
> 	 Thu Oct 23 2008
>
> 4. Technical Description
>
> 4.1 Description
>
>     A new 'nulldriver' driver is introduced. This driver succeeds
>     probe(9E), attach(9E), and detach(9E) but provides no
>     functionality.
>
>     Only consolidation private use of this driver is proposed. Since no
>     public use is proposed, this case is not providing a nulldriver(7D)
>     manpage. Any future promotion of nulldriver will be responsible for
>     documenting public use in nulldriver(7D).
>
>     The nulldriver can be used in an number of private ways:
>
>      A] To simplify nexus driver child discovery code: With nulldriver,
> 	a nexus driver's bus_config implementation [1] can implement
> 	dynamic child discovery by creating a child 'probe' devinfo
> 	node, bound to nulldriver, at the specific @unit-addresses
> 	associated with discovery. By promoting [2] this
> 	nulldriver-bound 'probe' node, nexus discovery code can reuse
> 	normal operation transport services for discovery. While
> 	nulldriver prevents external device access, a nexus driver can
> 	still internally use the transport services. Reuse of transport
> 	services for discovery results in significant simplification.
>
> 	In the case of SCSA, nulldriver enables nexus code to issue a
> 	REPORT_LUN command to lun 0 to discover luns. It also allows
> 	the discovery code to issue various forms of identity related
> 	INQUIRY commands (standard, page 0x80, and page 0x83) to
> 	determine the scsi(4) 'compatible' property forms [3] that
> 	apply to each reported lun, and lun devid/GUID information [4].
>
>      B] Exclusions: Aliases that specify nulldriver can be used to
> 	represent exclusions. An example use would be to configure a
> 	system so a specific SCSI target driver remains unused on a
> 	given binding-set [3]: the ses(7D) driver should not be used on
> 	ATAPI.
>
> 		nulldriver "scsiclass,0d.batapi"
>
> 	The nulldriver allows exclusions to be implemented without
> 	incorporating that knowledge into target drivers.
>
>      C] Hardware Disable: Access to a specific device can be disabled
> 	by establishing a path-oriented alias [5] to nulldriver.
>
> 	   # update_drv -a -i '"/pci@8,600000/SUNW,qlc@4"' nulldriver
>
> 	The above example would disable a specific Qlogic HBA.
>
>      D] Accommodate Hardware Design Flaw: In this specific use, see [6]
> 	for details, a multi-function card was produced in a
> 	depopulated form, but the fact that the board was depopulated
> 	was not properly reflected in pci config space. While you could
> 	argue that this represents a hardware design flaw, such
> 	hardware was shipped before the flaw was noticed. The
> 	nulldriver could be used to siliently accommodate this type of
> 	errata.
>
>      E] Aid: For some devices, the nulldriver can be used in
> 	conjunction with the lowest precedence 'compatible' form to
> 	ensure that devices lacking a driver binding still promote [2]
> 	above DS_LINKED.  Promotion causes the unit-address to be
> 	available in its more convenient string form: the @unit-address
> 	form used in /devices path components.  In this way,
> 	associating the lowest precedence alias with nulldriver can aid
> 	in establishing a more meaningful driver binding.
>
>     The imminent intended private use of nulldriver is A]. The other
>     use cases above are just informatinal at this point.
>
>     Support for automatically changing driver binding as a result of
>     alias additions (update_drv -a -i) and deletions (update_drv -d -i)
>     without additional action (cfgadm(1M), modunload(1M), or reboot) is
>     dependent on correct framework support. There have been issues in
>     this area for a long time. While some progress has been made [5]
>     (unbind_children), some issues still remain [8]. Ensuring complete
>     correctness is beyond the scope of this proposal, but the remaining
>     issues are being worked on.
>
>     The nulldriver was previously proposed as part of [3], but there
>     was some disagreement around its utility. I think that some of this
>     resistance may have been related to framework deficiencies at the
>     time related to dynamic alias modification support. In the interest
>     of delivering on [3], and because nulldriver was not an integral
>     part of that case, it was dropped from that proposal.
>
> 4.2 Proposed Interfaces
>
>     ------------------------------------------------------------------
>     Interface Name		Comm.Level	Comments
>     ------------------------------------------------------------------
>
>       nulldriver		Private		Driver that provides a
> 						'null' implementation.
>
>       nulldriver_major		Private		major_t of nulldriver(7D).
> 						Used to suppress path_to_inst
> 						entries for nulldriver(7D)
> 						paths.
>
> 4.3 Release Binding
>
>     Micro/patch binding is requested.
>
> 4.4 References
>
>     [1] PSARC/2002/168	Bus Config
>         http://sac.sfbay/PSARC/2002/168
>         http://www.opensolaris.org/os/community/arc/caselog/2002/168
>
>     [2] PSARC/2000/532	Devinfo State Model 
>         http://sac.sfbay/PSARC/2000/532
>         http://www.opensolaris.org/os/community/arc/caselog/2000/532
>
>     [3] PSARC/2004/116	SCSI target compatible property
>         http://sac.sfbay/PSARC/2004/116
>         http://www.opensolaris.org/os/community/arc/caselog/2004/116
>
>     [4] PSARC/2004/504	Common Devid/GUID Encode Interfaces for SCSI Devices
>         http://sac.sfbay/PSARC/2004/504
>         http://www.opensolaris.org/os/community/arc/caselog/2004/504
>
>     [5] PSARC/2007/176	path-oriented driver alias
>         http://sac.sfbay/PSARC/2007/176
>         http://www.opensolaris.org/os/community/arc/caselog/2007/176
>
>     [6] Bugs related to hardware that should not be used.
> 	5094257 No driver binding for X1033A during PCI hotplug
> 	http://monaco.sfbay.sun.com/detail.jsf?cr=5094257
>
>     [7] Prtconf display of 'compatible'
> 	6502202 prtconf should display 'compatible'
> 	http://monaco.sfbay.sun.com/detail.jsf?cr=6502202
>
>     [8] Bugs related to update_drv operation.
> 	4854243 update_drv -d requires reboot
> 	6464765 update_drv -d can remove other etnries than one specified
> 	6198348 update_drv: needs -n option
> 	http://monaco.sfbay.sun.com/detail.jsf?cr=4854243,6464765,6198348
>
>
> 6. Resources and Schedule
>     6.4. Steering Committee requested information
>    	6.4.1. Consolidation C-team Name:
> 		ON
>     6.5. ARC review type: Automatic
>     6.6. ARC Exposure: open
>
>   


From Darren.Moffat@sun.com Mon Nov  3 01:43:21 2008
Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mA39hKVt009189
	for <psarc-ext@sac.sfbay.Sun.COM>; Mon, 3 Nov 2008 01:43:20 -0800 (PST)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id mA39gqXa028770
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Mon, 3 Nov 2008 17:43:19 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K9R0031Z4C2CC00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Mon, 03 Nov 2008 01:43:14 -0800 (PST)
Received: from gmp-eb-inf-1.sun.com ([192.18.6.21])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K9R00H424C1OS40@nwk-avmta-1.sfbay.Sun.COM> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon,
 03 Nov 2008 01:43:14 -0800 (PST)
Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe2.eu.sun.com [192.18.6.11])
	by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mA39hDnp025232	for
 <PSARC-ext@sun.com>; Mon, 03 Nov 2008 09:43:13 +0000 (GMT)
Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0K9R000012EBIN00@fe-emea-10.sun.com>
 (original mail from Darren.Moffat@Sun.COM)
 for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon,
 03 Nov 2008 09:43:13 +0000 (GMT)
Received: from [129.156.173.21] by fe-emea-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0K9R00GRT4BBSR80@fe-emea-10.sun.com>; Mon,
 03 Nov 2008 09:42:49 +0000 (GMT)
Date: Mon, 03 Nov 2008 09:42:47 +0000
From: Darren J Moffat <Darren.Moffat@sun.com>
Subject: Re: nulldriver [PSARC/2008/674 Self Review]
In-reply-to: <200811030223.mA32NCAt029008@sac.sfbay.sun.com>
Sender: Darren.Moffat@sun.com
To: Christopher Horne <cth@sac.sfbay.sun.com>
Cc: PSARC-ext@sun.com
Message-id: <490EC797.2040500@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200811030223.mA32NCAt029008@sac.sfbay.sun.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080922)
Status: RO
Content-Length: 127

I'd rather see a man page shipped even if it basically says "no user 
serviceable parts inside - go away".

--
Darren J Moffat

From ceri@submonkey.net Mon Nov  3 04:06:26 2008
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mA3C6QDs011901
	for <psarc-ext@sac.sfbay.sun.com>; Mon, 3 Nov 2008 04:06:26 -0800 (PST)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mA3C6OYV026417
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Mon, 3 Nov 2008 05:06:26 -0700 (MST)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K9R00J0NAYOE000@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Mon, 03 Nov 2008 04:06:24 -0800 (PST)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K9R00HMJAYOOSC0@nwk-avmta-1.sfbay.Sun.COM> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon,
 03 Nov 2008 04:06:24 -0800 (PST)
Received: from relay12i.sun.com
 (ip122.net129179-4.block1.us.syntegra.com [129.179.4.122])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mA3C6NC6001218	for
 <PSARC-ext@sun.com>; Mon, 03 Nov 2008 12:06:23 +0000 (GMT)
Received: from mmp14es.mmp.us.syntegra.com ([160.41.208.14] [160.41.208.14])
 by relay12i.sun.com with ESMTP id BT-MMP-327240 for PSARC-ext@sun.com; Mon,
 03 Nov 2008 12:06:23 +0000 (Z)
Received: from relay17i.sun.com (relay17i.sun.com [129.179.4.127])
 by mmp14es.mmp.us.syntegra.com with ESMTP id BT-MMP-198790 for
 PSARC-ext@sun.com; Mon, 03 Nov 2008 12:06:23 +0000 (Z)
Received: from scuttle.submonkey.net ([208.111.43.184] [208.111.43.184])
 by relay1ib.sun.com with ESMTP id BT-MMP-7674794 for PSARC-ext@sun.com; Mon,
 03 Nov 2008 12:06:22 +0000 (Z)
Received: from cpc1-cdif1-0-0-cust63.cdif.cable.ntl.com
 ([81.104.164.64] helo=shrike.submonkey.net)	by scuttle.submonkey.net with
 esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256)	(Exim 4.69)
	(envelope-from <ceri@submonkey.net>)	id 1KwyCM-0002O0-F2; Mon,
 03 Nov 2008 12:06:22 +0000
Received: from ceri by shrike.submonkey.net with local (Exim 4.69 (FreeBSD))
	(envelope-from <ceri@submonkey.net>)	id 1KwyCK-000GKD-CH; Mon,
 03 Nov 2008 12:06:20 +0000
Date: Mon, 03 Nov 2008 12:06:20 +0000
From: Ceri Davies <ceri@submonkey.net>
Subject: Re: nulldriver [PSARC/2008/674 Self Review]
In-reply-to: <200811030223.mA32NCAt029008@sac.sfbay.sun.com>
Sender: Ceri Davies <ceri@submonkey.net>
To: Christopher Horne <cth@sac.sfbay.sun.com>
Cc: PSARC-ext@sun.com
Message-id: <20081103120620.GB56353@submonkey.net>
MIME-version: 1.0
Content-type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature"; boundary="gr/z0/N6AeWAPJVB"
Content-disposition: inline
X-PMX-Version: 5.4.1.325704
X-Brightmail-Tracker: AAAAAA==
X-PGP: finger ceri@FreeBSD.org
X-Antispam: No, score=0.0/5.0, scanned in 0.109sec at (localhost [127.0.0.1])
	by smf-spamd v1.3.1 - http://smfs.sf.net/
References: <200811030223.mA32NCAt029008@sac.sfbay.sun.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Status: RO
Content-Length: 1443


--gr/z0/N6AeWAPJVB
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Nov 02, 2008 at 06:23:12PM -0800, Christopher Horne wrote:
> I am sponsoring the following fasttrack for myself.  Micro/patch
> binding is requested.  I believe the case qualifies for self review,
> and have filed it as Closed Approved Automatic.  If there is a request,
> I'd be happy to convert it to a fasttrack and set the timer to enable
> further discussion.
>=20
> -Chris
>=20
> 1. Introduction
>     1.1. Project/Component Working Name:
>          nulldriver
>     1.2. Name of Document Author/Supplier:
>          Author:  Chris Horne
>     1.3. Date of This Document:
> 	 Thu Oct 23 2008
>=20
> 4. Technical Description
>=20
> 4.1 Description
>=20
>     A new 'nulldriver' driver is introduced. This driver succeeds
>     probe(9E), attach(9E), and detach(9E) but provides no
>     functionality.

Does it need to support quiesce(9E) now that Fast Reboot exists?

Ceri
--=20
That must be wonderful!  I don't understand it at all.
                                                  -- Moliere

--gr/z0/N6AeWAPJVB
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)

iD8DBQFJDuk8ocfcwTS3JF8RApj6AKC16fW+7nU0MmPHaqLXcZmAaTINegCfZLCq
ew79IWARJW5zODhKo141H6s=
=JgI+
-----END PGP SIGNATURE-----

--gr/z0/N6AeWAPJVB--

From Chris.Horne@sun.com Mon Nov  3 07:05:20 2008
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mA3F5Khc007217
	for <psarc-ext@sac.sfbay.sun.com>; Mon, 3 Nov 2008 07:05:20 -0800 (PST)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mA3F5FBT022544
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Mon, 3 Nov 2008 08:05:20 -0700 (MST)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K9R00E7MJ8VRN00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@sun.com); Mon, 03 Nov 2008 07:05:19 -0800 (PST)
Received: from brmea-mail-3.sun.com ([192.18.98.34])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K9R000M1J8TQ4C0@nwk-avmta-1.sfbay.Sun.COM> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon,
 03 Nov 2008 07:05:17 -0800 (PST)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mA3F5H9L003969	for
 <PSARC-ext@sun.com>; Mon, 03 Nov 2008 15:05:17 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0K9R00601IIWM200@mail-amer.sun.com>
 (original mail from Chris.Horne@Sun.COM)
 for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Mon,
 03 Nov 2008 08:05:17 -0700 (MST)
Received: from sun.com ([129.150.32.56])
 by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28
 2007)) with ESMTPSA id <0K9R00HVZJ8G2Y90@mail-amer.sun.com>; Mon,
 03 Nov 2008 08:05:05 -0700 (MST)
Date: Mon, 03 Nov 2008 08:05:04 -0700
From: Chris Horne <Chris.Horne@sun.com>
Subject: Re: nulldriver [PSARC/2008/674 Self Review]
In-reply-to: <20081103120620.GB56353@submonkey.net>
Sender: Chris.Horne@sun.com
To: Ceri Davies <ceri@submonkey.net>
Cc: Christopher Horne <cth@sac.sfbay.sun.com>, PSARC-ext@sun.com
Message-id: <490F1320.6030703@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
X-PMX-Version: 5.4.1.325704
References: <200811030223.mA32NCAt029008@sac.sfbay.sun.com>
 <20081103120620.GB56353@submonkey.net>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4) Gecko/20040414
Status: RO
Content-Length: 315

Ceri

>>    A new 'nulldriver' driver is introduced. This driver succeeds
>>    probe(9E), attach(9E), and detach(9E) but provides no
>>    functionality.
> 
> Does it need to support quiesce(9E) now that Fast Reboot exists?

Thanks for the reminder, it will use ddi_quiesce_not_needed() for
devo_quiesce.

-Chris


From Chris.Horne@Sun.COM Mon Nov  3 13:50:43 2008
Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mA3LohmI019948
	for <psarc-ext@sac.sfbay.sun.com>; Mon, 3 Nov 2008 13:50:43 -0800 (PST)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mA3LohKc017742
	for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Mon, 3 Nov 2008 13:50:43 -0800 (PST)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0K9S00H0D20JZ000@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com
 (ORCPT PSARC-ext@Sun.COM); Mon, 03 Nov 2008 14:50:43 -0700 (MST)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0K9S007X920ISBD0@brm-avmta-1.central.sun.com> for
 PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Mon,
 03 Nov 2008 14:50:42 -0700 (MST)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mA3LogQN001165	for
 <PSARC-ext@Sun.COM>; Mon, 03 Nov 2008 21:50:42 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0K9S00H011ADIH00@mail-amer.sun.com>
 (original mail from Chris.Horne@Sun.COM)
 for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Mon,
 03 Nov 2008 14:50:42 -0700 (MST)
Received: from [172.20.25.50] by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0K9S002H220G35A0@mail-amer.sun.com>; Mon,
 03 Nov 2008 14:50:40 -0700 (MST)
Date: Mon, 03 Nov 2008 14:48:36 -0700
From: Chris Horne <Chris.Horne@Sun.COM>
Subject: Re: nulldriver [PSARC/2008/674 Self Review]
In-reply-to: <490EC797.2040500@Sun.COM>
Sender: Chris.Horne@Sun.COM
To: Darren J Moffat <Darren.Moffat@Sun.COM>
Cc: Christopher Horne <cth@sac.sfbay.sun.com>, PSARC-ext@Sun.COM
Message-id: <490F71B4.4080208@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200811030223.mA32NCAt029008@sac.sfbay.sun.com>
 <490EC797.2040500@Sun.COM>
User-Agent: Thunderbird 1.5.0.8 (X11/20061204)
Status: RO
Content-Length: 497

Darren
> I'd rather see a man page shipped even if it basically says "no user 
> serviceable parts inside - go away".
I have put a minimal nulldriver(7d) man page in the materials directory.
It communicates that having a devinfo node bound to nulldriver is normal,
at least in some circumstances, without going into details.
http://sac.eng/arc/PSARC/2008/674/materials/nulldriver.7d

This change implies a modification from 'private' to 'public'  for
'nulldriver' in the interface table.

-Chris


