Re: [coLinux-users] 0.7.2 less reliable on dual core?

[Henry N. <Hen...@Ar...>]

baldyeti wrote:
> On 06/03/2008 09:18, Henry Nestler wrote:
>> DebugView is totaly ok. No errors, no "Bug: ...", very good.
>>
>> "big Range" can not see on coLinux starts.
>> You can only see it at driver load:
>>   colinux-daemon.exe --remove-driver
>>   colinux-daemon.exe --install-driver
>>
> Just for confirmation:
> 
> [m:colinux-driver f:0 l:10 
> src/colinux/os/winnt/kernel/manager.c:134:co_os_manager_init] big 
> Range[2] 0x0.01000000 0x0.77000000
> 
> and then later:
> 
> [m:colinux-driver f:0 l:10 
> src/colinux/os/winnt/kernel/alloc.c:65:co_winnt_new_mdl_bucket] FixRange 
> used 0x1000000 0x77000000
> 
> So Henry ... is this all pointing to a problem in the nvidia
> graphics driver, or a bug that might have bitten anyone with
> an IGP using shared memory?

I have tryed to allocating memory in the range of my shared graphic
adapter. Failed, and don't got memory from this area. So, my graphics
driver (ATI) works right and block coLinux from getting this memory area.

My laptop has 512MB total ram, from that are 32MB shared graphic. This
is coLinux driver debug from testing:
  Rage[0] 0x1000 0x9e000 (647168 0MB)
  Rage[1] 0x100000 0xeff000 (15724544 14MB)
  Rage[2] 0x1000000 0x1cff0000 (486473728 463MB)
  Try to get from 0x1e000000 to 0x20000000 size 262144
  MmAllocatePagesForMdl failed


It's a double fault on both drivers. It's a bug in your graphic card
driver and in coLinux driver. Would coLinux ask for specific range
instead "any" ram, then would no have problems. The last workarround
does exactly this.
If your card would mark the memory as "in use", then colinux driver
would not got it.

We know, that MmAllocatePagesForMdl is undocumented. But, I can not find
a simple way to get a big list of pages without having virtual memory
before. All the functions needs to have virtual memory as parameter.
With virtual bufer would have to create a MDL from that, than can fill
the MDL with pages...

Interesing links:
"Address Mappings and MDLs"
http://msdn2.microsoft.com/en-us/library/ms796200.aspx

"Long-Term Internal Driver Buffers"
http://msdn2.microsoft.com/en-us/library/ms796250.aspx

-- 
Henry N.