[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC v2 04/11] tcg: comment on which functions have to
From: |
Sergey Fedorov |
Subject: |
Re: [Qemu-devel] [RFC v2 04/11] tcg: comment on which functions have to be called with tb_lock held |
Date: |
Thu, 5 May 2016 17:19:48 +0300 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 |
On 05/04/16 18:32, Alex Bennée wrote:
> diff --git a/exec.c b/exec.c
> index f46e596..17f390e 100644
> --- a/exec.c
> +++ b/exec.c
> @@ -826,6 +826,7 @@ int cpu_breakpoint_insert(CPUState *cpu, vaddr pc, int
> flags,
> {
> CPUBreakpoint *bp;
>
> + /* TODO: locking (RCU?) */
> bp = g_malloc(sizeof(*bp));
>
> bp->pc = pc;
This comment is a little inconsistent. We should make access to
breakpoint and watchpoint lists to be thread-safe in all the functions
using them. So if we note this, it should be noted in all such places.
Also, it's probably not a good idea to put such comment just above
g_malloc() invocation, it could be a bit confusing. A bit more details
would also be nice.
Kind regards,
Sergey
- Re: [Qemu-devel] [RFC v2 04/11] tcg: comment on which functions have to be called with tb_lock held,
Sergey Fedorov <=