[question] why does rtc_read() use spin_lock_irq()?

• Next message: Jes Sorensen: "Re: monotone polling in a driver"
• Previous message: Andi Kleen: "Re: Query on UDP Sockets on Linux."
• Next in thread: Jeff Garzik: "Re: [question] why does rtc_read() use spin_lock_irq()?"
• Reply: Jeff Garzik: "Re: [question] why does rtc_read() use spin_lock_irq()?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi guys,

It would appear that fop->read() methods assume that interrupts are always
enabled on the current cpu. For example, drivers/char/rtc:rtc_read() uses
spin_lock_irq(&rtc_lock) while the interrupt handler uses the plain
spin_lock(&rtc_lock). It is clear why rtc_interrupt() use spin_lock() but
is not clear why rtc_read() uses spin_lock_irq() and not the generic
spin_lock_irqsave().

Anyone knows why?

regards,
Tigran

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Jes Sorensen: "Re: monotone polling in a driver"
• Previous message: Andi Kleen: "Re: Query on UDP Sockets on Linux."
• Next in thread: Jeff Garzik: "Re: [question] why does rtc_read() use spin_lock_irq()?"
• Reply: Jeff Garzik: "Re: [question] why does rtc_read() use spin_lock_irq()?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Jun 26 2000 - 21:00:09 EST