On Sat, Jun 11, 2005 at 05:16:46PM +0200, Andrea Arcangeli wrote:
> On Fri, Jun 10, 2005 at 06:07:55PM -0700, Paul E. McKenney wrote:
> > f. Any code that manipulates hardware that can stall the
> > bus, delay interrupts, or otherwise interfere with
> > forward progress. Note that it is also necessary to
> > inspect user-level code that directly manipulates such
> > hardware.
> >
> > I added point "f". Does that cover it?
>
> Yes. F is really a bad problem if it really can cause DMA starvation on
> the memory bus on some arch as stated on this thread. Hopefully
> measurements are good enough to rule it out and there will be no corner
> cases triggering once in a while.
Agreed!
But who knows? Maybe we can convince some HW manufacturers to make
their memory and I/O systems better. So it might also be good to have
tests that forced the conditions as well as tests that avoid them.
Though such tests do sound horribly hardware dependent...
Thanx, Paul
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
