[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <BYAPR11MB2632E0BCC9CE86D7DB6E7CFEFFBC9@BYAPR11MB2632.namprd11.prod.outlook.com>
Date: Tue, 26 Jan 2021 02:12:45 +0000
From: "Zhang, Qiang" <Qiang.Zhang@...driver.com>
To: "peterz@...radead.org" <peterz@...radead.org>,
"tglx@...utronix.de" <tglx@...utronix.de>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Question on migrate_disabe/enable()
Hello Peterz, tglx
I have some questions about migrate_disabe/enable(), in the past migrate_disabe/enable() is replaced by preempt_disable/enable() in no RT system.
And now migrate_disabe/enable() has its own implementation, I want to know in migrate_disabe/enable() critical area is blocking allowed?
If allowed, There's a blockage in migrate_disabe/enable() critical area, and this time if CPU going offline,offline time will be longer. Is this normal phenomenon?
Thanks
Qiang
Powered by blists - more mailing lists