Hi, Bill, Matias

For this bug related to the validation scheduler test program, with errors
like:

scheduler.c:878 - bctx->sequence == seq

I saw a potential problem in the validation scheduler program code itself:

After schedule events, it makes copies of these events,
which did not retain ordered information attached to the
original ones (buffer_header->origin_qe, etc), by enqueue
these copies and release those original events the ordered
information were lost.

I'd like to know what's the defined behavior, for when a thread holds an
ordered context, and allocate new events and enqueue them, shall these new
allocated events preserve the ordered restriction also?

Because if this is the expected behavior, then the event allocation
function should be fixed to inheritate ordered information from the ordered
context, right?

Otherwise we can fix it in the validation scheduler program code.

Best Regards, Yi

Reply via email to