> Ok, makes sense. Tom Hughes suggested that I create a bug and attach > my patch, so that's what I did. If it is going to be a significant > performance hit, maybe it would be better to have an option that can > turn this on for all syscalls?
In the past we've simply added the SfMayBlock flags on an ad-hoc basis, on demand, and for the most part that's worked pretty well. It may be that you only need to add that flag to enough syscalls to break cycles of threads waiting for each other: once one link in the cycle is broken then it won't deadlock. I guess that's not robust in the worst case though, so all affected syscalls would need to be marked. Your patch on bug 287057 looks OK, although it would be good if you could fill in at least the amd64-linux equivalents too. J ------------------------------------------------------------------------------ Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
