On Fri, Jan 17, 2020 at 04:22:11PM +0100, Marek Marczykowski-Górecki wrote: > On Fri, Jan 17, 2020 at 01:58:25PM +0100, Gerd Hoffmann wrote: > > > Should switching to bochsdrmfb be deferred until efifb gets properly > > > destroyed? How? > > > > Should be in do_remove_conflicting_framebuffers, everyone might run into > > this. So lets try wait for all (other) references went away: > > Yes, this solves the problem. I guess the proper solution would be to > replace it with some wait queue or such, right? Not sure a wait queue would actually be better. > Is there any guarantee that the process holding /dev/fb0 (plymouthd in > this case) will eventually release it? No. So it'll probably makes sense to limit the time we are willing to wait here. Or maybe take a completely different path and make the reservation failure in bochs-drm a warning not an error. cheers, Gerd _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
