diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-17 09:10:43 +0200 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-17 09:10:43 +0200 |
| commit | f2ec263023649e596c5076df32c2d328bc9393d2 (patch) | |
| tree | 5dd86caab46e552bd2e62bf9c4fb1a7504a44db4 /results/scraper/fex/1772 | |
| parent | 63d2e9d409831aa8582787234cae4741847504b7 (diff) | |
| download | qemu-analysis-main.tar.gz qemu-analysis-main.zip | |
Diffstat (limited to 'results/scraper/fex/1772')
| -rw-r--r-- | results/scraper/fex/1772 | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/results/scraper/fex/1772 b/results/scraper/fex/1772 new file mode 100644 index 000000000..dc6699386 --- /dev/null +++ b/results/scraper/fex/1772 @@ -0,0 +1,14 @@ +TCBs: Track metadata fragment metadata internally, not in InternalThreadState::DebugStore +#### Current Situation +Currently, debug metadata is tracked by its guest entrypoint, and it is assumed that there's an 1:1 mapping between fragments and guest entry points. + +There are a number of cases where this is not true. The current fragment may be invalidated, but still executing. eg +- Cross thread SMC invalidation +- Signal or thunk return +- Shared memory mode migration +- Possibly others + +There is also a race condition, as debug metadata corresponds to a specific version of a fragment, however a guest entrypoint is inherently not versioned. + +#### Proposal +We can track debug (and other) metadata, as part of the host fragment translation. This way, we will be able to locate the correct version. Metadata clearing will also become a responsibility of the backend, which will reduce the context's responsibilities. To get debug data for a specific translation, a host TCB ptr will be required. \ No newline at end of file |