From sacadmin Sun Jun  3 23:52:02 2007
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 l546q2hb015118;
	Sun, 3 Jun 2007 23:52:02 -0700 (PDT)
Received: (from eh146360@localhost)
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id l546q2op015114;
	Sun, 3 Jun 2007 23:52:02 -0700 (PDT)
Date: Sun, 3 Jun 2007 23:52:02 -0700 (PDT)
From: En-Hua Cecilia Hu <eh146360@sac.sfbay.sun.com>
Message-Id: <200706040652.l546q2op015114@sac.sfbay.sun.com>
To: PSARC-record@sac.sfbay.sun.com
Subject: New subclass for DR class events [PSARC/2007/326 FastTrack timeout 06/10/2007]
Status: RO
Content-Length: 543


Template Version: @(#)sac_nextcase 1.61 05/24/07 SMI
This information is Copyright 2007 Sun Microsystems
1. Introduction
    1.1. Project/Component Working Name:
	 New subclass for DR class events
    1.2. Name of Document Author/Supplier:
	 Author:  Dolpher Du/River Li
    1.3  Date of This Document:
	03 June, 2007
4. Technical Description
    See the case directory for more detail

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

From sacadmin Mon Jun  4 00:18:02 2007
Received: from sineb-mail-2.sun.com ([192.18.19.7])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l547I1XY016362
	for <psarc@sac.sfbay.sun.com>; Mon, 4 Jun 2007 00:18:02 -0700 (PDT)
Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged))
	by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l547GXiv003813
	for <psarc@sac.sfbay.sun.com>; Mon, 4 Jun 2007 07:16:33 GMT
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JJ300L01O2G7900@mail-apac.sun.com>
 (original mail from Cecilia.Hu@Sun.COM) for psarc@sac.sfbay.sun.com; Mon,
 04 Jun 2007 15:16:33 +0800 (SGT)
Received: from [129.158.218.120] by mail-apac.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPSA id <0JJ3003EJO7F1UV8@mail-apac.sun.com> for
 psarc@sac.sfbay.sun.com; Mon, 04 Jun 2007 15:16:28 +0800 (SGT)
Date: Mon, 04 Jun 2007 15:16:32 +0800
From: Cecilia Hu <Cecilia.Hu@Sun.COM>
Subject: PSARC 2007/326 New subclass for DR class events
Sender: Cecilia.Hu@Sun.COM
To: psarc@sac.sfbay.sun.com
Cc: yongfeng du <Yongfeng.Du@Sun.COM>, Ming Li <River.Li@Sun.COM>,
        "Dana H. Myers" <Dana.Myers@Sun.COM>
Reply-to: Cecilia.Hu@Sun.COM
Message-id: <4663BC50.2020900@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
User-Agent: Thunderbird 1.5.0.8 (X11/20061204)
Status: RO
Content-Length: 3348

I'm sponsoring this fast-track for Dolpher Du and River Li.
The requested release binding is micro/patch, timer is set
to 06/11/2007.

This project proposes to introduce a new subclass to EC_DR
event class so as to describe target status change.

-Cecilia



1. Introduction
    1.1. Project/Component Working Name:
	New subclass for DR class events

    1.2. Name of Document Author/Supplier:
	Author: Dolpher Du/River Li

    1.3. Date of This Document:
    	1 June, 2007

4. Technical Description:
1) Background
=============

    The sfx-4500 disk monitor, which  is used to monitor the  status of
    disk, requires  the mpt HBA driver  to generate notification events
    when sata  drives are removed  or inserted. The mpt  HBA controller
    hardware  provides  asynchronous message  mechanism  to notify  HBA
    driver  about target  hotplug. When  mpt HBA  driver  receives such
    messages, it should generate EC_DR events and reports them to upper
    level consumers.
	
