- kernelnewbies@kernelnewbies.org - Kernelnewbies Mailing Lists

Missing parallel port interrupts
by Eric Fowler Jan. 8, 2014

Jan. 8, 2014

I am writing a simple driver that hooks the parallel port irq and when written to, enables the port for generating interrupts (the pins 9&10 are wired together) and then toggles the high bit once for every byte in the written input. This means that if I do: >echo "0123456789" >> /dev/foobar I expect to toggle that bit 10 times, and generate 10 interrupts. My ISR is a simple counter that bumps a number every time it is called. I am seeing that I am missing about 85% or more of my interrupts. Sometimes I get 2/10 but more often only 1/10. I have tried udelay()-ing between the port toggles but no go, and of course that is not really a solution. I am not trying to protect the counter but nothing else is accessing it. I would expect to see *some* losses here, but not that many. What is going on? Code follows. Thanks loads Eric ///////////////////////////////-----------cut here------------------------ #include <linux/kernel.h> #include <linux/module.h> #include <linux/fs.h> #include <linux/ioport.h> #include <linux/cdev.h> #include <linux/slab.h> #include <linux/init.h> #include <linux/delay.h> #include <asm/uaccess.h> #include <linux/seq_file.h> #include <linux/interrupt.h> MODULE_LICENSE("GPL"); #define NUM_DEVICES (1) #define DEVNAME "foobar" #define FOOBAR_MAJOR (248) #define FOOBAR_MINOR (0) int foobar_init(void); void foobar_exit(void); int foobar_release(struct inode *, struct file*); ssize_t foobar_read(struct file *, char __user *, size_t, loff_t *); ssize_t foobar_write(struct file *, const char __user *, size_t, loff_t *); int foobar_open(struct inode * inode, struct file * file); void set_port_and_irq(void); static irqreturn_t irqhandler(int irq, void * data); int foobar_set_irq(void); int port_address = -1; module_param(port_address, int, 0); unsigned int irq = 0; module_param(irq, uint, 0); int irqavail = -1; size_t chars_read = 0; static struct file_operations foobar_i_fops = { .owner = THIS_MODULE, .read = foobar_read, .write = foobar_write, .open = foobar_open, .release = foobar_release, }; struct resource * region = NULL; static unsigned long mask; static unsigned long probe; static dev_t g_dev; unsigned dev_id = (unsigned)&foobar_i_fops; int foobar_init(void) { int result = 0; result = register_chrdev(0, DEVNAME, &foobar_i_fops); g_dev = MKDEV(result, FOOBAR_MINOR); if(result < 0) { printk(KERN_WARNING "foobar: can't get device number, returning %d", result); return result; } printk(KERN_WARNING "foobar: Module %s got device number %d, minor is %d, result is %d\n", THIS_MODULE->name, MAJOR(g_dev), MINOR(g_dev), result); g_dev = MKDEV(MAJOR(g_dev), FOOBAR_MINOR + NUM_DEVICES); set_port_and_irq(); region = request_region(port_address, 1, DEVNAME); printk(KERN_WARNING "Port address is 0x%x, IRQ is %d, region is 0x%p\n", port_address, irq, region); if(region == 0) { printk(KERN_WARNING "Can't get region"); return -ENODEV; } mask = probe_irq_on(); return 0; } void foobar_exit(void) { int major = MAJOR(g_dev); release_region(port_address, 1); printk(KERN_WARNING "unregister_chrdev(%d) called for %s, dev # is %d\n", major, DEVNAME, g_dev); unregister_chrdev(major, DEVNAME); } int foobar_open(struct inode * inode, struct file * file) { irqavail = request_irq(irq, irqhandler, IRQF_SHARED, DEVNAME, (void*)dev_id); printk(KERN_WARNING "IRQ:%d\tPort Address:0x%x\tAvailable:%s\n", irq, port_address, irqavail == 0 ? "true" : "false"); return irqavail; } int foobar_release(struct inode * inode, struct file * filp) { printk(KERN_WARNING "foobar_release() is called, fil is 0x%p, inode is 0x%p\n", filp, inode); if(irqavail == 0) { printk(KERN_WARNING "Freeing irq %d, dev_id is 0x%x\n", irq, dev_id); free_irq(irq, (void*)dev_id); } else printk(KERN_WARNING "NOT freeing irq %d, dev_id is 0x%x\n", irq, dev_id); probe = probe_irq_off(mask); return 0; } ssize_t foobar_read(struct file * filp, char __user * buf, size_t count, loff_t * f_pos) { if(chars_read == 0) { printk(KERN_WARNING "Read is called, nothing to return."); return 0; } sprintf(buf, "Chars>%d\n", chars_read); chars_read = 0; printk(KERN_WARNING "Read is called, returning %s, length is %d\n", buf, strlen(buf)); return count; } ssize_t foobar_write(struct file * filp, const char __user * buf, size_t count, loff_t *f_pos) { size_t idx; unsigned long address = (unsigned long)port_address; printk(KERN_WARNING "Write is called, count is %d, address is 0x%lx, buffer is %s\n", count, address, buf); outb_p(0x10, address + 2); for(idx = 0; idx < strlen(buf); ++idx) { outb_p(0x00, address); udelay(100); outb_p(0xff, address); udelay(100); } outb_p(0x00, address + 2); udelay(5); printk(KERN_WARNING "probe_irq_off(0x%lx) returned 0x%lx", mask, probe); if(f_pos) * f_pos = 0; return count; } static irqreturn_t irqhandler(int irq, void * data) { chars_read++; printk(KERN_WARNING "Interrupt is fired, IRQ is %d, data is 0x%p, chars %d\n", irq, data, chars_read); return IRQ_HANDLED; } void set_port_and_irq(void) { if(irq < 0) switch(port_address) { case 0x378: irq = 7; break; case 0x278: irq = 2; break; } switch(irq) { case 2: port_address = 0x278; break; case 7: port_address = 0x378; break; } } module_init(foobar_init); module_exit(foobar_exit);

