miniport driver - registry key access

NTDEV
1

Hi,

Can some one help me how to access registry keys from storport miniport driver? I want to access them from BuildIo or StartIo and DPC routines context. In WDK help there are no StorPort support routines to access registry keys.

The requirement is when user wants store some login information persistently, that needs to be stored by driver in registry. I think we should not call ZwOpenKey() and ZwSetValueKey() from miniport context. Any ideas on how to implement this would be greatly appreciated.

Thanks inadvance.

Regards,
Rama.

2

Regardless of what functions storport does or does not give you, you cannot touch the registry in a DPC routine. The registry can only be touched at IRQL == PASSIVE_LEVEL and DPC routines run at IRQL == DISPATCH_LEVEL. Looking at the docs for HwStorBuildIo, it is also called at IRQL == DISPATCH_LEVEL.

Can you read the values from the registry in DriverEntry or must these values be read dynamically at runtime and can change over the course of time?

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@yahoo.com
Sent: Tuesday, October 02, 2007 9:45 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] miniport driver - registry key access

Hi,

Can some one help me how to access registry keys from storport miniport driver? I want to access them from BuildIo or StartIo and DPC routines context. In WDK help there are no StorPort support routines to access registry keys.

The requirement is when user wants store some login information persistently, that needs to be stored by driver in registry. I think we should not call ZwOpenKey() and ZwSetValueKey() from miniport context. Any ideas on how to implement this would be greatly appreciated.

Thanks inadvance.

Regards,
Rama.

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

3

Hi Doron,

Thanks for the quick response. In the DriverEntry() I can read, but the requirement is I need to record/write the new entries also as and when user creates a persistent login entry through a WMI request or IOCTL. The requirement is for iSCSI HBA driver.

Will it work if I implement a filter driver for miniport and handle registry keys in filter driver?
With this approach will there be any issue for windows logo certification.

Regards,
Rama.

4

You can’t do this in a standard miniport driver. Whatever data you
needed from the registry had to be fetched in HwFindAdapter using the
ugly obscure registry interfaces. (See the ‘ArgumentString’ parameter.)
You can use more standard techniques in DriverEntry, but you will be
violating the storport api restrictions, which is fine with me but
eventually may be not so fine with WHQL. BuildIo and StartIO and your
DPC routines are executing at DIRQL and you cannot access the registry
at all at those levels in any driver.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@yahoo.com
Sent: Wednesday, October 03, 2007 12:45 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] miniport driver - registry key access

Hi,

Can some one help me how to access registry keys from storport miniport
driver? I want to access them from BuildIo or StartIo and DPC routines
context. In WDK help there are no StorPort support routines to access
registry keys.

The requirement is when user wants store some login information
persistently, that needs to be stored by driver in registry. I think we
should not call ZwOpenKey() and ZwSetValueKey() from miniport context.
Any ideas on how to implement this would be greatly appreciated.

Thanks inadvance.

Regards,
Rama.

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

5

Can we have a filter driver for miniport driver and handle registry key access at filter driver level?
Will WHQL accepts Miniport+filter driver combination for iSCSI HBA driver?

Regards,
Rama.

6

If your filter is going to have an interface with your miniport you will
be technically outside of the defined scsiport/storport architecture.
WHQL currently is not too strict about this. Certainly filter drivers
are legitimate, and you can create signed driver packages that include
and install filter drivers along with their WHQL’d driver.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@yahoo.com
Sent: Wednesday, October 03, 2007 11:12 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] miniport driver - registry key access

Can we have a filter driver for miniport driver and handle registry key
access at filter driver level?
Will WHQL accepts Miniport+filter driver combination for iSCSI HBA
driver?

Regards,
Rama.

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

7

Can I have a dedicated PASSIVE_LEVEL thread in miniport driver for registry access.
If WHQL is not strict about filter driver, why can’t WHQL allow the miniport drivers thread also to use Rtl-xx/Zw-xxx routines for registry access? Because filter driver or the miniport drivers thread would be serving the same purpose.

Regards,
Rama.

8

b/c the WHQL test does not detect the presence of the filter driver while the WHQL test can test the import in the miniport

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@yahoo.com
Sent: Thursday, October 04, 2007 9:00 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] miniport driver - registry key access

Can I have a dedicated PASSIVE_LEVEL thread in miniport driver for registry access.
If WHQL is not strict about filter driver, why can’t WHQL allow the miniport drivers thread also to use Rtl-xx/Zw-xxx routines for registry access? Because filter driver or the miniport drivers thread would be serving the same purpose.

Regards,
Rama.

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

9

Doron,
I just found StorPortRegistryRead() and StorPortRegistryWrite(), Can I use them in PASSIVE_LEVEL thread in miniport context, because these two are storport support routines which can be used in miniport driver.

Regards,
Rama.

10

Until Microsoft releases its virtual storport support there is no legitimate way to have passive level threads in your miniport. You’ve just pushed the problem around.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-302357-
xxxxx@lists.osr.com] On Behalf Of xxxxx@yahoo.com
Sent: Friday, October 05, 2007 6:01 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] miniport driver - registry key access

Doron,
I just found StorPortRegistryRead() and StorPortRegistryWrite(), Can I
use them in PASSIVE_LEVEL thread in miniport context, because these two
are storport support routines which can be used in miniport driver.

Regards,
Rama.

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer