On Fri, 30 May 2008 15:19:43 -0500 Scott Wood <scottwood@xxxxxxxxxxxxx> wrote: > Kim Phillips wrote: > > On Fri, 30 May 2008 14:41:17 -0500 > > Scott Wood <scottwood@xxxxxxxxxxxxx> wrote: > > > >> Kim Phillips wrote: > >>> On Fri, 30 May 2008 22:09:04 +0400 > >>> Evgeniy Polyakov <johnpol@xxxxxxxxxxx> wrote: > >>>> Don't you want to protect against simultaneous access to register space > >>>> from different CPUs? Or it is single processor board only? > >>> Doesn't linux mask the IRQ line for the interrupt currently being > >>> serviced, and on all processors? > >> Yes. Could there be interference from non-interrupt driver code on > >> another cpu (or interrupted code), though? > > > > not that I can see - the fetch fifo register writes are protected with > > per-channel spinlocks. > > But you don't take the spinlocks from the interrupt handler. why can't fetch fifo registers be written the same time the ISR is being accessed? Kim -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
