Bind to CPU about libafl-legacy HOT 7 CLOSED

as this gives a huge performance increase - yes, yes and yes.

from libafl-legacy.

I've started working on this over here. https://github.com/AFLplusplus/LibAFL/tree/bind_to_cpu

from libafl-legacy.

nice!
One thing though I don't see a reason to making the actual bind functions depending on the engine, right? Maybe instead return the bound cpu index, or -1 on error?

from libafl-legacy.

I was thinking over something, about storing the bound cpu in engine somewhere. So that when we restart the engine we can possibly bind it again to that cpu? What do you think?

from libafl-legacy.

Btw @domenukk any chance of any race condition during cpu binding? two instances being bound to the same cpu?

from libafl-legacy.

I was thinking over something, about storing the bound cpu in engine somewhere. So that when we restart the engine we can possibly bind it again to that cpu? What do you think?

That is possible without taking an engine pointer. The caller can call bindcpu the first time around, and bind to a speciific cpu the second time.

Btw @domenukk any chance of any race condition during cpu binding? two instances being bound to the same cpu?

Original afl had a race condition here, but I think @vanhauser-thc fixed it at some point(?)

from libafl-legacy.

Done with #42

from libafl-legacy.