diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
| commit | d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch) | |
| tree | f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/deepseek-2-tmp/output/hypervisor/1867072 | |
| parent | 7f4364274750eb8cb39a3e7493132fca1c01232e (diff) | |
| download | qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip | |
add deepseek and gemma results
Diffstat (limited to 'results/classifier/deepseek-2-tmp/output/hypervisor/1867072')
| -rw-r--r-- | results/classifier/deepseek-2-tmp/output/hypervisor/1867072 | 10 |
1 files changed, 0 insertions, 10 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/hypervisor/1867072 b/results/classifier/deepseek-2-tmp/output/hypervisor/1867072 deleted file mode 100644 index 3c81a4556..000000000 --- a/results/classifier/deepseek-2-tmp/output/hypervisor/1867072 +++ /dev/null @@ -1,10 +0,0 @@ - -ARM: tag bits cleared in FAR_EL1 - -The ARM Architecture Reference Manual provides the following for FAR_EL1: - -"For a Data Abort or Watchpoint exception, if address tagging is enabled for the address accessed by the data access that caused the exception, then this field includes the tag." - -However, I have found that the tag bits in FAR_EL1 are always clear, even if the tag bits were set in the original access. - -I can reproduce the problem on both 4.1.1 and master (6e8a73e911f066527e775e04b98f31ebd19db600). \ No newline at end of file |