On Fri, 28 Feb 2014 18:34:00 -0500 (EST) Vince Weaver <vincent.wea...@maine.edu> wrote:
> > I was poking fun at you on IRC for this exact reason: > > > > <rostedt> poor Vince, I keep sending him new patches. "No, don't test this > > patch, now test this one. Oh wait, try this one instead" > > * peterz sees Vince thinking: "stop... sending.. me.. damn... patches... > > already... !!!11!" > > <rostedt> or at least, "Let me finish this test before I cancel it again > > for another damn patch" > > <rostedt> then he's probably doing "I'm not going to run any tests now, > > until I wait a while to see if there's a new patch to test" I hope you were not offended by this. It was actually a testament to the work you've given us. > > Well while it might appear that I spend all of my days finding perf_event > bugs, I actually am a college professor so I do occasionally have to run > off to teach a class, meet with students, or write papers/grants for other > academics to reject. But perf_event bug finder is a much more prestigious title than "college professor" ;-) > > It's nice others can reproduce the issue now, it would have saved me a lot > of trouble, although now in theory I have a much better handle of how to > use/abuse ftrace so I guess it was worth it. I always enjoy finding bugs in other people's code. That's usually the best way to learn what their code does. > > Once the fix gets into git I'm sure the relentless perf_fuzzer will let us > know if there are any other issues left. I do look forward to the day > when I can leave it running overnight and have a clean syslog the next > morning. BTW, is the perf_fuzzer code posted somewhere? It sounds like it can be really useful for us to do our own testing too. Thanks, -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
