What’s the difference between these two routines? I want to register an MSIx interrupt handler. If I understand things correctly I should make a call to one of these routines with the appropriate messageID to determine if Windows granted me the vector during my HW_Initialize routine. It looks like they both map to the same storport extended function, but I just want to be sure. Anyone have the answer?
Hmmm. What version of the WDK are you using? I know nothing about StorPort (or storage for that
matter), but I don’t see the second one mentioned in the 7000.0 WDK.
mm
xxxxx@intel.com wrote:
What’s the difference between these two routines? I want to register an MSIx interrupt handler. If I understand things correctly I should make a call to one of these routines with the appropriate messageID to determine if Windows granted me the vector during my HW_Initialize routine. It looks like they both map to the same storport extended function, but I just want to be sure. Anyone have the answer?
I suspect that StorPortGetMessageInterruptInformation morphed into
StorPortGetMSIInfo the only reference to former that I can find is the
WinHEC 2006 slide deck on storage futures.
–
Don Burn (MVP, Windows DDK)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
wrote in message news:xxxxx@ntdev…
> What’s the difference between these two routines? I want to register an
> MSIx interrupt handler. If I understand things correctly I should make a
> call to one of these routines with the appropriate messageID to determine
> if Windows granted me the vector during my HW_Initialize routine. It
> looks like they both map to the same storport extended function, but I
> just want to be sure. Anyone have the answer?
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 3956 (20090323)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
Information from ESET NOD32 Antivirus, version of virus signature database 3957 (20090324)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
I have no idea of what this means, but they do both appear in storport.h
mm
Don Burn wrote:
I suspect that StorPortGetMessageInterruptInformation morphed into
StorPortGetMSIInfo the only reference to former that I can find is the
WinHEC 2006 slide deck on storage futures.
One (StorPortGetMSIInfo) is a “StorPortExtendedFunction” while the
other is a native storport API. This allows one to write a single
storport driver binary that will run on W2K3 without MSI support and
W2K8 with MSI support, using StorPortGetMSIInfo on either platform.
I haven’t checked the W7 WDK, but earlier WDKs do a horrible job of
documenting storport extended functions and their use.
Mark Roddy
On Tue, Mar 24, 2009 at 8:50 AM, Martin O’Brien
wrote:
> I have no idea of what this means, but they do both appear in storport.h
>
> mm
>
> Don Burn wrote:
>>
>> I suspect that StorPortGetMessageInterruptInformation morphed into
>> StorPortGetMSIInfo ?the only reference to former that I can find is the
>> WinHEC 2006 slide deck on storage futures.
>>
>>
>
> —
> 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
>
Thanks
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Mark Roddy
Sent: Tuesday, March 24, 2009 6:17 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] Difference between StorPortGetMSIInfo and StorPortGetMessageInterruptInformation
One (StorPortGetMSIInfo) is a “StorPortExtendedFunction” while the
other is a native storport API. This allows one to write a single
storport driver binary that will run on W2K3 without MSI support and
W2K8 with MSI support, using StorPortGetMSIInfo on either platform.
I haven’t checked the W7 WDK, but earlier WDKs do a horrible job of
documenting storport extended functions and their use.
Mark Roddy
On Tue, Mar 24, 2009 at 8:50 AM, Martin O’Brien
wrote:
> I have no idea of what this means, but they do both appear in storport.h
>
> mm
>
> Don Burn wrote:
>>
>> I suspect that StorPortGetMessageInterruptInformation morphed into
>> StorPortGetMSIInfo the only reference to former that I can find is the
>> WinHEC 2006 slide deck on storage futures.
>>
>>
>
> —
> 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
>
—
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
Maybe I wasn’t clear. One is the storport extended function version,
the other isn’t. You can use the extended function implementation to
code a single binary that will run on OS releases that support
extended functions but don’t support MSI interrupts.
Mark Roddy
On Mon, Mar 23, 2009 at 7:43 PM, wrote:
> What’s the difference between these two routines? ?I want to register an MSIx interrupt handler. ?If I understand things correctly I should make a call to one of these routines with the appropriate messageID to determine if Windows granted me the vector during my HW_Initialize routine. ?It looks like they both map to the same storport extended function, but I just want to be sure. ?Anyone have the answer?
>
> —
> 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
>