Due to the involvement of qemu and the way code is structured, re-execution of insns under emulation is frequently necessary. Such re-execution must under no circumstance take a path different from the one the original execution(s) has (have) taken. This in particular means that page walks done to emulate memory accesses cannot be allowed to read different data from guest page tables during re-execution than what was read originally, which implies that data read (and possibly also data written) needs to be "cached".
The purpose of this session is to come to an agreement how to best arrange for such caching, and how to best integrate it also taking into consideration further plans on changes to our emulation paths.
Scheduling note: The presumed audience for this is small, so if we're tight on slots, then this is a prime candidate to scratch, in which case the topic will be converted to an informal talk.
Design sessions are NOT presentations, but problem-solving sessions with tangible output (e.g. a set of notes published on a list, photos of whiteboards, etc). There is also no pre-determined schedule: attendees will vote which sessions they plan to attend
during the event. Our design session scheduling tool will do automatic scheduling based on attendee input and minimize conflicts between attendees.
Design sessions can be submitted at any time, even during the event. To submit a design session, go to
https://design-sessions.xenproject.org.
Examples of design sessions already submitted for this year’s summit are:
For a full list of submitted design sessions, go to
https://design-sessions.xenproject.org/list/discussion
