On Tue, 22 Nov 2022 at 08:04, Akihiko Odaki wrote:
>
> Hi,
>
> On 2022/11/22 7:37, Philippe Mathieu-Daudé wrote:
> > Cc'ing more UI/display contributors.
> >
> > On 17/11/22 14:05, Peter Maydell wrote:
> >> On Tue, 1 Nov 2022 at 14:17, Peter Maydell
> >> wrote:
> >>>
> >>> Hi; I'm trying to find
Hi,
On 2022/11/22 7:37, Philippe Mathieu-Daudé wrote:
Cc'ing more UI/display contributors.
On 17/11/22 14:05, Peter Maydell wrote:
On Tue, 1 Nov 2022 at 14:17, Peter Maydell
wrote:
Hi; I'm trying to find out what the UI layer's threading and
locking strategy is, at least as far as it
Cc'ing more UI/display contributors.
On 17/11/22 14:05, Peter Maydell wrote:
On Tue, 1 Nov 2022 at 14:17, Peter Maydell wrote:
Hi; I'm trying to find out what the UI layer's threading and
locking strategy is, at least as far as it applies to display
device models.
Ping! :-) I'm still
On Tue, 1 Nov 2022 at 14:17, Peter Maydell wrote:
>
> Hi; I'm trying to find out what the UI layer's threading and
> locking strategy is, at least as far as it applies to display
> device models.
Ping! :-) I'm still looking for information about this,
and about what threads call_rcu() callbacks
Hi; I'm trying to find out what the UI layer's threading and
locking strategy is, at least as far as it applies to display
device models.
Specifically:
* is the device's GraphicHwOps::gfx_update method always called
from one specific thread, or might it be called from any thread?
* is that