1 0

Error in Make for Kernel Module
by Arun M Kumar Jan. 7, 2014

Jan. 7, 2014

I am starting with Device Drivers for Linux System Details: Linux linux-nwya.site 3.10.25-2.10-desktop #2 SMP PREEMPT Tue Jan 7 00:25:03 IST 2014 i686 i686 i386 GNU/Linux I created a Simple Hello_world Kernel Module. "Hello_World.c" //--------------------------------------------------------- /* My first kernel Module */ #include <linux/init.h> #include <linux/module.h> static init my_init(void){ printk(KERN_ALERT "Hello World\n"); return 0; } static void my_exit(void){ printk(KERN_ALERT "Exit\n"); } MODULE_LICENSE("GPL"); module_init(my_init); module_exit(my_exit); //--------------------------------------------------------------------- The Makefile is as follows: The file name is "Makefile" //--------------------------------------------------------------------- obj-m := Hello_World.o //--------------------------------------------------------------------- on running the make command i get the following error. //---------------------------------------------------------------------------- make: Entering directory `/home/arun/Linux_Source' ERROR: Kernel configuration is invalid. include/generated/autoconf.h or include/config/auto.conf are missing. Run 'make oldconfig && make prepare' on kernel src to fix it. make: *** No rule to make target `Device'. Stop. make: Leaving directory `/home/arun/Linux_Source' //------------------------------------------------------------------------------- I have tried "make prepare" but the issue remains.... any suggestions would be appreciated. Thanks in advance.

2 1

Self Introduction
by Ganessh Kumar R P Jan. 7, 2014

Jan. 7, 2014

Hello guys, I have a fair knowledge about kernel after a course on Operating System as part of my under-grad and hands on in building kernel from source code. I want to start contributing to small projects. Is anyone needs some assistance or small work lying around please point it to me. Any guidance or pointers will be helpful. I will be also active in IRC channel. Thanks, Ganessh

1 0

user space vs kernel space address space
by Pritam Bankar Jan. 7, 2014

Jan. 7, 2014

Lets consider 32 bit Linux system with 512 physical RAM. Suppose I have standard 3:1 address space split. Now what I understand is (In general) 1. In the fourth gigabyte I have kernel space 2. Out of 1GB for kernel address space only 896MB is used as direct mapping and other 128 MB is used for Noncontiguous Memory Area Management, Fixed Mapping and Permanent Mapping. PCMIIW Following are my doubts : 1. Since my system has only 512MB RAM, will there be only direct mappings since 896 is enough to hold 512 RAM? 2. When user space program do malloc, we get some virtual address from userspace region (from first 3GB) of process. So will it be like, when I access some memory from that region, there is some physical frame associated with it AND same physical frame will also be mapped in kernel space ? So what I want to know, for every physical frame is there a mapping in userspace as well as kernel space ? (given that some address in user space of process map to same physical frame) 3. If we consider example of Linux system with 4GB, now if I do malloc from user space from which memory region kernel will give memory ? Direct mapped region or fixed map or permanent map ? Thanks and regards, Pritam Bankar

