qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>,
	"Ilya Leoshkevich" <iii@linux.ibm.com>
Cc: "Laurent Vivier" <laurent@vivier.eu>,
	"Warner Losh" <imp@bsdimp.com>, "Kyle Evans" <kevans@freebsd.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH v3 02/11] {linux,bsd}-user: Update ts_tid after fork()
Date: Sat, 17 Feb 2024 10:22:40 -1000	[thread overview]
Message-ID: <ccd10805-0f0b-4731-8c91-899b1b55fce5@linaro.org> (raw)
In-Reply-To: <87ttm82thj.fsf@draig.linaro.org>

On 2/16/24 07:45, Alex Bennée wrote:
> Ilya Leoshkevich <iii@linux.ibm.com> writes:
> 
>> Currently ts_tid contains the parent tid after fork(), which is not
>> correct. So far it has not affected anything, but the upcoming
>> follow-fork-mode child support relies on the correct value, so fix it.
>>
>> Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
>> ---
>>   bsd-user/main.c   | 1 +
>>   linux-user/main.c | 1 +
>>   2 files changed, 2 insertions(+)
>>
>> diff --git a/bsd-user/main.c b/bsd-user/main.c
>> index e5efb7b8458..4140edc8311 100644
>> --- a/bsd-user/main.c
>> +++ b/bsd-user/main.c
>> @@ -127,6 +127,7 @@ void fork_end(int child)
>>            * state, so we don't need to end_exclusive() here.
>>            */
>>           qemu_init_cpu_list();
>> +        ((TaskState *)thread_cpu->opaque)->ts_tid = qemu_get_thread_id();
>>           gdbserver_fork(thread_cpu);
>>       } else {
>>           mmap_fork_end(child);
>> diff --git a/linux-user/main.c b/linux-user/main.c
>> index 74b2fbb3938..e6427d72332 100644
>> --- a/linux-user/main.c
>> +++ b/linux-user/main.c
>> @@ -160,6 +160,7 @@ void fork_end(int child)
>>               }
>>           }
>>           qemu_init_cpu_list();
>> +        ((TaskState *)thread_cpu->opaque)->ts_tid = qemu_get_thread_id();
>>           gdbserver_fork(thread_cpu);
>>       } else {
>>           cpu_list_unlock();
> 
> Given how many functions do this cast dance it does make we wonder if we
> should just have a helper for *-user:
> 
>    TaskState * get_task_state(CPUState *cs)
>    {
>          return (TaskState *) cs->opaque;
>    }
> 
> and be done with it. Richard?

Seems like a good idea.


r~


  reply	other threads:[~2024-02-17 20:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-16 13:05 [PATCH v3 00/11] gdbstub: Implement follow-fork-mode child Ilya Leoshkevich
2024-02-16 13:05 ` [PATCH v3 01/11] gdbstub: Support disablement in a multi-threaded process Ilya Leoshkevich
2024-02-16 17:04   ` Alex Bennée
2024-02-17 20:21   ` Richard Henderson
2024-02-19 13:05     ` Ilya Leoshkevich
2024-02-19 14:18       ` Ilya Leoshkevich
2024-02-16 13:05 ` [PATCH v3 02/11] {linux,bsd}-user: Update ts_tid after fork() Ilya Leoshkevich
2024-02-16 17:45   ` Alex Bennée
2024-02-17 20:22     ` Richard Henderson [this message]
2024-02-16 13:05 ` [PATCH v3 03/11] gdbstub: Introduce gdbserver_fork_start() Ilya Leoshkevich
2024-02-16 17:46   ` Alex Bennée
2024-02-16 13:05 ` [PATCH v3 04/11] {linux,bsd}-user: Pass pid to fork_end() Ilya Leoshkevich
2024-02-16 17:48   ` Alex Bennée
2024-02-17 20:26   ` Richard Henderson
2024-02-16 13:05 ` [PATCH v3 05/11] {linux,bsd}-user: Pass pid to gdbserver_fork() Ilya Leoshkevich
2024-02-17 20:27   ` Richard Henderson
2024-02-16 13:05 ` [PATCH v3 06/11] gdbstub: Call gdbserver_fork() both in parent and in child Ilya Leoshkevich
2024-02-17 20:30   ` Richard Henderson
2024-02-16 13:05 ` [PATCH v3 07/11] gdbstub: Introduce gdb_handle_query_supported_user() Ilya Leoshkevich
2024-02-17 20:36   ` Richard Henderson
2024-02-16 13:05 ` [PATCH v3 08/11] gdbstub: Introduce gdb_handle_set_thread_user() Ilya Leoshkevich
2024-02-16 13:05 ` [PATCH v3 09/11] gdbstub: Introduce gdb_handle_detach_user() Ilya Leoshkevich
2024-02-16 13:05 ` [PATCH v3 10/11] gdbstub: Implement follow-fork-mode child Ilya Leoshkevich
2024-02-16 13:05 ` [PATCH v3 11/11] tests/tcg: Add two follow-fork-mode tests Ilya Leoshkevich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ccd10805-0f0b-4731-8c91-899b1b55fce5@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=iii@linux.ibm.com \
    --cc=imp@bsdimp.com \
    --cc=kevans@freebsd.org \
    --cc=laurent@vivier.eu \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).