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/1217 | |
| parent | 63d2e9d409831aa8582787234cae4741847504b7 (diff) | |
| download | qemu-analysis-main.tar.gz qemu-analysis-main.zip | |
Diffstat (limited to 'results/scraper/fex/1217')
| -rw-r--r-- | results/scraper/fex/1217 | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/results/scraper/fex/1217 b/results/scraper/fex/1217 new file mode 100644 index 000000000..94b9f97dc --- /dev/null +++ b/results/scraper/fex/1217 @@ -0,0 +1,19 @@ +Support SIGILL to the guest +Currently FEX will just close an application if it encounters a block with an invalid instruction. +We can support giving the guest a SIGILL. +This should be done in two steps to reduce the amount of immediate work + +1) Support the use-case of SIGILL + guest handler terminate + - This means that once the frontend encounters and invalid operation. + - Save Thread state + - End the Block + - Call a SIGILL host side handler + - Pass the signal information to the guest + - Invoke the guests signal handler with the known good information + - Guest will invoke terminate, thus taking down the application and FEX with it + 2) Once step 1 is done, support use cases where an application is testing for instructions and safely recovering + - Guest will modify the passed in ucontext once it has caught the sigill + - Most likely modifying RIP to jump past the instruction, or using longjump to escape + - Will likely also modify another GPR to know the failure case + - Once the guest has returned from its signal, we need to read the state back in to our context and safely continue + - This can benefit more than SIGILL later once we have some form of state recovery for the other signals. \ No newline at end of file |