Messages in this thread | | | Date | Wed, 10 Sep 2003 16:47:04 +0100 | From | John Bradford <> | Subject | Re: Lock EVERYTHING (for testing) [was: Re: Scaling noise] |
| |
> The analogy for Linux is this: At a machine level, we add a check to > EVERY access. The check is there to ensure that every memory access is > properly locked. So, if some access is made where there isn't a proper > lock applied, then we can print a warning with the line number or drop > out into kdb or something of that sort. > > I'm betting there's another solution to this, otherwise, I wouldn't > suggest such an idea, because of the relative amount of work versus > benefit. But it may require massive modifications to GCC to add this > code in at the machine level.
Couldn't Valgrind be modified to do this for the kernel?
http://developer.kde.org/~sewardj/
John. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |