On 03/29/2018 12:11 PM, Christian Borntraeger wrote:
>
>
> On 03/29/2018 11:52 AM, Ming Lei wrote:
>> From the debugfs log, hctx0 is mapped to lots of CPU, so it shouldn't be
>> unmapped, could you check if it is hctx0 which is unmapped when the
>> warning is triggered? If not, what is the unmapped hctx? And you can do
>> that by adding one extra line:
>>
>> printk("unmapped hctx %d", hctx->queue_num);
>
> Where do you want that printk?
And do you want it with or without the other patch that you have just sent?
