On Mon, Sep 10, 2012 at 12:17:02PM +0100, Alan Cox wrote:
[...]
> > +static void pl011_clear_irqs(struct uart_port *port)
> > +{
> > + struct uart_amba_port *uap = (struct uart_amba_port *)port;
> > + unsigned char __iomem *regs = uap->port.membase;
> > +
> > + writew(readw(regs + UART011_MIS), regs + UART011_ICR);
> > + /*
> > + * There is no way to clear TXIM, this is "ready to transmit IRQ", so
> > + * we simply mask it. ops->start_tx will unmask it.
> > + */
>
> Not if you race here with the transmit start it won't.
True, the race is possible. But I guess there will be no harm: only non-polling
code uses ->start_tx(), but then we don't care, the port is used for NMI
debugger, so the worst that can happen, is that we'll get another NMI just
after the race, and so we'll mask it again.
And once we release the port from KDB, we never call this function anymore
(since normal IRQ routine will be called instead).
I guess I need to add some commens about this.
Thanks!
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Kgdb-bugreport mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
