qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 00/18] Stop all qemu-cpu threads on a breakpoint


From: Richard Henderson
Subject: Re: [PATCH 00/18] Stop all qemu-cpu threads on a breakpoint
Date: Tue, 24 Sep 2024 13:46:43 +0200
User-agent: Mozilla Thunderbird

On 9/23/24 18:12, Ilya Leoshkevich wrote:
Hi,

On reporting a breakpoint in a non-non-stop mode, GDB remotes must stop
all threads. Currently qemu-user doesn't do that, breaking the
debugging session for at least two reasons: concurrent access to the
GDB socket, and an assertion within GDB [1].

This series fixes this by importing pause_all_vcpus() from qemu-system.
This in turn requires introducing BQL and a few stubs to qemu-user.

I would have expected you to reuse (some portion of) start_exclusive, which is already part of qemu-user. Is there a reason you chose a solution which requires...

   replay: Add replay_mutex_{lock,unlock}() stubs for qemu-user
   qemu-timer: Provide qemu_clock_enable() stub for qemu-user
   cpu: Use BQL in qemu-user

all sorts of other infrastructure?


r~



reply via email to

[Prev in Thread] Current Thread [Next in Thread]