Creating a Work Item at Dispatch Level

NTDEV
1

Hi,

I’m trying to create a work item inside a continuous reader read complete callback which is called at dispatch level.

The problem is that my context, which has the pointer to the wdf device (necessary to fill the config structure of the reader), seems to be accessible only at passive level.

When I try to access my context to get the pointer to wdf device, I get a kernel panic with IRL NOT LESS OR EQUAL

Is it possible to create a Work Item at this level? How should I overcome this problem?

Thanks,

Nuno

2

xxxxx@imaginando.net wrote:

I’m trying to create a work item inside a continuous reader read complete callback which is called at dispatch level.

The problem is that my context, which has the pointer to the wdf device (necessary to fill the config structure of the reader), seems to be accessible only at passive level.

When I try to access my context to get the pointer to wdf device, I get a kernel panic with IRL NOT LESS OR EQUAL

Is it possible to create a Work Item at this level? How should I overcome this problem?

KMDF contexts are stored in non-paged memory. You should be able to
access them at any IRQL. Are you sure you are passing your context into
the work item correctly? Do you want to show us the code that creates
and launches the work item, and the first few lines of the work item
callback?

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

3

Create the work item at startup and queue it at DISPATCH_LEVEL. If you
is to do more work while the work item is queued, have a data structure
that can be updated, typically use the InterlockedXXx calls to manage
it.

Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

“xxxxx@imaginando.net” wrote in message
news:xxxxx@ntdev:

> Hi,
>
> I’m trying to create a work item inside a continuous reader read complete callback which is called at dispatch level.
>
> The problem is that my context, which has the pointer to the wdf device (necessary to fill the config structure of the reader), seems to be accessible only at passive level.
>
> When I try to access my context to get the pointer to wdf device, I get a kernel panic with IRL NOT LESS OR EQUAL
>
> Is it possible to create a Work Item at this level? How should I overcome this problem?
>
> Thanks,
>
> Nuno

4

You can create a work item at dispatch, your context is also accessible at dispatch. My guess is that your context pointer itself is invalid.

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@imaginando.net
Sent: Monday, June 06, 2011 10:14 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Creating a Work Item at Dispatch Level

Hi,

I’m trying to create a work item inside a continuous reader read complete callback which is called at dispatch level.

The problem is that my context, which has the pointer to the wdf device (necessary to fill the config structure of the reader), seems to be accessible only at passive level.

When I try to access my context to get the pointer to wdf device, I get a kernel panic with IRL NOT LESS OR EQUAL

Is it possible to create a Work Item at this level? How should I overcome this problem?

Thanks,

Nuno

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

Hi,

Thanks for your replies. I’ve solved the problem in the meanwhile. It was a stupid thing.

Sometimes, compilers are so picky about little thing and it wasn’t complaing about the fact of two parameters are being passed to a one parameter function. I was accessing something that wasn’t supposed to.

Work items are working great!

Cheers,

Nuno

6

Sorry, but that sounds more like an operator headspace issue.

Gary G. Little

----- Original Message -----
From: xxxxx@imaginando.net
To: “Windows System Software Devs Interest List”
Sent: Tuesday, June 7, 2011 6:52:50 AM
Subject: RE:[ntdev] Creating a Work Item at Dispatch Level

Hi,

Thanks for your replies. I’ve solved the problem in the meanwhile. It was a stupid thing.

Sometimes, compilers are so picky about little thing and it wasn’t complaing about the fact of two parameters are being passed to a one parameter function. I was accessing something that wasn’t supposed to.

Work items are working great!

Cheers,

Nuno

—
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

I have seen this when using the function pointers.
Is this the case for you?
Otherwise this should be a compile time error…

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@imaginando.net
Sent: Tuesday, June 07, 2011 5:23 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Creating a Work Item at Dispatch Level

Hi,

Thanks for your replies. I’ve solved the problem in the meanwhile. It was a stupid thing.

Sometimes, compilers are so picky about little thing and it wasn’t complaing about the fact of two parameters are being passed to a one parameter function. I was accessing something that wasn’t supposed to.

Work items are working great!

Cheers,

Nuno

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

8

Yes, it was on a fuction using pointers.

9

MSC_WARNING_LEVEL=/W4 /WX

as a standard setting in all Sources files works for me.

Mark Roddy

On Tue, Jun 7, 2011 at 7:52 AM, wrote:
> Hi,
>
> Thanks for your replies. I’ve solved the problem in the meanwhile. It was a stupid thing.
>
> Sometimes, compilers are so picky about little thing and it wasn’t complaing about the fact of two parameters are being passed to a one parameter function. I was accessing something that wasn’t supposed to.
>
> Work items are working great!
>
> Cheers,
>
> Nuno
>
>
>
>
>
> —
> 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
>