2) Problem
==========

    The EC_DR  event class was  defined in PSARC 2000/189.  It contains
    two  subclasses:  ESC_DR_AP_STATE_CHANGE  and ESC_DR_REQ,  both  of
    which  are  designed  to  reflect  the  status  change  of  dynamic
    attachment   point.  The  dynamic   attachment  point   defined  in
    cfgadm(1M)  is  a  lun   based  conception  for  SCSI,  not  target
    based.  For the  SCSI/SAS HBAs  that are  target  status sensitive,
    those two type of events are not feasible since the host HBA driver
    can't get  the notification  of single lun  online or  offline from
    hardware  if the  target keeps  connection. In  other  respect, the
    existing  event subclasses  are not  convenient for  consumers that
    only care for target status change.

3) Solution
===========

    We propose a new subclass belonging  to the EC_DR class. It is used
    to describe target status change, and defined as following:
	
    ESC_DR_TARGET_STATE_CHANGE (per target state change event)
	
    Description		- Indicate a cable connection state change
    Commitment Level	- "Consolidation Private"

    Event Class		- EC_DR
    Event Sub-Class	- ESC_DR_TARGET_STATE_CHANGE
    Event Publisher	- SUNW:kern:<driver-name>
    Attribute Name	- TARGET_ID
    Attribute Type	- [SE_DATA_TYPE_STRING]
    Attribute Value	- </physical_path_to_hba:target>
    Attribute Name	- HINT
    Attribute Type	- [SE_DATA_TYPE_STRING]
    Attribute Value	- "" | "insert" | "remove" | ...	

    For example,  a sata disk is  connected to LSI  SAS controller, and
    marked as target 5. The physical  path of the LSI SAS controller is
    /devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@1.  When the sata
    disk  is   removed  physically,   mpt  driver  will   generate  the
    ESC_DR_TARGET_STATE_CHANGE   event.   Its   TARGET_ID  payload   is
    /devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@1:5,  and HINT is
    "remove".
	
    This event  will be first  used by mpt  driver, but the  concept of
    target id is not limited to  SCSI, it's common enough for other HBA
    drivers to use.

5. Reference Documents:
    PSARC 2000/189
    PSARC/1998/424

6. Resources and Schedule:
    6.4. Product Approval Committee requested information:
    	6.4.1. Consolidation or Component Name:
                ON
    6.5. ARC review type:
         FastTrack


From sacadmin Wed Jun  6 13:51:34 2007
Received: from sfbaymail1sca.SFBay.Sun.COM (sfbaymail1sca.SFBay.Sun.COM [129.145.154.35])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l56KpY5o021334
	for <psarc@sac.sfbay.sun.com>; Wed, 6 Jun 2007 13:51:34 -0700 (PDT)
Received: from sca-es-mail-1.sun.com (sca-es-mail-1.Sun.COM [192.18.43.132])
	by sfbaymail1sca.SFBay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l56Ko9dW025504
	for <psarc@sac.sfbay.sun.com>; Wed, 6 Jun 2007 13:50:09 -0700 (PDT)
Received: from fe-sfbay-09.sun.com ([192.18.43.129])
	by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l56Ko3qn000429
	for <psarc@sac.sfbay.sun.com>; Wed, 6 Jun 2007 13:50:03 -0700 (PDT)
Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JJ800201EYP0W00@fe-sfbay-09.sun.com>
 (original mail from Huay-Yong.Wang@Sun.COM) for psarc@sac.sfbay.sun.com; Wed,
 06 Jun 2007 13:50:03 -0700 (PDT)
Received: from [129.153.85.36] by fe-sfbay-09.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0JJ8008C6F7EXTH0@fe-sfbay-09.sun.com> for
 psarc@sac.sfbay.sun.com; Wed, 06 Jun 2007 13:50:03 -0700 (PDT)
