[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Concurrency, again
From: |
Eli Zaretskii |
Subject: |
Re: Concurrency, again |
Date: |
Thu, 20 Oct 2016 10:54:39 +0300 |
> From: Ken Raeburn <address@hidden>
> Date: Thu, 20 Oct 2016 02:08:14 -0400
> Cc: address@hidden
>
> I just tried a test with a breakpoint in redisplay_internal; it can get
> called from threads other than the main thread. As far as I know, we can’t
> have multiple threads in the redisplay code at the same time, though.
But redisplay_internal will return immediately without doing anything
if it's already running in some other thread. (And this "running in
some other thread could only happen if that other thread somehow
succeeded to block or yield in the middle of redisplay, which I think
is only possible if it calls Lisp.)
- Re: Concurrency, again, (continued)
- Re: Concurrency, again, Perry E. Metzger, 2016/10/17
- Re: Concurrency, again, Tom Tromey, 2016/10/17
- Re: Concurrency, again, Eli Zaretskii, 2016/10/18
- Re: Concurrency, again, Ken Raeburn, 2016/10/18
- Re: Concurrency, again, Eli Zaretskii, 2016/10/18
- Re: Concurrency, again, Ken Raeburn, 2016/10/18
- Re: Concurrency, again, Eli Zaretskii, 2016/10/18
- Re: Concurrency, again, Ken Raeburn, 2016/10/19
- Re: Concurrency, again, Eli Zaretskii, 2016/10/19
- Re: Concurrency, again, Ken Raeburn, 2016/10/20
- Re: Concurrency, again,
Eli Zaretskii <=
- RE: Concurrency, again, Herring, Davis, 2016/10/20
- Re: Concurrency, again, Ken Raeburn, 2016/10/20
- Re: Concurrency, again, Paul Eggert, 2016/10/20
- Re: Concurrency, again, Alan Third, 2016/10/18
- Re: Concurrency, again, Ken Raeburn, 2016/10/19
- Re: Concurrency, again, Tom Tromey, 2016/10/18
- Re: Concurrency, again, Philipp Stephani, 2016/10/25
- Re: Concurrency, again, Eli Zaretskii, 2016/10/25
- Re: Concurrency, again, John Wiegley, 2016/10/25
- Re: Concurrency, again, Philipp Stephani, 2016/10/25