Re: [PATCH] docs/devel: Explain in more detail the TB chaining mechanisms

2021-05-29 Thread Richard Henderson
On 5/28/21 1:15 PM, Luis Fernando Fujita Pires wrote: From: Richard Henderson More completely, update the CPU state with any information that has been assumed constant. For most guests, this is just the PC. But e.g. for hppa this is both iaoq.f (cip) and iaoq.b (nip). It is very much up to t

RE: [PATCH] docs/devel: Explain in more detail the TB chaining mechanisms

2021-05-28 Thread Luis Fernando Fujita Pires
From: Richard Henderson > More completely, update the CPU state with any information that has been > assumed constant. For most guests, this is just the PC. But e.g. for hppa > this is both iaoq.f (cip) and iaoq.b (nip). > > It is very much up to the guest to determine the set of data that is p

Re: [PATCH] docs/devel: Explain in more detail the TB chaining mechanisms

2021-05-28 Thread Richard Henderson
On 5/28/21 5:30 AM, Luis Pires wrote: +In its simplest, less optimized form, this is done by exiting from the +current TB, going through the TB epilogue, and then back to the outer +execution loop. That’s where QEMU looks for the next TB to execute, +translating it from the guest architecture if