HalAllocateCommonBuffer internaly relays on
MmAllocateContiguousMemorySpecifyCache to carry out the allocation.
HalAllocateCommonBuffer shameless ignore the CacheEnabled parameter in my XP
build. You can pass anything there, it will be ignored. The later function
always gets called (XP no service pack) with CacheType set to 1, which is
MmCached.
Regardless of what the DDK doc says, you will always get cached memory. Now
kindly ask MS to fix either docs , either the HAL itself .
I think this permanantly solves the mistery.
My best , Dan
----- Original Message -----
From: “Stephen Williams”
To: “NT Developers Interest List”
Sent: Thursday, June 20, 2002 11:47 PM
Subject: [ntdev] Re: posible bug in XP kernel - was MmMapLockedPages… on
XP vs. 2000
> >> And what should I do with said exception? Just fail the whole
operation?
>
> xxxxx@rdsor.ro said:
> > Fix the situation , ensure cache coherency. Make sure you use the same
> > attributtes for caching everywhere.
>
> But these pages are supposedly noncached everywhere! I’m asking the
> AllocateCommonBuffer function to make them non-cached. And if I weren’t,
> wouldn’t it crash every time?
>
>
> –
> Steve Williams “The woods are lovely, dark and deep.
> steve at icarus.com But I have promises to keep,
> steve at picturel.com and lines to code before I sleep,
> http://www.picturel.com And lines to code before I sleep.”
>
> abuse@xo.com
> xxxxx@ftc.gov
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@rdsor.ro
> To unsubscribe send a blank email to %%email.unsub%%
>