disabling interrupts/scheduling in ioctl() handler
From: Ulrich Eckhardt (doomster_at_knuut.de)
Date: 03/30/04
- Next message: Kasper Dupont: "Re: disabling interrupts/scheduling in ioctl() handler"
- Previous message: Kasper Dupont: "Re: Obtaining the "ps ax" pid from a thread?"
- Next in thread: Kasper Dupont: "Re: disabling interrupts/scheduling in ioctl() handler"
- Reply: Kasper Dupont: "Re: disabling interrupts/scheduling in ioctl() handler"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 30 Mar 2004 11:29:16 +0200
Hi!
The topic already says almost all, I am accessing a dual-port RAM[1] and I
must not have a shared address selected for a longer time(because that
blocks accesses on the other side). Time constraints could live with
IRQs(possibly) but by no means with scheduling.
What is the preferred way to disable scheduling? Can that happen at all,
while in the ioctl() handler?
Another related question is about copy_to_user(): docs mention that this
might sleep, so I better avoid this function while in a section where I
must not be interrupted/scheduled, right?
thanks for your input,
Ulrich Eckhardt
[1] RAM with two address/data busses, one connected to the PCI bus, the
other to a microcontroller
-- Questions ? see C++-FAQ Lite: http://parashift.com/c++-faq-lite/ first !
- Next message: Kasper Dupont: "Re: disabling interrupts/scheduling in ioctl() handler"
- Previous message: Kasper Dupont: "Re: Obtaining the "ps ax" pid from a thread?"
- Next in thread: Kasper Dupont: "Re: disabling interrupts/scheduling in ioctl() handler"
- Reply: Kasper Dupont: "Re: disabling interrupts/scheduling in ioctl() handler"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]