blob: 754032272251f8f3f32564d9fe4fd0ab616e0fce (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Alright, I'm trying to classify this bug report as either user-mode or system-mode related. Let's break down the information given.
The issue occurs when a SEGV signal happens in QEMU. The problem is that when the si_addr of the info struct is nil, QEMU still tries to translate the address from host to guest. This results in an incorrect fault_addr being received by the signal handler, something like 0xffffffffbf709000.
The reporter mentions they were using a specific configure script with flags including --target-list=aarch64-linux-user and --disable-system. The fact that it's a user target suggests it's about user-mode emulation since system targets would include things like hardware devices and higher privileges.
User-mode QEMU typically deals with running applications without emulating an entire OS, focusing on CPU instruction translation. System-mode involves emulating the whole system, including peripherals and kernel-level operations.
Given that the problem arises in the user-exec.c file under accel/tcg, which is part of the TCG (Translation-Cache-Based Generator) used for user-mode emulation, it's clear this is a user-mode issue.
</think>
user
|