Date: Wed, 06 Jun 2007 13:50:02 -0700
From: Huay-Yong.Wang@Sun.COM
Subject: Re: PSARC 2007/326 New subclass for DR class events
In-reply-to: <4663BC50.2020900@sun.com>
Sender: Huay-Yong.Wang@Sun.COM
To: Cecilia.Hu@Sun.COM, yongfeng du <Yongfeng.Du@Sun.COM>,
        Ming Li <River.Li@Sun.COM>
Cc: psarc@sac.sfbay.sun.com, "Dana H. Myers" <Dana.Myers@Sun.COM>
Message-id: <46671DFA.4040108@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
References: <4663BC50.2020900@sun.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20070109
Status: RO
Content-Length: 4366


Will this effort address the issue in the PICL
framework where the SCSI/SAS disk targets picl status are
not updated upon hot insert/removal? Please see
CR 6526184.

Regarding the PICL framework, currently the generic
PICL syseventd module filter out all but 3 sysevents.
The 3 events delivered to PICL are:

  - PICLEVENT_SYSEVENT_DEVICE_ADDED (EC_DEVFS, ESC_DEVFS_DEVI_ADD)
  - PICLEVENT_SYSEVENT_DEVICE_REMOVED (EC_DEVFS, ESC_DEVFS_DEVI_REMOVE)
  - PICLEVENT_DR_AP_STATE_CHANGE (EC_DR, ESC_DR_AP_STATE_CHANGE)

For this case, I see that you are proposing a set of new EC_DR subclass.
I want to make sure that this proposal is generic enough
to address the PICL update for SAS/mpt hot insert/removal.
(preferably without the need to change  PICL framework code)

Cecilia Hu wrote:

> I'm sponsoring this fast-track for Dolpher Du and River Li.
> The requested release binding is micro/patch, timer is set
> to 06/11/2007.
>
> This project proposes to introduce a new subclass to EC_DR
> event class so as to describe target status change.
>
> -Cecilia
>
>
>
> 1. Introduction
>     1.1. Project/Component Working Name:
>     New subclass for DR class events
>
>     1.2. Name of Document Author/Supplier:
>     Author: Dolpher Du/River Li
>
>     1.3. Date of This Document:
>         1 June, 2007
>
> 4. Technical Description:
> 1) Background
> =============
>
>     The sfx-4500 disk monitor, which  is used to monitor the  status of
>     disk, requires  the mpt HBA driver  to generate notification events
>     when sata  drives are removed  or inserted. The mpt  HBA controller
>     hardware  provides  asynchronous message  mechanism  to notify  HBA
>     driver  about target  hotplug. When  mpt HBA  driver  receives such
>     messages, it should generate EC_DR events and reports them to upper
>     level consumers.
>     
> 2) Problem
> ==========
>
>     The EC_DR  event class was  defined in PSARC 2000/189.  It contains
>     two  subclasses:  ESC_DR_AP_STATE_CHANGE  and ESC_DR_REQ,  both  of
>     which  are  designed  to  reflect  the  status  change  of  dynamic
>     attachment   point.  The  dynamic   attachment  point   defined  in
>     cfgadm(1M)  is  a  lun   based  conception  for  SCSI,  not  target
>     based.  For the  SCSI/SAS HBAs  that are  target  status sensitive,
>     those two type of events are not feasible since the host HBA driver
>     can't get  the notification  of single lun  online or  offline from
>     hardware  if the  target keeps  connection. In  other  respect, the
>     existing  event subclasses  are not  convenient for  consumers that
>     only care for target status change.
>
> 3) Solution
> ===========
>
>     We propose a new subclass belonging  to the EC_DR class. It is used
>     to describe target status change, and defined as following:
>     
>     ESC_DR_TARGET_STATE_CHANGE (per target state change event)
>     
>     Description        - Indicate a cable connection state change
>     Commitment Level    - "Consolidation Private"
>
>     Event Class        - EC_DR
>     Event Sub-Class    - ESC_DR_TARGET_STATE_CHANGE
>     Event Publisher    - SUNW:kern:<driver-name>
>     Attribute Name    - TARGET_ID
>     Attribute Type    - [SE_DATA_TYPE_STRING]
>     Attribute Value    - </physical_path_to_hba:target>
>     Attribute Name    - HINT
>     Attribute Type    - [SE_DATA_TYPE_STRING]
>     Attribute Value    - "" | "insert" | "remove" | ...   
>
>     For example,  a sata disk is  connected to LSI  SAS controller, and
>     marked as target 5. The physical  path of the LSI SAS controller is
>     /devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@1.  When the sata
>     disk  is   removed  physically,   mpt  driver  will   generate  the
>     ESC_DR_TARGET_STATE_CHANGE   event.   Its   TARGET_ID  payload   is
>     /devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@1:5,  and HINT is
>     "remove".
>     
>     This event  will be first  used by mpt  driver, but the  concept of
>     target id is not limited to  SCSI, it's common enough for other HBA
>     drivers to use.
>
> 5. Reference Documents:
>     PSARC 2000/189
>     PSARC/1998/424
>
> 6. Resources and Schedule:
>     6.4. Product Approval Committee requested information:
>         6.4.1. Consolidation or Component Name:
>                 ON
>     6.5. ARC review type:
>          FastTrack
>


