[ros-kernel] How to get started writing ReactOS drivers

[Hartmut Birr]

Hi,    

for my nt/xp drivers I use my own tool which sets the common gcc
sections to non pageable. The init and pageable code goes to a special
section like the init section from ntoskrnl. At the moment this isn't a
problem for ros. Paging of kernel code is not implemented. I would like
that ld can set special attributes for sections.  

- Hartmut

> -----Original Message-----
> From: ros-kernel-bounces at reactos.com 
> [mailto:ros-kernel-bounces at reactos.com] On Behalf Of Vizzini
> Sent: Monday, February 09, 2004 8:50 AM
> To: ReactOS Kernel List
> Subject: Re: [ros-kernel] How to get started writing ReactOS drivers
> 
> 
> On Sun, 2004-02-08 at 18:50, Vizzini wrote:
> > I really didn't mean for this discussion to get so theoretical.  I'm
> > really interested to know what Hartmut, Eric, Casper, David, and the
> > rest of the folks who have contributed drivers currently do 
> to keep code
> > from paging out.  I will go look tonight and see if I can 
> figure it out.
> 
> OK, I'll bite.  I glanced at a couple of drivers and don't 
> see anything
> explicit preventing them from being paged.  Unless there is 
> some voodoo
> inthe build system that keeps these things resident, I'd say we have a
> nontrivial problem on our hands.
> 
> If this problem is indeed un-adressed at the moment, I'd say we need a
> tool to set the sections up as not paged, discardable, etc.  At the
> least, we need something that un-pages the whole driver.  If 
> we have to
> do runtime paging control with Mm apis until we get compiler/linker
> support, that's not the end of the world.
> 
>  -Vizzini
> 
> 
> _______________________________________________
> Ros-kernel mailing list
> Ros-kernel at reactos.com
> http://reactos.com/mailman/listinfo/ros-kernel
>