On Tue, Feb 1, 2011 at 12:30, Peter Maydell wrote: > On 1 February 2011 17:20, Mike Frysinger wrote: >> On Tue, Feb 1, 2011 at 05:31, Peter Maydell wrote: >>> I suspect that this check of pc against the lbreg[] >>> values should be being done in the generated code, >>> not at translate time. >> >> the way i'm doing it atm i believe is safe. if a lbreg changes, then >> i invalidate any TBs associated with the old value and any TBs >> associated with the new value. thus i force the code to be >> retranslated, and i can assume the lbreg values are constant when >> doing so. > > That's OK too, that would fall into my category (3).
so the TB invalidation checking can be taken care of implicitly if i handled things in cpu_get_tb_cpu_state() ? that would be nice. but i guess i'm not seeing how i would handle this scenario ... i want to attach to each TB the state of the two 32bit lbregs when that TB was created. then in this state func, make sure the current lbregs have the same values. but if i need to encode this information into "flags", i dont think i have enough space. -mike