From sacadmin Wed Jun  6 19:35:02 2007
Received: from dm-singapore-01.singapore.sun.com (dm-singapore-01.Singapore.Sun.COM [129.158.71.101])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l572Z1bo001626
	for <psarc@sac.sfbay.sun.com>; Wed, 6 Jun 2007 19:35:01 -0700 (PDT)
Received: from sineb-smtp-1.singapore.sun.com (sineb-smtp-1 [129.158.123.4])
	by dm-singapore-01.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id l572XYq2013564
	for <psarc@sac.sfbay.sun.com>; Thu, 7 Jun 2007 10:33:34 +0800 (SGT)
Received: from phys-sedge1-1.singapore.sun.com (phys-sedge1-1.Singapore.Sun.COM [129.158.123.8])
	by sineb-smtp-1.singapore.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l572ioSW014434
	for <psarc@sac.sfbay.sun.com>; Thu, 7 Jun 2007 02:44:50 GMT
Received: from [129.158.218.218] by sedge1-mail1.singapore.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 with ESMTPA id <0JJ800AHYV3S7AD0@sedge1-mail1.singapore.sun.com> for
 psarc@sac.sfbay.sun.com; Thu, 07 Jun 2007 10:33:29 +0800 (SGT)
Date: Thu, 07 Jun 2007 10:31:43 +0800
From: yongfeng du <Yongfeng.Du@Sun.COM>
Subject: Re: PSARC 2007/326 New subclass for DR class events
In-reply-to: <46671DFA.4040108@Sun.COM>
To: Huay-Yong.Wang@Sun.COM
Cc: Cecilia.Hu@Sun.COM, Ming Li <River.Li@Sun.COM>, psarc@sac.sfbay.sun.com,
        "Dana H. Myers" <Dana.Myers@Sun.COM>
Message-id: <46676E0F.3060804@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
References: <4663BC50.2020900@sun.com> <46671DFA.4040108@Sun.COM>
User-Agent: Thunderbird 1.5.0.8 (X11/20061204)
Status: RO
Content-Length: 5230

This proposal is generic enough for PICL to use.
You could use this new event the same way as ESC_DR_AP_STATE_CHANGE,
just keep in mind the payload is a little different (Target ID vs AP ID).
The ESC_DR_AP_STATE_CHANGE will not be implemented in mpt since
the AP_ID is not feasible for HBA driver.

For the CR 6526184, it can be solved by using of this new proposed event.

There is another case that might help CR 6526184, see
PSARC/2006/703 section 4.7 Dynamic target change capability
Mpt driver will configure/unconfigure the target automatically according 
to the hardware events,
independent of the cfgadm(1M). There would be EC_DEVFS events generated 
on successfully
configuration/unconfiguration.

