Hello, I had looked at the Documentation/sysrq.txt) and at the code (sysrq.c) and it seems to me that pressing a combination of sysrq keys does not create a special interrupt except the standard keyboard interrupt (which I do not want to use from reasons explaned before). am I right ? Does anybodu know about a solution to my requirements ? TIA, Rgs, John On 7/26/05, chgans@xxxxxxx <chgans@xxxxxxx> wrote: > Selon John Que <qwejohn@xxxxxxxxx>: > > > Hello, > > Thanks. > > If the timer you are talking about is not an interrupt driven > > timer than it is not suitable; > > or if it uses the usual linux timer interrupt than it is not > > suitable because this timer interrupt occurs many times in a second. > > > > My aim is to write a simple module which generate single > > interrupts which can be generated from user space > > or by some hw (like a keyboard sequence). > Hi, > > Why not hacking the SysReq linux feature? > It's a keyboard sequence that trigger some internal mechanism to dump some > interesting information (see Documentation/sysrq.txt) > > Christian > > > > > For what is this good ? > > I want to use it as a tool for tracing the interrupt > > mechanism of Xen , which is a bit different than the ordinary one on > > Linux. Since I don't want to add printk > > messages in a way which will bloat and cause the kernel hang, I want > > to use a driver like this. Generating single interrupts upon some > > predefined action will help me a lot; > > and also this explains (I hope) why I do not want to use timer (or > > other device which causes a lot of interrupts per second): timer > > interrupts frequency is too high. > > > > I will gladly answer any other questions regarding this. > > John > > > > > > On 7/26/05, Thomas Petazzoni <thomas.petazzoni@xxxxxxxx> wrote: > > > Hello, > > > > > > John Que wrote: > > > > > > > If there is a way to do such a thing : to register a device interreupt > > > > (in the range 1-16), so that a use space program (like ioctl , or cat > > > > /dev/mymodle , etc.) will > > > > generate such interrupt ? ( Or let's say pressing some keyboard > > combinatiion ?) > > > > > > Can you be more precise about the condition under which your interrupt > > > handler should be called ? > > > > > > I have the feeling that what you need is not an interrupt handler per-se > > > but rather a timer. But give more details first. > > > > > > Sincerly, > > > > > > Thomas > > > -- > > > Thomas Petazzoni > > > thomas.petazzoni@xxxxxxxx > > > > > > > -- > > Kernelnewbies: Help each other learn about the Linux kernel. > > Archive: http://mail.nl.linux.org/kernelnewbies/ > > FAQ: http://kernelnewbies.org/faq/ > > > > > > > -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
