site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On Mar 3, 2008, at 11:23 AM, mm w wrote: Hi Greg, In the doc there is a small chapter regarding Memory wiring called: Memory Mapping and Block Copying, I guess it's exactly what you asked, as Michael said most people think that not using IOKit is more efficient, for the most of cases, it's really wrong, as you have may be noticed IOKit is not a full C++, it's based on Embedded C++, Iokit provides many facilities and kern controls, and sure it depends on what you want to accomplish, if it's to learn or implement something that doesn't exist, your are on the way, if it's for implementing something that already exists not sure :), and sure the xnu source is always your best doc: osfmk/vm/vm_user.c Thanks, - Greg _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... The only reason that I don't want to make an IOKit kext is that I feel it would over-complicate my code. I don't have much time to learn all the paradigms of creating a driver and then a userclient when all I need is one function to start the kernel extension (kextname_start) and one function to stop it (kextname_stop). Are the functions in vm_user.c the only functions available to do what I want? And are you saying that no actual documentation on how to use those functions to do memory mapping exists? Because if that's the case then converting my extension to IOKit stuff might be easier than wading through kernel code. This email sent to site_archiver@lists.apple.com