Thanks,
Dolpher

Huay-Yong.Wang@Sun.COM wrote:
>
> Will this effort address the issue in the PICL
> framework where the SCSI/SAS disk targets picl status are
> not updated upon hot insert/removal? Please see
> CR 6526184.
>
> Regarding the PICL framework, currently the generic
> PICL syseventd module filter out all but 3 sysevents.
> The 3 events delivered to PICL are:
>
>  - PICLEVENT_SYSEVENT_DEVICE_ADDED (EC_DEVFS, ESC_DEVFS_DEVI_ADD)
>  - PICLEVENT_SYSEVENT_DEVICE_REMOVED (EC_DEVFS, ESC_DEVFS_DEVI_REMOVE)
>  - PICLEVENT_DR_AP_STATE_CHANGE (EC_DR, ESC_DR_AP_STATE_CHANGE)
>
> For this case, I see that you are proposing a set of new EC_DR subclass.
> I want to make sure that this proposal is generic enough
> to address the PICL update for SAS/mpt hot insert/removal.
> (preferably without the need to change  PICL framework code)
>
> Cecilia Hu wrote:
>
>> I'm sponsoring this fast-track for Dolpher Du and River Li.
>> The requested release binding is micro/patch, timer is set
>> to 06/11/2007.
>>
>> This project proposes to introduce a new subclass to EC_DR
>> event class so as to describe target status change.
>>
>> -Cecilia
>>
>>
>>
>> 1. Introduction
>>     1.1. Project/Component Working Name:
>>     New subclass for DR class events
>>
>>     1.2. Name of Document Author/Supplier:
>>     Author: Dolpher Du/River Li
>>
>>     1.3. Date of This Document:
>>         1 June, 2007
>>
>> 4. Technical Description:
>> 1) Background
>> =============
>>
>>     The sfx-4500 disk monitor, which  is used to monitor the  status of
>>     disk, requires  the mpt HBA driver  to generate notification events
>>     when sata  drives are removed  or inserted. The mpt  HBA controller
>>     hardware  provides  asynchronous message  mechanism  to notify  HBA
>>     driver  about target  hotplug. When  mpt HBA  driver  receives such
>>     messages, it should generate EC_DR events and reports them to upper
>>     level consumers.
>>     2) Problem
>> ==========
>>
>>     The EC_DR  event class was  defined in PSARC 2000/189.  It contains
>>     two  subclasses:  ESC_DR_AP_STATE_CHANGE  and ESC_DR_REQ,  both  of
>>     which  are  designed  to  reflect  the  status  change  of  dynamic
>>     attachment   point.  The  dynamic   attachment  point   defined  in
>>     cfgadm(1M)  is  a  lun   based  conception  for  SCSI,  not  target
>>     based.  For the  SCSI/SAS HBAs  that are  target  status sensitive,
>>     those two type of events are not feasible since the host HBA driver
>>     can't get  the notification  of single lun  online or  offline from
>>     hardware  if the  target keeps  connection. In  other  respect, the
>>     existing  event subclasses  are not  convenient for  consumers that
>>     only care for target status change.
>>
>> 3) Solution
>> ===========
>>
>>     We propose a new subclass belonging  to the EC_DR class. It is used
>>     to describe target status change, and defined as following:
>>         ESC_DR_TARGET_STATE_CHANGE (per target state change event)
>>         Description        - Indicate a cable connection state change
>>     Commitment Level    - "Consolidation Private"
>>
>>     Event Class        - EC_DR
>>     Event Sub-Class    - ESC_DR_TARGET_STATE_CHANGE
>>     Event Publisher    - SUNW:kern:<driver-name>
>>     Attribute Name    - TARGET_ID
>>     Attribute Type    - [SE_DATA_TYPE_STRING]
>>     Attribute Value    - </physical_path_to_hba:target>
>>     Attribute Name    - HINT
>>     Attribute Type    - [SE_DATA_TYPE_STRING]
>>     Attribute Value    - "" | "insert" | "remove" | ...  
>>     For example,  a sata disk is  connected to LSI  SAS controller, and
>>     marked as target 5. The physical  path of the LSI SAS controller is
>>     /devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@1.  When the sata
>>     disk  is   removed  physically,   mpt  driver  will   generate  the
>>     ESC_DR_TARGET_STATE_CHANGE   event.   Its   TARGET_ID  payload   is
>>     /devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@1:5,  and HINT is
>>     "remove".
>>         This event  will be first  used by mpt  driver, but the  
>> concept of
>>     target id is not limited to  SCSI, it's common enough for other HBA
>>     drivers to use.
>>
>> 5. Reference Documents:
>>     PSARC 2000/189
>>     PSARC/1998/424
>>
>> 6. Resources and Schedule:
>>     6.4. Product Approval Committee requested information:
>>         6.4.1. Consolidation or Component Name:
>>                 ON
>>     6.5. ARC review type:
>>          FastTrack
>>
>

