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

[PATCH MULTISERIES] Optimize Xen barriers


  • To: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
  • From: Tu Dinh <ngoc-tu.dinh@xxxxxxxxxx>
  • Date: Mon, 18 May 2026 12:24:24 +0200
  • Authentication-results: eu.smtp.expurgate.cloud; dkim=pass header.s=selector1 header.d=vates.tech header.i="@vates.tech" header.h="From:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type:Feedback-ID"
  • Cc: Tu Dinh <ngoc-tu.dinh@xxxxxxxxxx>
  • Delivery-date: Mon, 18 May 2026 10:24:37 +0000
  • Feedback-id: default:8631fc262581453bbf619ec5b2062170:Sweego
  • List-id: Developer list for the Windows PV Drivers subproject <win-pv-devel.lists.xenproject.org>

This series aims to optimize the use of memory barriers in all Windows
PV drivers.

Particularly, the following have been changed:
* x86 is TSO and only needs a compiler barrier as read/write barriers.
  So the xen_* barriers in xen-types.h don't always need to be
  KeMemoryBarrier (which is a full barrier using a locked instruction).
* Barriers right next to Interlocked* operations were deleted, as these
  operations serve as implicit full barriers.
* Ring operations were converted acquire-release semantics instead of
  full barriers.
* As a related change, LockThread tracking was conditioned to debug
  builds.


--
Ngoc Tu Dinh | Vates XCP-ng Developer

XCP-ng & Xen Orchestra - Vates solutions

web: https://vates.tech

 


Rackspace

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