> >> The main problem is that we have just merged Sai's code to use a work
> >> queue for invoking EFI services, and killing kworker threads is
> >> obviously not going to make EFI any new friends.
> >>
> >> So I guess we should probably rework that code to use a dedicated
> >> kthread, and just freeze it when it performs an illegal memory
> >> access, and signal the completion in a way that makes the calling
> >> thread understand that a) the call failed and b) runtime services are no longer
> available.
> >
> > Yes, this makes sense to me.
> > Initially I did use a dedicated kthread for efi but moved to work queues later so
> that the synchronization is well handled. I am ok to rework on the patches, could
> we ask Ingo to hold onto efi_workqueue patches?
> >
>
> I am fine with keeping them. We will have a different approach in
> v4.19 than in subsequent kernels, but the workqueue approach is still better than
> nothing at all.
Makes sense to me.
��.n��������+%������w��{.n�����{����* jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