From sacadmin Wed Jun  6 19:54:38 2007
Received: from sineb-mail-1.sun.com ([192.18.19.6])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l572sbMB002664
	for <psarc@sac.sfbay.sun.com>; Wed, 6 Jun 2007 19:54:38 -0700 (PDT)
Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged))
	by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l572r6CI015272
	for <psarc@sac.sfbay.sun.com>; Thu, 7 Jun 2007 02:53:06 GMT
Received: from sun.com ([129.158.123.14])
 by mail-apac.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr  3
 2006)) with ESMTP id <0JJ800DMYW0I95RC@mail-apac.sun.com> for
 psarc@sac.sfbay.sun.com; Thu, 07 Jun 2007 10:53:06 +0800 (SGT)
Received: from [192.18.19.175] (Forwarded-For: [129.158.71.40])
 by sedge2-mail1.singapore.sun.com (mshttpd); Thu, 07 Jun 2007 10:53:06 +0800
Date: Thu, 07 Jun 2007 10:53:06 +0800
From: En-Hua Cecilia Hu <Cecilia.Hu@Sun.COM>
Subject: Re: PSARC 2007/326 New subclass for DR class events
In-reply-to: <46676E0F.3060804@sun.com>
To: yongfeng du <Yongfeng.Du@Sun.COM>
Cc: Huay-Yong.Wang@Sun.COM, Ming Li <River.Li@Sun.COM>,
        psarc@sac.sfbay.sun.com, "Dana H. Myers" <Dana.Myers@Sun.COM>
Message-id: <fcc6dddd74dd.4667e392@sun.com>
MIME-version: 1.0
X-Mailer: Sun Java(tm) System Messenger Express 6.2-6.01 (built Apr  3 2006)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
Priority: normal
References: <4663BC50.2020900@sun.com> <46671DFA.4040108@Sun.COM>
 <46676E0F.3060804@sun.com>
Status: RO
Content-Length: 70

FYI.

This fasttrack was approved at today's PSARC meeting.

-Cecilia

From sacadmin Thu Jun  7 09:27:15 2007
Received: from sfbaymail1sca.SFBay.Sun.COM (sfbaymail1sca.SFBay.Sun.COM [129.145.154.35])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id l57GRFci016359
	for <psarc@sac.sfbay.sun.com>; Thu, 7 Jun 2007 09:27:15 -0700 (PDT)
Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36])
	by sfbaymail1sca.SFBay.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with ESMTP id l57GPmEQ009906
	for <psarc@sac.sfbay.sun.com>; Thu, 7 Jun 2007 09:25:49 -0700 (PDT)
