Re: [PATCH 5/5] task_work: use TIF_NOTIFY_SIGNAL if available

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Oct 16 2020 at 07:35, Jens Axboe wrote:
> On 10/16/20 3:39 AM, Thomas Gleixner wrote:
>> On Fri, Oct 16 2020 at 11:00, Thomas Gleixner wrote:
>> That's a truly great suggestion:
>> 
>>    X86 is going to have that TIF bit once the above is available.
>> 
>> I'm happy to help with the merge logistics of this.
>
> Not really following this email...

What I tried to convey is, that the x86 tif bit is not going in before
the complete thing (including cleanups) is available. I'm only half
joking.

> But it seems to me that you're happy with approach 2, so I'll do
> the following:
>
> - Get rid of the CONFIG_GENERIC_ENTRY dependency for TIF_NOTIFY_SIGNAL
> - Respin the arch additions and cleanups on top of that again
>
> And hopefully we'll have something mergeable at that point. Once we
> have this series merged somewhere (would be great if you could carry
> it), I'll be talking to arch folks on the rest. Once archs have taken
> the necessary bits, I'll be posting the third and final series which
> is the cleanups that are currently sitting on top of the arch support.

Can you please just post the full thing after resolving #1 of the list
items which I pointed out in the other reply?

With moving the handling into get_signal() you don't need more changes
to arch/* than adding the TIF bit, right? So there should not be much
talking involved other than agreeing on the bit number to use.

I might be missing something though.

Thanks,

        tglx





[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux