Re: [PATCH 4/8] user: Introduce host_interrupt_signal

2024-11-05 Thread Warner Losh
On Tue, Nov 5, 2024 at 3:49 PM Ilya Leoshkevich wrote: > On Tue, 2024-11-05 at 22:30 +, Richard Henderson wrote: > > On 11/5/24 15:50, Ilya Leoshkevich wrote: > > > On Tue, 2024-11-05 at 08:39 -0700, Warner Losh wrote: > > > > On Thu, Oct 24, 2024 at 2:00 PM Ilya Leoshkevich > > > > > > > >

Re: [PATCH 4/8] user: Introduce host_interrupt_signal

2024-11-05 Thread Ilya Leoshkevich
On Tue, 2024-11-05 at 22:30 +, Richard Henderson wrote: > On 11/5/24 15:50, Ilya Leoshkevich wrote: > > On Tue, 2024-11-05 at 08:39 -0700, Warner Losh wrote: > > > On Thu, Oct 24, 2024 at 2:00 PM Ilya Leoshkevich > > > > > > wrote: > > > > Attaching to the gdbstub of a running process requires

Re: [PATCH 4/8] user: Introduce host_interrupt_signal

2024-11-05 Thread Richard Henderson
On 11/5/24 15:50, Ilya Leoshkevich wrote: On Tue, 2024-11-05 at 08:39 -0700, Warner Losh wrote: On Thu, Oct 24, 2024 at 2:00 PM Ilya Leoshkevich wrote: Attaching to the gdbstub of a running process requires stopping its threads. For threads that run on a CPU, cpu_exit() is enough, but the only

Re: [PATCH 4/8] user: Introduce host_interrupt_signal

2024-11-05 Thread Ilya Leoshkevich
On Tue, 2024-11-05 at 08:39 -0700, Warner Losh wrote: > On Thu, Oct 24, 2024 at 2:00 PM Ilya Leoshkevich > wrote: > > Attaching to the gdbstub of a running process requires stopping its > > threads. For threads that run on a CPU, cpu_exit() is enough, but > > the > > only way to grab attention of

Re: [PATCH 4/8] user: Introduce host_interrupt_signal

2024-11-05 Thread Warner Losh
On Thu, Oct 24, 2024 at 2:00 PM Ilya Leoshkevich wrote: > Attaching to the gdbstub of a running process requires stopping its > threads. For threads that run on a CPU, cpu_exit() is enough, but the > only way to grab attention of a thread that is stuck in a long-running > syscall is to interrupt

Re: [PATCH 4/8] user: Introduce host_interrupt_signal

2024-11-05 Thread Richard Henderson
On 10/24/24 20:59, Ilya Leoshkevich wrote: Attaching to the gdbstub of a running process requires stopping its threads. For threads that run on a CPU, cpu_exit() is enough, but the only way to grab attention of a thread that is stuck in a long-running syscall is to interrupt it with a signal. Re

[PATCH 4/8] user: Introduce host_interrupt_signal

2024-10-24 Thread Ilya Leoshkevich
Attaching to the gdbstub of a running process requires stopping its threads. For threads that run on a CPU, cpu_exit() is enough, but the only way to grab attention of a thread that is stuck in a long-running syscall is to interrupt it with a signal. Reserve a host realtime signal for this, just l