Received: from fe-amer-06.sun.com ([192.18.108.180])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l57GPm8R003178
	for <psarc@sac.sfbay.sun.com>; Thu, 7 Jun 2007 16:25:48 GMT
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java System Messaging Server 6.2-6.01 (built Apr  3 2006))
 id <0JJ900J01XGYS200@mail-amer.sun.com>
 (original mail from Huay-Yong.Wang@Sun.COM) for psarc@sac.sfbay.sun.com; Thu,
 07 Jun 2007 10:25:48 -0600 (MDT)
Received: from [192.168.1.2] ([71.154.212.76])
 by mail-amer.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr  3
 2006)) with ESMTPSA id <0JJ9001W6XMVQD12@mail-amer.sun.com> for
 psarc@sac.sfbay.sun.com; Thu, 07 Jun 2007 10:25:48 -0600 (MDT)
Date: Thu, 07 Jun 2007 09:25:39 -0700
From: Huay-Yong Wang <Huay-Yong.Wang@Sun.COM>
Subject: Re: PSARC 2007/326 New subclass for DR class events
In-reply-to: <46676E0F.3060804@sun.com>
Sender: Huay-Yong.Wang@Sun.COM
To: yongfeng du <Yongfeng.Du@Sun.COM>
Cc: Cecilia.Hu@Sun.COM, Ming Li <River.Li@Sun.COM>, psarc@sac.sfbay.sun.com,
        "Dana H. Myers" <Dana.Myers@Sun.COM>
Message-id: <46683183.6010705@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
References: <4663BC50.2020900@sun.com> <46671DFA.4040108@Sun.COM>
 <46676E0F.3060804@sun.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.13)
 Gecko/20060414
Status: RO
Content-Length: 5654

yongfeng du wrote:
> This proposal is generic enough for PICL to use.
> You could use this new event the same way as ESC_DR_AP_STATE_CHANGE,
> just keep in mind the payload is a little different (Target ID vs AP ID).
> The ESC_DR_AP_STATE_CHANGE will not be implemented in mpt since
> the AP_ID is not feasible for HBA driver.
> 
> For the CR 6526184, it can be solved by using of this new proposed event.
> 
> There is another case that might help CR 6526184, see
> PSARC/2006/703 section 4.7 Dynamic target change capability
> Mpt driver will configure/unconfigure the target automatically according 
> to the hardware events,
> independent of the cfgadm(1M). There would be EC_DEVFS events generated 
> on successfully
> configuration/unconfiguration.

My point is that since you are adding functionality to
generate events for mpt detected hardware events (hot insert/removal),
it make sense to ensure PICL framework benefit from it.
If you are generating EC_DEVFS events, that will work too.
Thanks.