4 6

Breaking up a bvec in a bio for reading more than 512
by neha naik Jan. 7, 2014

Jan. 7, 2014

Hi All, I am getting a request with bvec->bv_len > 512. Now, the information to be read is scattered across the entire disk in 512 chunks. So that, information on disk can be : sector 8, sector 100, sector 9. Now if i get a request to read with the bvec->bv_len > 512 i need to pull in the information from multiple places on disk since the data is not sequentially located. I tried to look at the linux source code because i think raid must be doing it all the time. (eg : on disk 1 we may be storing sector 6 and on disk 2 we may be storing sector 7 and so on). However, i have not really got any useful information from it. Also scouring through articles on google has not helped much. I am hoping somebody points me in the right direction. Thanks in advance, Neha

3 7

simple memory malloc and free in ip_output.c
by Guibin(Bill) Tian Jan. 7, 2014

Jan. 7, 2014

Hi, I am doing a very simple operation at the method of ip_queue_xmit in ip_output.c. The code is very simple. char *p = kmalloc(48, GFP_KERNEL); kfree(p); This will be called every time this method is called. But the result is that the whole system is not responsive at all. This is a very simple, not sure what I am doing wrong. Can anybody help? Thanks

5 9

DMA, CMA, coherence and performance
by Steven Bell Jan. 7, 2014

Jan. 7, 2014

Hi, I'm working on a device driver for a video device which continuously reads and writes image frames using DMA. The frames are fairly large, in the range of 2-8MB, and I would like the buffers for them to be contiguous because of my hardware. My understanding is that using the contiguous memory allocator is the current "right way" to get the buffers, and that CMA operates entirely behind the scenes when calls are made to dma_alloc_coherent(). However, it seems that for this system, a streaming DMA setup would be more appropriate. The buffer gets filled with data once, handed to the device, and then isn't touched again until it gets reused with new data. The resources I've read have hinted that streaming DMA has some performance benefits over coherent DMA, so this seems like the way to go. But I haven't seen any discussion of how to use CMA with streaming DMA (or whether such a thing is even necessary). Does the CMA also work behind get_free_pages, or other kernel memory allocation methods? Does it matter? The kernel newbies page on memory allocation (http://kernelnewbies.org/KernelMemoryAllocation) says that get_free_pages up to about 8MB are ok. Is that a generalization based on typical memory fragmentation, or a guarantee? Thanks, Steven

5 6

Interrupt fires when module is unloaded
by Eric Fowler Jan. 7, 2014

Jan. 7, 2014

I am trying to figure out interrupts by writing a shadow of Rubini's 'short' program. Recall that Rubini tells us to enable parallel port interrupts by wiring pins 9&10 together, then writing binary data to the parallel port's address. I am doing that, but: - I don't see interrupts when I write to the port - I do see one interrupt when I unload the driver (in the fop's .release method) - This happens whether or not the pins are wired up. What is going on here?

2 3

Help request: Blocking access to USB mass storage device across momentary power loss
by Rick Ramstetter Jan. 6, 2014

Jan. 6, 2014

