Hi Chris, Thanks! I have applied this fixing patch (yesterday before you merged) and tried in our platform. Didn't found this issue by now. This fix works. Best Regards GangWu
-----Original Message----- From: Chris Redpath [mailto:Chris.Redpath@arm.com] Sent: 2019年2月26日 18:58 To: Wu Gang(吴刚); eas-dev@lists.linaro.org; ke.wang@spreadtrum.com Subject: Re: [Eas-dev] one stall issue in migration_cpu_stop? Thanks!
Hi GangWu,
On 26/02/2019 02:43, Wu Gang(吴刚) wrote:
Hi Chris, Thanks for your information. It is very helpful. I will try the "in review" fixing patch mentioned. BTW, I think we should meet a lot of WALT warning/bug issues if revert commit bfc525947c5686d on the other hand.
The fix from Ke Wang is now merged - what it does is replace an unconditional unlock of the original rq with a double_rq_unlock call which is able to cope in the case where both rq pointers are the same. This means that the rqs should now be locked every time we call walt_fixup_busy_time.
Please let me know if this does not solve your issue!
Best Regards,
Chris
Thanks GangWu
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.