March 2013 - kernelnewbies@kernelnewbies.org - Kernelnewbies Mailing Lists

numerous kernel tutorials coming shortly
by Robert P. J. Day March 16, 2013

March 16, 2013

over the next few weeks, i'm going to be writing wiki pages totally arbitrarily to be (eventually) incorporated into some new kernel programming and embedded linux courses. the eventual courseware will be released under a creative commons license so i have no reason not to publish everything as i write it. the wiki pages will be in rough draft, not guaranteed to be totally correct and subject to change without notice, but help yourself. here's one i put together just this morning: http://www.crashcourse.ca/wiki/index.php/USB_devices simply because i wanted at least a starting point to talk about USB devices and drivers. more to come, and in no particular order. feedback welcome, especially pointers to online sources of current and well-written pages by others. back to work ... rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================

1 0

Re: linux-newbie vs kernelnewbies
by Raymond Jennings March 16, 2013

March 16, 2013

On Fri, Mar 15, 2013 at 4:48 PM, information.security.admin(a)gmail.com <information.security.admin(a)gmail.com> wrote: > I thought linux newbies was for people new to linux. I guess it is not. I > sent a question to about getting my network connection working and was > directed elsewhere. I think these lists are for kernal hackers. Not linux > newbies like myself. Considering the two contradictory replies I've seen in response to my question I think some clarification is in order! > Sent from my HTC on the Now Network from Sprint! > > > ----- Reply message ----- > From: "Raymond Jennings" <shentino(a)gmail.com> > Date: Fri, Mar 15, 2013 6:48 am > Subject: linux-newbie vs kernelnewbies > To: <linux-newbie(a)vger.kernel.org> > Cc: <kernelnewbies(a)kernelnewbies.org> > > > Is there much of a difference between these two lists? > -- > To unsubscribe from this list: send the line "unsubscribe linux-newbie" in > the body of a message to majordomo(a)vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.linux-learn.org/faqs > >

1 0

linux-newbie vs kernelnewbies
by Raymond Jennings March 15, 2013

March 15, 2013

Is there much of a difference between these two lists?

2 1

block mailing list?
by Raymond Jennings March 15, 2013

March 15, 2013

Is there a kernel list dedicated to discussion of block devices?

2 1

Need of different memory zones
by Niroj Pokhrel March 15, 2013

March 15, 2013

Hi All, I have been studying Memory Management in linux. But I am confused with the division of different ZONE. The use of ZONE_DMA and ZONE_NORMAL is fine. But I am confused with ZONE_HIGHMEM, if the system is 32 bit then why can't it map 4GB memory (2^32). I had thought that ZONE_NORMAL was for the kernel usage so directly mapped and ZONE_HIGHMEM for the user process and is not directly mapped to facilitate virtual addressing. But I know I am not getting something right. While going through Ch - 15 of Rubini's Linux Device Driver (Memory Management and DMA) I came across following line "a 64-bit architecture such as Intel’s x86-64 can fully map and handle 64-bits of memory.Thus, x86-64 has no ZONE_HIGHMEM and all physical memory is contained within ZONE_DMA and ZONE_NORMAL." So, if it can be directly mapped why not in 32 bit architecture. I am really confused. Please Help. Thanking you in Advance Yours, Niroj Pokhrel

4 5

[ARM-LINUX] Quiry regarding the DMA mapping.
by sandeep kumar March 15, 2013

March 15, 2013

Dear All i have one question regarding DMA mapping. i know that dma_alloc* API does the mapping for DMA' able memory. But is it the only way to get dma'able memory? Can we do a dma to pmem or ion reserved heaps as well, right away without dma_alloc?(this also assures us the physical contigious region) -- With regards, Sandeep Kumar Anantapalli,

1 0

networking question
by devendra.aaru March 15, 2013

March 15, 2013

Hey all, I have got a strange bug(?) while testing the multicasting server and client. I have done only the INADDR_ANY bind in server and client adds its IP_MULTICAST_IF to 224.0.0.1 , surprisingly i recvd pkts from the client with out joining using IP_ADD_MEMBERSHIP. Is that a bug? or as we listening on INADDR_ANY will make us recv all the mcast/bcast pkts? while if i do tx on 224.0.0.3 , the server is not able to recv the packets. any ideas?

2 2

When to use blk_end_request_* routines.
by Pranay Kumar Srivastava March 14, 2013

March 14, 2013

Hi, I'm using SLES11-SP1 kernel 2.6.32 .12-0.7 I wrote a block driver for an in-memory disk. The driver seems to work fine however sometimes when I try to unload the driver the machine freezes, the module_exit code looks like the following, /*We take no more requests!*/ spin_lock_irqsave(&pks_disk->queue_lock,flags); blk_stop_queue(pks_disk->pks_disk_rqq); spin_unlock_irqrestore(&pks_disk->queue_lock,flags); /*Remove disk*/ del_gendisk(pks_disk->pks_disk_gd); /*free queue*/ blk_cleanup_queue(pks_disk->pks_disk_rqq); I searched around and found out that while processing the requests from request queue you've got to use one of the blk_end_request* functions (which I did). However if I only use a) blk_end_request: The module removal code freezes machine. b) blk_end_request_cur: The module removal code works fine. There's one more c)blk_end_request_all: Didn't used this one cuz the above one worked :P. I digged around in the source and found this function blk_update_request and in the comment section it says " Actual device drivers should use blk_end_request instead" which I did and the driver module didn't liked it when I tried to remove it :( Now I'm confused as I've got no clue when to use which function can anyone give some examples please? --P.K.S ::DISCLAIMER:: ---------------------------------------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ----------------------------------------------------------------------------------------------------------------------------------------------------

1 0

Unlocking task_list read lock before performing a sleepy operation
by Pranami Bhattacharya March 14, 2013

March 14, 2013

Dear All, I was trying the following and had a doubt. >From my kernel module I want to iterate over task list and do some sleepy operation for all the process for which my task->flag is set .I know by holding read_lock(tasklist_lock)/rcu_read_lock I should not be performing any sleepy operation. So I have coded like below : 1. Take the read lock 2. Iterate over task (for_each_process) 3. If my flag is set I unlock the tasklist_lock and get_task_struct 4. Perform the sleepy operation 5. Then put_task_struct 6. Again take read_lock(&tasklist_lock); 7. Loop continues The code snippet is as shown below : read_lock(&tasklist_lock); for_each_process(c) { if (c->my_flag) { read_unlock(&tasklist_lock); get_task_struct(c); ... perform_sleepy_operation(); ... put_task_struct(c); read_lock(&tasklist_lock); } } Please let me know if this approach is correct. Thanks and Regards, Pranami

1 0

nmi_watchdog kernel parameter is set but NMI interrupts are not incremented
by Kevin Wilson March 13, 2013

March 13, 2013

I read the nmi_watchdog section in http://lxr.free-electrons.com/source/Documentation/sysctl/kernel.txt I tried booting with nmi_watchdog=2 and with nmi_watchdog=1. In both cases I did not see that the NMI interrupts are incremented (cat /proc/interrupts showed 0 0 for NMI) I saw on the web the most new computers from the last 2-3 years should have support for using nmi_watchdog. I am using Fedora 18. (x86_64) I would appreciate if someone (preferably more than one) will try to boot with nmi_watchdog=2 and will report the result. rgs, Kevin

1 0