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

Re: [RFC PATCH 01/10] sched: core: save IRQ state during locking


  • To: Volodymyr Babchuk <Volodymyr_Babchuk@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  • Date: Wed, 24 Feb 2021 18:29:30 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=4D45fhMbVNY7HwSrUfby8l6DNxZ+oy/vDwl1OVkHISI=; b=btNKMKJrY+ReLjsT7jakWGpuroeL/gYyM4wtk7oliqX1ciXho/fhPvRbYq/pC8kwGgMzGNn79MSBC0f2R8Ynl4E4zaeherrOe9mpItk8c4nBJapzbiv3HL0LeBUqB+hd+oSmMpNpuCpPFSlXC7t2ljWDJVl35NptYW52X5KNmEaZVZfSx9rsSe+40gTYPLRBAwW9yGOTJRREwf+aUgkktzvN7PEjWmX81xlDSQ6CLJ19naXTBQLipMGAyI8Sabb7cabzzpigzjr8+U+hayKfpv5tX95u8OEyi+7fgWBpq1AQbJXrPKeAr8UPxcL8o2wgJCKgVpsCcbgBYDhTMvcLvg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=h2ZqP/kOYZoZ2W92GiDICCHF+A/EtXaV338lIUgAGkRn+meC4u7zbVRh7XNgd9cK0zPHmtLgntPV8m8Z6/l1dSFgxGf6dHowfHwGLNrzDquSaBbEy9xQHAvwaBmFwF/BnE0XB5Ia0t2fJJ32CKKNIMpXa69CGNwWhKM2vwDGVI09ATgWC75Nj8KKGdF6ogaIy5L3wxADuZbrQ9MLHhT5q0jB9wuOrZTBE4ptFMSzHiev3zKDVzA+C9r0VHCcVncJBgvsREokhgVClKqDWEd9IVFk3Ax/Pyif2SPTBVSp/zC78Qa5mAOfs6FSCcys14bf/OWCrfDEx1zR9th02xSmYg==
  • Authentication-results: esa3.hc3370-68.iphmx.com; dkim=pass (signature verified) header.i=@citrix.onmicrosoft.com
  • Cc: George Dunlap <george.dunlap@xxxxxxxxxx>, Dario Faggioli <dfaggioli@xxxxxxxx>
  • Delivery-date: Wed, 24 Feb 2021 18:29:46 +0000
  • Ironport-sdr: U5ruABiQsx1p2QeAfF9JDHhx+JzXj1pXIKcgQuAaIGXEx/1AxJ0SI+/2ZPFG33KCAHgk1XimIT Vj+P4Qe/RKZU+bs7JOKJHtL3hpVVX6YrCdndjn7PVrNV9+BpDJNWunBmez7vfLwQbGsmiAPxeZ N8BD5AN7QZeIREhvVtkqacGoPG1wdV8ER2YdI+rCVHwKmyLwLXYZKpmsHHVfWsAQSxuXre9kI6 SobAxsc5b4PpsBUOA9nLf+xxSjPu4x3Z5echvvFGJsP/5sATWy8juqnd5FKbx4R6ckqaXwLMo0 Vr0=
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 23/02/2021 02:34, Volodymyr Babchuk wrote:
> With XEN preemption enabled, scheduler functions can be called with
> IRQs disabled (for example, at end of IRQ handler), so we should
> save and restore IRQ state in schedulers code.
>
> Signed-off-by: Volodymyr Babchuk <volodymyr_babchuk@xxxxxxxx>

These functions need to fixed not to be _irq() variants in the first place.

The only reason they're like that is so the schedule softirq/irq can
edit the runqueues.  I seem to recall Dario having a plan to switch the
runqueues to using a lockless update mechanism, which IIRC removes any
need for any of the scheduler locks to be irqs-off.

~Andrew



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.