I sent the following email to "Matthew Dharm" whose name appears in Linux 2.6.35's "scsiglue.c" as that file's primary maintainer. I realize in retrospect I should have messaged the kernelnewbies and/or linux-usb lists first. To summarize the below text, "what we're hoping to do ... is reset the SD cards ... via a drop of the appropriate power rail ... such that in progress userspace calls to read() and write() are blocked until the hardware completes its power on initialization sequence" ------------------------------------------- From: J. Rick Ramstetter Sent: Monday, January 06, 2014 11:53 AM To: mdharm-usb(a)one-eyed-alien.net Subject: Help request: Blocking access to USB mass storage device across momentary power loss Hello Matthew, I'm emailing you because your name and email address were mentioned in the source "scsiglue.c" of Linux kernel version 2.6.35. I'm about to ask for help with aspects of that source file, and I'm hoping you'd be kind enough to entertain my questions. I work for a company that makes in flight entertainment (IFE) hardware for various non-US airlines. These units are, at their core, flight certified movie players with a secondary storage methodology of SD cards. Each unit interfaces with its SD card storage via an SMSC 2660 or SMSC 2640 chip; in other words, the individual SD cards appear to the IFE units as USB mass storage devices using the most-common forms of USB mass storage (drivers/usb/storage/scsiglue.c, Bulk-Only, Transparent SCSI). We've recently root-caused a bug in our use of the SMSC 26x0 chips. The cause is in hardware: in our board design, we failed to use CRD_PWR lines provided by the SMSC chips to power the SD cards, but instead wired the SD cards directly to the same 3.3v rail that powers the SMSC chips. We've been advised by SMSC that this is improper, and our own empirical testing suggests that the SMSC chips expect to be able to "power cycle" the SD cards by cycling the CRD_PWR lines. Though we've fixed the problem for future board revisions, we have thousands of affected IFE units in the field and reworking them is impossible. We have observed the following behaviors: (1) The SMSC chip becomes, in USB terminology, "orphaned" (2) The IFE units react by issuing a USB port reset (the usb mass storage driver's "scsiglue.c" sets a port reset as the scsi host bus reset function pointer) (3) That reset causes the SMSC chip to reset, but the SD cards are not reset due to improper wiring (4) The SMSC chip and SD cards cannot communicate due to non-matched state. Accesses fall through to scsi_lib's scsi_io_completion()'s "case NOT_READY ... action = ACTION_FAIL" logic. What we're hoping to do, and forgive me if this seems extreme, is reset the SD cards at step (3) above via a drop of the appropriate power rail. We have software control of that rail, and there are few devices on it, all of which are storage devices. We've demonstrated the feasibility of "suspending" all of the platform (hardwired platform_device) storage devices on that rail during a blackout, such that in progress userspace calls to read() and write() are blocked until the hardware completes its power on initialization sequence. We have not, however, demonstrated this feasibility with our USB Mass Storage SD card devices, and thus I'm emailing you. With regard to "suspending" the SD card devices, we've tried walking the LDM device tree from childmost device to parentmost device, invoking the appropriate power management suspend() operations as we go (including those for usb's endpoint.c devices), but have had no luck during our resume operation. Upon powerup of the SD cards and SMSC chip, USB re-enumerates the devices, and re-invokes scsi_add_host() (ref usb_stor_probe2()). The net result is a new scsi host, a new UEVENT, and a new udev device node. Can you offer any advice on the goal of blocking userspace read() and write() calls during the device's blackout? I can see a few different approaches to this, including: * A FUSE layer * Pausing the Host in the SCSI layers * Preventing the calls to scsi_add_host() et all in the USB layer Some more specific questions: * Is any documentation regarding the design and requirements of power operations in the Linux SCSI code available on the internet? * Besides host self-blocking (shost->host_self_blocked), does SCSI have any facility for host "pausing" or temporary disconnection? * Is this a problem for the SCSI layer at all, or does the USB / USB Mass Storage layer need to handle it? Thank you for your time, --Rick R.

1 0

Re: how to use mmap() on a disk file to get a kernel address?
by Yu Bi Jan. 6, 2014

Jan. 6, 2014

Thanks for your idea. Because I implement a kernel storage service based on a disk file through VFS layer. To simplify the implementation, I prefer to read/write the mapped kernel space address instead of the file data access api(such as page cache API / VFS API). In FreeBSD, I can use vm_map_find to map a file into kernel space address( vnode pager) But in linux, I don't know how to implement this(map disk file into kernel space)? On Thu, Dec 26, 2013 at 3:42 PM, Yu Bi <lazysmartegg(a)gmail.com> wrote: > Hi, > I try to mmap a file in a linux kernel module. I have tried to use the > function do_mmap_pgoff. But the address returned is memory virtual > address in current process' user space, i.e., below the kernel boundary. > Instead, I want to map the file in the kernel space and get the kernel > virtual address of the mapped region. Is there any kernel API in Linux > support this operation? Or I have to reimplement a kernel mmap version ? > But reimplement a kernel version mmap() is not easy I guess. Do you > have any idea? > > > > > >

2 1