Re: second, sync-alloc syscall

Andy Lutomirski
2021-05-27T19:36:25Z

On Thu, May 27, 2021, at 6:59 AM, Len Brown wrote:
> On Thu, May 27, 2021 at 7:14 AM Borislav Petkov <bp@alien8.de> wrote:
>
> > So if this second syscall doesn't sound really great, I'd say we stick
> > to the #NM-based allocation and keep this one in the bag for now and
> > take it out only if it turns out that it makes sense as a use case.
>
> I agree. Simple to add if later, if something requires it --
> though given it's modest incremental value, currently hard to justify.
>
> > As tglx said: it is easy to add stuff later. It is a lot harder - even
> > impossible - to remove already present machinery.

Also, in case you haven’t been watching the other thread, this whole thing needs to wait until the existing code gets cleaned up. The current signal code is a disaster.

>
> Indeed.
>
> thanks!
> Len Brown, Intel Open Source Technology Center
>