June 2007 - Darwin-kernel - lists.apple.com

Newbie question - missing vop* structures/functions in sys/vnode.h on 10.4
by Ratheesh Ramachandran 06 Jun '07

06 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-kernel(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=Crz5dTw3dW+Us4u3YJ3v2Vy05Rri7P3TB74+hlJ1DE8nlfQLi6wWa0lzmZ6bBk3uxRdehlrHVMR7s9mA2TBad/06yvSjBaMyw/YB1n/btYKjisEb2TxFg6LZTrxnsmZ3DyGCzWXQYa8hSS7+isxDPYlNlvdckeU7w7Trct42VL8=; _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Compiling Darwin for MacBook Pro
by Michael Smith 06 Jun '07

06 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-kernel(a)lists.apple.com On Jun 6, 2007, at 7:31 AM, John Criswell wrote: I'd like to gain some confidence that if we buy this machine, we can expect to compile our own kernels and have them work on the machine. Yes. Yes. = Mike _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… Our research group is looking to buy a Macbook Pro (2.16 GHz Intel Core 2 Duo) for some research that we are doing. Our work involves modifications to the Darwin kernel. Modulo the complexity of building the open-source kernel releases, yes, this generally works. Has anyone compiled a Darwin kernel and successfully run it on an Intel Mac laptop Are there any drivers required for the machine that are not part of the open source Darwin project? Our project requires being able to do compiler analysis of the entire kernel source. Drivers are not part of the kernel, per se. They, and their supporting libraries ("Families") are handled as loadable modules. This email sent to site_archiver(a)lists.apple.com

1 0

Compiling Darwin for MacBook Pro
by John Criswell 06 Jun '07

06 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-kernel(a)lists.apple.com Organization: University of Illinois User-agent: Thunderbird 1.5.0.10 (X11/20070221) Dear All, Our research group is looking to buy a Macbook Pro (2.16 GHz Intel Core 2 Duo) for some research that we are doing. Our work involves modifications to the Darwin kernel. I'd like to gain some confidence that if we buy this machine, we can expect to compile our own kernels and have them work on the machine. Has anyone compiled a Darwin kernel and successfully run it on an Intel Mac laptop (or conversely, tried it and have it fail)? Are there any drivers required for the machine that are not part of the open source Darwin project? Our project requires being able to do compiler analysis of the entire kernel source. Thanks in advance on any advice. -- John Criswell _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Reload VM hint? (James Bucanek)
by Terry Lambert 06 Jun '07

06 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-kernel(a)lists.apple.com <http://www.macosxhints.com/article.php?story=20060817044149264> and Amit's book covers it in detail in chapter 11. <http://developer.apple.com/wwdc/tracks/macosx.html> -- Terry _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… On Jun 5, 2007, at 5:05 AM, Quinn wrote: At 7:51 -0400 5/6/07, Michael Cashwell wrote: Really?? Is this a change in policy? I had a mental post-it on fsevents that it was akin to an SPI and not really meant for general 3rd party use. Yes. One of the downsides of having direct access to kernel engineers via this mailing list is that they sometimes forget what's public API and what's not. They've been working on Leopard for a long time (-: Actually, there's "FSEvents" tracks announced for WWDC that show up for any "fsevents site:apple.com" search, and there's some documentation on <http://developer.apple.com>. But I meant "/dev/fsevents", for which there is also a "hints" article at: But Quinn's right, we don't recommend using it at present; it's just better than the alternative, in this case. 8^/. Anyway, for the record, we're introducing a public API for fsevents in Leopard, but on current released systems there's no supported API for accessing it. You can talk to /dev/fsevents directly (reverse engineering the protocol from the Darwin kernel source), but that's unsupported. Specifically, it's possible that that the interface to /dev/fsevents will change over time: if you talk to the public API, you'll be isolated from this change; if you talk directly to / dev/fsevents, you won't. There's a non-supported API, however, which is what I was referring to. It's also possible to hook into the KAUTH system to implement your own notification mechanism (this is what the virus scanners do). btw If you look at the public session information for WWDC, you'll see that we have a session that discusses the new-in-Leopard public API (the FSEvents framework). It should be a good session, and it's an API that I've been eagerly waiting for a long time. Once Leopard ships it would be reasonably safe to use /dev/fsevents prior to Leopard. That is, write code that using the FSEvents framework on Leopard and later, and separate code that using /dev/ fsevents on 10.4.x. Once Leopard ships, it's unlikely that we'll do any significant revisions to /dev/fsevents. It's still a risk, but it's a much smaller risk. Actually, for Leopard, you will want to use the framework, for sure, rather than the device directly. The device requires that you be root to open it, because if you are non-responsive to events coming in, then you can stall operations in the kernel. If you go the /dev/ fsevents route from the "hints" article, make sure you allocate a separate thread whose only job is to dequeue events from the kernel as quickly as possible, and deal with any latency/bottlenecks in user space. This email sent to site_archiver(a)lists.apple.com

1 0

Re: kdb with serial port
by Carlos Calderon 05 Jun '07

05 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-kernel(a)lists.apple.com For posterity: // carlos On Jun 2, 2007, at 9:50 AM, Terry Lambert wrote: Thank you Terry for this great infos. _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… Some "debug" flags described here: <http://developer.apple.com/ technotes/tn2004/tn2118.html#SECDEBUGFLAGS> All the "debug" flags are defined here: <Kernel/PrivateHeaders/kern/ debug.h>. On Jun 2, 2007, at 8:14 AM, apic | puredarwin.org wrote: I put right after the delay you mentioned a PE_enter_debugger ("debug_me") which works fine, the problem at this point now is the kernel does not find a mac/ip address to use. Which nic's mac address is commonly used? The primary interfaces one? Yes. If this is PPC, and you have bootp setup, then it will set the IP address to the bootp address in Open Firmware, and then once it's done that, even though it says it's IP is 0.0.0.0 when it's waiting for the debugger to attach, the IP address will actually be what the bootp/dhcpd vended to OF. For Intel, I just always use the firewire debugging method (or hardware debugger, if it's too early for IOKit to to have started), which has the same effect. I don't know if Intel sets the IP in EFI or not (maybe Derek is listening in on this and can answer). The way to know if something is registered to handle debugging that early, BTW, is whether or not it says "waiting for debugger" or it says "We are hanging here...". If it says the latter, no one has registered to handle kdp, and you will need to find some way to get a driver loaded (generally, firewire is the recommended metho - see the kernel debugging documentation for details). -- Terry _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/carlos% 40apple.com This email sent to carlos(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: Reload VM hint? (James Bucanek)
by Quinn 05 Jun '07

05 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-kernel(a)lists.apple.com <http://developer.apple.com/wwdc/tracks/macosx.html> S+E -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… At 7:51 -0400 5/6/07, Michael Cashwell wrote: Really?? Is this a change in policy? I had a mental post-it on fsevents that it was akin to an SPI and not really meant for general 3rd party use. Yes. One of the downsides of having direct access to kernel engineers via this mailing list is that they sometimes forget what's public API and what's not. They've been working on Leopard for a long time (-: Anyway, for the record, we're introducing a public API for fsevents in Leopard, but on current released systems there's no supported API for accessing it. You can talk to /dev/fsevents directly (reverse engineering the protocol from the Darwin kernel source), but that's unsupported. Specifically, it's possible that that the interface to /dev/fsevents will change over time: if you talk to the public API, you'll be isolated from this change; if you talk directly to /dev/fsevents, you won't. btw If you look at the public session information for WWDC, you'll see that we have a session that discusses the new-in-Leopard public API (the FSEvents framework). It should be a good session, and it's an API that I've been eagerly waiting for a long time. Once Leopard ships it would be reasonably safe to use /dev/fsevents prior to Leopard. That is, write code that using the FSEvents framework on Leopard and later, and separate code that using /dev/fsevents on 10.4.x. Once Leopard ships, it's unlikely that we'll do any significant revisions to /dev/fsevents. It's still a risk, but it's a much smaller risk. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Reload VM hint? (James Bucanek)
by Michael Cashwell 05 Jun '07

05 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-kernel(a)lists.apple.com On Jun 4, 2007, at 11:03 PM, Terry Lambert wrote: -Mike _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… For a backup utility, you'd be much better off being an fsevents clients (search on <http://developer.apple.com>), and then reacting to events only for files which are actually changed since the last backup. Really?? Is this a change in policy? I had a mental post-it on fsevents that it was akin to an SPI and not really meant for general 3rd party use. My biggest beef with my present backup approach is how glacially slow it is comparing its catalog data to the disk in search of what's changed. What you describe sounds like a very efficient way to avoid all that work. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Error compiling darwin kernel
by Terry Lambert 05 Jun '07

05 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-kernel(a)lists.apple.com Hi list, Search the list archives for details. -- Terry _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… On Jun 4, 2007, at 8:52 AM, Billy Lau wrote: I encountered this error while compiling the kernel using "make all". I obtained the xnu source code from the darwin source code website. /Users/xxx/darwin2/xnu-792.17.14/iokit/Kernel/IOWorkLoop.cpp: In member function 'virtual bool IOWorkLoop::init()': /Users/xxx/darwin2/xnu-792.17.14/iokit/Kernel/IOWorkLoop.cpp:79: error: converting from `IOReturn (IOWorkLoop::*)(void*, void*, void*, void*)' to `IOReturn (*)(OSObject*, void*, void*, void*, void*)' in a kext. Use OSMemberFunctionCast() instead. /Users/xxx/darwin2/xnu-792.17.14/iokit/Kernel/IOWorkLoop.cpp:93: warning: invalid conversion from 'void (*)(void*, wait_result_t)' to 'void (*)(void*)' /Users/xxx/darwin2/xnu-792.17.14/iokit/Kernel/IOWorkLoop.cpp:93: warning: initializing argument 1 of 'thread* IOCreateThread(void (*)(void*), void*)' make[6]: *** [IOWorkLoop.cpo] Error 1 make[5]: *** [build_all] Error 2 make[4]: *** [do_all] Error 2 make[3]: *** [build_all] Error 2 make[2]: *** [build_all] Error 2 make[1]: *** [build_all] Error 2 make: *** [all] Error 2 Does anyone know what is the problem and how to solve it? THank you very much Yeah, you are compiling PPC kernel sources with the gcc 4.0 compiler instead of the gcc 3.3 compiler, or using the Intel kernel sources, which compile for both the PPC and Intel platforms with the gcc 4.0 compiler (but which is not a supported configuration for PPC on not Mac OS X server platforms at this time). This email sent to site_archiver(a)lists.apple.com

1 0

Re: Reload VM hint? (James Bucanek)
by Terry Lambert 05 Jun '07

05 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-kernel(a)lists.apple.com I hadn't thought of that, and that's an excellent suggestion (thanks also extended to Brian and Matt). The source file data is only read once, so at least I can eliminate that from being cashed. Come to think of it, that might improve my overall performance since the reading the source file blocks also competes with the caching of my database file blocks. -- Terry _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… On Jun 2, 2007, at 8:17 PM, Sam Vaughan wrote: On 01/06/2007, at 5:04 AM, James Bucanek <subscriber(a)gloaming.com>: There's an even better reason why F_NOCACHE will probably improve your code's performance. Provided that you do as Quinn suggests with respect to alignment, it will cause the I/O to go directly to/ from your user space buffer, removing the additional copy that happens in the buffered I/O case. This is why it's called "direct I/ O" on most other platforms, where the O_DIRECT flag is used at file open time to enable it. Direct I/O is not necessarily the best idea for anything for which you are not guaranteeing rate monotonic data flow. If you use mmap(), then the memory will not need obe paged out (if you read it using F_NOCACHE, then the pages become dirty pages in your process address space, and may be forced out to swap). If you sequentially access the pages after they are mmap()'ed, then you will trigger clustered I/O read-ahead, which will cause the pages to be faulted in, up to a 1M ubc descriptor at a time. By doing it this way, you will also signal that the pager can scavenge behind by having the pages flagged that way by the pager, which will put them first on the list to be shot, should you hit memory pressure. You can also issue aan fcntl(fd, F_RDADVISE, ...) to force a read ahead; if you then touch (read a byte in from) the last page in the range, the touch will block until the buffer is no longer busy, which means all your pages will be available. For a backup utility, you'd be much better off being an fsevents clients (search on <http://developer.apple.com>), and then reacting to events only for files which are actually changed since the last backup. This email sent to site_archiver(a)lists.apple.com

1 0

Error compiling darwin kernel
by Billy Lau 04 Jun '07

04 Jun '07

site_archiver(a)lists.apple.com Delivered-To: darwin-kernel(a)lists.apple.com Hi list, I encountered this error while compiling the kernel using "make all". I obtained the xnu source code from the darwin source code website. /Users/xxx/darwin2/xnu-792.17.14/iokit/Kernel/IOWorkLoop.cpp: In member function 'virtual bool IOWorkLoop::init()': /Users/xxx/darwin2/xnu-792.17.14/iokit/Kernel/IOWorkLoop.cpp:79: error: converting from `IOReturn (IOWorkLoop::*)(void*, void*, void*, void*)' to `IOReturn (*)(OSObject*, void*, void*, void*, void*)' in a kext. Use OSMemberFunctionCast() instead. /Users/xxx/darwin2/xnu-792.17.14/iokit/Kernel/IOWorkLoop.cpp:93: warning: invalid conversion from 'void (*)(void*, wait_result_t)' to 'void (*)(void*)' /Users/xxx/darwin2/xnu-792.17.14/iokit/Kernel/IOWorkLoop.cpp:93: warning: initializing argument 1 of 'thread* IOCreateThread(void (*)(void*), void*)' make[6]: *** [IOWorkLoop.cpo] Error 1 make[5]: *** [build_all] Error 2 make[4]: *** [do_all] Error 2 make[3]: *** [build_all] Error 2 make[2]: *** [build_all] Error 2 make[1]: *** [build_all] Error 2 make: *** [all] Error 2 Does anyone know what is the problem and how to solve it? THank you very much -Billy _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0