> 
> Thanks,
> Dolpher
> 
> Huay-Yong.Wang@Sun.COM wrote:
> 
>>
>> Will this effort address the issue in the PICL
>> framework where the SCSI/SAS disk targets picl status are
>> not updated upon hot insert/removal? Please see
>> CR 6526184.
>>
>> Regarding the PICL framework, currently the generic
>> PICL syseventd module filter out all but 3 sysevents.
>> The 3 events delivered to PICL are:
>>
>>  - PICLEVENT_SYSEVENT_DEVICE_ADDED (EC_DEVFS, ESC_DEVFS_DEVI_ADD)
>>  - PICLEVENT_SYSEVENT_DEVICE_REMOVED (EC_DEVFS, ESC_DEVFS_DEVI_REMOVE)
>>  - PICLEVENT_DR_AP_STATE_CHANGE (EC_DR, ESC_DR_AP_STATE_CHANGE)
>>
>> For this case, I see that you are proposing a set of new EC_DR subclass.
>> I want to make sure that this proposal is generic enough
>> to address the PICL update for SAS/mpt hot insert/removal.
>> (preferably without the need to change  PICL framework code)
>>
>> Cecilia Hu wrote:
>>
>>> I'm sponsoring this fast-track for Dolpher Du and River Li.
>>> The requested release binding is micro/patch, timer is set
>>> to 06/11/2007.
>>>
>>> This project proposes to introduce a new subclass to EC_DR
>>> event class so as to describe target status change.
>>>
>>> -Cecilia
>>>
>>>
>>>
>>> 1. Introduction
>>>     1.1. Project/Component Working Name:
>>>     New subclass for DR class events
>>>
>>>     1.2. Name of Document Author/Supplier:
>>>     Author: Dolpher Du/River Li
>>>
>>>     1.3. Date of This Document:
>>>         1 June, 2007
>>>
>>> 4. Technical Description:
>>> 1) Background
>>> =============
>>>
>>>     The sfx-4500 disk monitor, which  is used to monitor the  status of
>>>     disk, requires  the mpt HBA driver  to generate notification events
>>>     when sata  drives are removed  or inserted. The mpt  HBA controller
>>>     hardware  provides  asynchronous message  mechanism  to notify  HBA
>>>     driver  about target  hotplug. When  mpt HBA  driver  receives such
>>>     messages, it should generate EC_DR events and reports them to upper
>>>     level consumers.
>>>     2) Problem
>>> ==========
>>>
>>>     The EC_DR  event class was  defined in PSARC 2000/189.  It contains
>>>     two  subclasses:  ESC_DR_AP_STATE_CHANGE  and ESC_DR_REQ,  both  of
>>>     which  are  designed  to  reflect  the  status  change  of  dynamic
>>>     attachment   point.  The  dynamic   attachment  point   defined  in
>>>     cfgadm(1M)  is  a  lun   based  conception  for  SCSI,  not  target
>>>     based.  For the  SCSI/SAS HBAs  that are  target  status sensitive,
>>>     those two type of events are not feasible since the host HBA driver
>>>     can't get  the notification  of single lun  online or  offline from
>>>     hardware  if the  target keeps  connection. In  other  respect, the
>>>     existing  event subclasses  are not  convenient for  consumers that
>>>     only care for target status change.
>>>
>>> 3) Solution
>>> ===========
>>>
>>>     We propose a new subclass belonging  to the EC_DR class. It is used
>>>     to describe target status change, and defined as following:
>>>         ESC_DR_TARGET_STATE_CHANGE (per target state change event)
>>>         Description        - Indicate a cable connection state change
>>>     Commitment Level    - "Consolidation Private"
>>>
>>>     Event Class        - EC_DR
>>>     Event Sub-Class    - ESC_DR_TARGET_STATE_CHANGE
>>>     Event Publisher    - SUNW:kern:<driver-name>
>>>     Attribute Name    - TARGET_ID
>>>     Attribute Type    - [SE_DATA_TYPE_STRING]
>>>     Attribute Value    - </physical_path_to_hba:target>
>>>     Attribute Name    - HINT
>>>     Attribute Type    - [SE_DATA_TYPE_STRING]
>>>     Attribute Value    - "" | "insert" | "remove" | ...      For 
>>> example,  a sata disk is  connected to LSI  SAS controller, and
>>>     marked as target 5. The physical  path of the LSI SAS controller is
>>>     /devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@1.  When the sata
>>>     disk  is   removed  physically,   mpt  driver  will   generate  the
>>>     ESC_DR_TARGET_STATE_CHANGE   event.   Its   TARGET_ID  payload   is
>>>     /devices/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@1:5,  and HINT is
>>>     "remove".
>>>         This event  will be first  used by mpt  driver, but the  
>>> concept of
>>>     target id is not limited to  SCSI, it's common enough for other HBA
>>>     drivers to use.
>>>
>>> 5. Reference Documents:
>>>     PSARC 2000/189
>>>     PSARC/1998/424
>>>
>>> 6. Resources and Schedule:
>>>     6.4. Product Approval Committee requested information:
>>>         6.4.1. Consolidation or Component Name:
>>>                 ON
>>>     6.5. ARC review type:
>>>          FastTrack
>>>
>>


