Re: VK_EXT_aquire_xlib_display and kernel security concerns

On 10/16/2017 05:49 PM, Keith Packard wrote: Andy Ritger writes: If the NVIDIA X driver finds an HMD display, it: (a) Marks it as disconnected. (b) Does not make its EDID available to RandR clients. So, unless I'm mistaken, RandR clients will see the HMD as an RandR

Re: VK_EXT_aquire_xlib_display and kernel security concerns

On 10/16/2017 01:33 PM, Dave Airlie wrote: On 17 October 2017 at 06:01, James Jones <jajo...@nvidia.com> wrote: On 10/16/2017 12:28 PM, Keith Packard wrote: James Jones <jajo...@nvidia.com> writes: I think at a lower level, we have different

Re: VK_EXT_aquire_xlib_display and kernel security concerns

On 10/16/2017 12:28 PM, Keith Packard wrote: James Jones <jajo...@nvidia.com> writes: I think at a lower level, we have different views of how vkGetPhysicalDeviceDisplayPropertiesKHR/VK_KHR_display works. vkGetPhysicalDeviceDisplayPropertiesKHR() is suppose to enumerate all the di

Re: VK_EXT_aquire_xlib_display and kernel security concerns

On 10/14/2017 02:00 AM, "Keith Packard" wrote: I've implemented this extension in DRM and have run into a conflict between the spec and the Linux architecture. The VkDisplayKHR parameter for VK_EXT_acquire_xlib_display can be found in two different ways: 1) Enumerate displays using

Re: [PATCH 0/5] GLX updates

For the series, Reviewed-by: James Jones jajo...@nvidia.com Thanks, -James On 06/02/2015 10:41 AM, Adam Jackson wrote: This series stubs in the server side of support for some newer GLX extensions. They won't do much without corresponding Mesa updates, but are necessary for such updates

Re: [PATCH] Add -iglx +iglx to Xserver.man

On 11/25/2014 11:37 PM, Robert Morell wrote: On Tue, Nov 25, 2014 at 11:20:58PM -0800, Alan Coopersmith wrote: On 11/25/14 10:36 PM, Robert Morell wrote: On Tue, Nov 25, 2014 at 07:26:14PM -0800, Alan Coopersmith wrote: Covers the current state after commits 99f0365b1fbdfd9238b9f,

Re: [PATCH v2] Add -iglx +iglx to Xserver.man

. +.TP 8 .B \-maxbigreqsize \fIsize\fP sets the maximum big request to .I size Reviewed-by: James Jones jajo...@nvidia.com ___ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman

Present proto feedback

Hi Keith, Thanks for incorporating all the suggested fencing in the present protocol. I think the latest version looks good, and just had some minor feedback: -I just noticed the email you listed for me in the Acknowledgements was incorrect. It should be jajones 'at' nvidia.com. -Should

Re: Present extension name alternatives

On 08/13/2013 02:25 PM, Bryce W. Harrington wrote: On Tue, Aug 13, 2013 at 02:02:59PM -0700, Alan Coopersmith wrote: On 08/13/13 01:09 PM, Keith Packard wrote: Present is a noun and a verb (with different pronunciations, no less). As such, it makes a pretty miserable extension name. Can you

Re: Current DRI3 specification

On 06/08/2013 11:18 AM, Daniel Stone wrote: Hi, On 7 June 2013 13:30, James Jones jajo...@nvidia.com wrote: We do need more than the 'make it pretty' requirement above though. What you describe is what interactive rendering apps want, when you're translating some sort of input into graphics

Re: Current DRI3 specification

On 06/07/2013 10:10 AM, Keith Packard wrote: * PGP Signed by an unknown key James Jones jajo...@nvidia.com writes: Yeah, I think the semantics are compatible. We allocate these buffers on the server-side, but I don't think that affects the interaction with Present. DRI2 allocates them

Re: Current DRI3 specification

On 06/05/2013 06:20 PM, Keith Packard wrote: * PGP Signed by an unknown key James Jones jajo...@nvidia.com writes: I read through this and the extension specification below. The DRI3 stuff doesn't directly affect our driver at the moment of course, but I like the direction it's going

Re: Current DRI3 specification

Airlie airl...@redhat.com Kristian Høgsberg k...@bitplanet.net James Jones jano...@nvidia.com ❄ ❄ ❄ ❄ ❄ ❄ ❄ 2. Data Types DRI3EVENTID { XID } Defines a unique event delivery target for DRI3 events. Multiple event IDs can be allocated to provide

Re: Initial DRI3000 protocol specs available

On 03/21/2013 03:41 PM, Keith Packard wrote: * PGP Signed by an unknown key James Jones jajo...@nvidia.com writes: If you associate an X Fence Sync with your swap operation, the driver has the option to trigger it directly from the client command stream and wake up only the applications

Re: Initial DRI3000 protocol specs available

On 03/07/2013 05:17 PM, Keith Packard wrote: * PGP Signed by an unknown key James Jones jajo...@nvidia.com writes: There didn't seem to be much interest outside of NVIDIA, so besides fence sync, the ideas are tabled internally ATM. This shouldn't surprise you though -- no-one else needs

Re: Initial DRI3000 protocol specs available

On 03/07/2013 12:49 PM, Keith Packard wrote: * PGP Signed by an unknown key Aaron Plattner aplatt...@nvidia.com writes: If I'm understanding this correctly, this requires the X server to receive a notification from the GPU that the swap is complete so it can send the SwapComplete event. Is

Re: Initial DRI3000 protocol specs available

On 03/07/2013 01:19 PM, Owen Taylor wrote: On Thu, 2013-02-28 at 16:55 -0800, Keith Packard wrote: * It would be great if we could figure out a plan to get to the point where the exact same application code is going to work for proprietary and open source drivers. When you get down to

Re: [PATCH v2 9/9] Xext: Add per-device SyncCounters

On 3/20/12 12:04 AM, Peter Hutterer wrote: On Fri, Mar 16, 2012 at 06:15:30PM -0700, James Jones wrote: Below: +SyncCounter* +SyncInitDeviceIdleTime(DeviceIntPtr dev) +{ +char timer_name[64]; +sprintf(timer_name, DEVICEIDLETIME %d, dev-id); + +return init_system_idle_counter

Re: [PATCH v2 9/9] Xext: Add per-device SyncCounters

Below: On 3/14/12 9:10 PM, Peter Hutterer wrote: Previously, we only had one idle alarm that was triggered for all devices, whenever the user used any device, came back from suspend, etc. Add system SyncCounters for each device (named DEVICEIDLETIME x, with x being the device id) that

Re: [PATCH 0/9] per-device idle counters

On 3/14/12 5:20 PM, Peter Hutterer wrote: On Wed, Mar 14, 2012 at 05:11:04PM -0700, James Jones wrote: I like the cleanups here. I prefer the SysCounterGetPrivate() helper over the macro, but don't particularly think the need to allow SyncNumSystemCounters to go negative by decrementing

Re: [PATCH 0/9] per-device idle counters

I like the cleanups here. I prefer the SysCounterGetPrivate() helper over the macro, but don't particularly think the need to allow SyncNumSystemCounters to go negative by decrementing in ResetProc() is a win for clarity. Thanks, -James On 3/14/12 4:30 PM, Peter Hutterer wrote: On Wed, Mar

Re: [PATCH] Don't free font closures prematurely (#31501)

to send it to xorg-devel ... I have not tested it and am just forwarding it along for comment since it reportedly addresses this crasher. From 59616dde4a04d407db76d55b06bcc82d646f42cd Mon Sep 17 00:00:00 2001 From: James Jones jajo...@nvidia.com Date: Thu, 9 Dec 2010 16:14:05 -0800 Subject: [PATCH

Re: Are we ready to tag release libXext 1.3.0?

everything finished up for integrating the client side of Sync 3.1 to our packages to go along with the Xorg 1.10 integration.) -Alan Coopersmith-alan.coopersm...@oracle.com Oracle Solaris Platform Engineering: X Window System On 05/ 5/11 08:09 PM, James Jones wrote: I'm

Re: Are we ready to tag release libXext 1.3.0?

I'm not aware of any fence sync issues that would hold up a release. Everything should be ready to go. Thanks, -James nvpublic On 5/5/11 7:09 PM, Alan Coopersmith alan.coopersm...@oracle.com wrote: It looks like we've still not done a release of libXext with the new XSyncAwaitFence() API

Re: RandR 1.4 restart

On Friday 04 March 2011 11:43:05 pm Keith Packard wrote: * PGP Signed by an unknown key On Fri, 4 Mar 2011 16:47:45 -0800, James Jones jajo...@nvidia.com wrote: On 3/1/11 6:56 PM, James Jones jajo...@nvidia.com wrote: On Tuesday 01 March 2011 08:02:24 Keith Packard wrote: *snip

Re: RandR 1.4 restart

On Thursday 03 March 2011 4:14:04 pm Soeren Sandmann wrote: James Jones jajo...@nvidia.com writes: With a scheme like this, the Composite extension itself would become simply a way to support legacy applications since window redirection doesn't really mean anything for InputOnly windows

Re: RandR 1.4 restart

On 3/1/11 6:56 PM, James Jones jajo...@nvidia.com wrote: On Tuesday 01 March 2011 08:02:24 Keith Packard wrote: *snip* Scanout pixmaps get resized automatically when the associated crtc gets a new mode. This lets a compositing manager deal with the scanout pixmap creation while separate

Re: RandR 1.4 restart

On Tuesday 01 March 2011 14:48:44 Soeren Sandmann wrote: Keith Packard kei...@keithp.com writes: On Tue, 01 Mar 2011 20:12:14 +0100, Soeren Sandmann sandm...@cs.au.dk wrote: Presumably the main use case for this is fullscreen video. When using a compositing manager, any full-screen

Re: RandR 1.4 restart

On Tuesday 01 March 2011 11:12:14 Soeren Sandmann wrote: Ville Syrjälä ville.syrj...@nokia.com writes: On Mon, Feb 28, 2011 at 05:29:56PM -0800, ext Keith Packard wrote: Ok, let's try to get a bit of protocol review, then look at the library API, then the server internal APIs and finally

Re: RandR 1.4 restart

On Tuesday 01 March 2011 18:35:14 Keith Packard wrote: * PGP Signed by an unknown key On Tue, 1 Mar 2011 18:11:24 -0800, James Jones jajo...@nvidia.com wrote: Also, getting the unredirect/redirect to work without causing a bunch of expose events and related flickering is hard. It's

Re: RandR 1.4 restart

On Tuesday 01 March 2011 08:02:24 Keith Packard wrote: *snip* Scanout pixmaps get resized automatically when the associated crtc gets a new mode. This lets a compositing manager deal with the scanout pixmap creation while separate screen configuration applications deal with mode setting. Of

[PATCH xserver (v2)] X Sync Cleanups

. -Return BadFence, not BadCounter from XSyncAwaitFence() Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Keith Packard kei...@keithp.com --- Xext/sync.c | 138 ++ 1 files changed, 81 insertions(+), 57 deletions(-) diff --git

[PATCH xserver (v3)] X Sync Cleanups

. -Return BadFence, not BadCounter from XSyncAwaitFence() Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Keith Packard kei...@keithp.com --- Xext/sync.c | 142 +++--- 1 files changed, 86 insertions(+), 56 deletions(-) diff --git

Re: [PATCH 2/2] mi: Sync: Don't free managed screen private

) SyncScreenPrivPtr pScreenPriv = SYNC_SCREEN_PRIV(pScreen); pScreen-CloseScreen = pScreenPriv-CloseScreen; -free(pScreenPriv); return (*pScreen-CloseScreen) (i, pScreen); } -- 1.7.2.3 Reviewed-by: James Jones jajo...@nvidia.com Thanks, -James

[PATCH xextproto] Document another error for XSyncAwaitFence

XSyncAwaitFence can generate BadValue if the fence list argument is empty. Document this in the spec. --- specs/sync.xml |5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/specs/sync.xml b/specs/sync.xml index 44a6b2c..aaad323 100644 --- a/specs/sync.xml +++

[PATCH xserver] X Sync Cleanups

() to kill an incompatible pointer type warning. -Remove comments claiming protocol updates are needed. One wasn't true and the other was addressed with a xextproto change. -Return BadFence, not BadCounter from XSyncAwaitFence() Signed-off-by: James Jones jajo...@nvidia.com --- Xext/sync.c

[PATCH xextproto] Document another error for XSyncAwaitFence (Resend)

Resend includes sign-off. XSyncAwaitFence can generate BadValue if the fence list argument is empty. Document this in the spec. Signed-off-by: James Jones jajo...@nvidia.com --- specs/sync.xml |5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/specs/sync.xml b/specs

[PATCH xserver (v4) 05/10] Move some sync code to miext

As a precursor to the fence sync object video driver and extension API, move some code from Xext to miext/sync. Most of this is just code to set up the build system to include the new directory. No functional code is added in this change. Signed-off-by: James Jones jajo...@nvidia.com

[PATCH xserver (v4) 02/10] Create SyncObject base type.

SyncObject is now the base type for SyncCounter. Data to be used by all sync types is stored in the base object. SyncCounter can be safely cast to SyncObject, and a SyncObject can be cast to the correct type based on SyncObject::type. Signed-off-by: James Jones jajo...@nvidia.com --- Xext

[PATCH xserver (v4) 04/10] Factor out generic code from ProcSyncAwait()

In preparation for adding more sync object types that will need Await requests of their own, factor out some setup and finalization code from ProcSyncAwait() into SyncAwaitPrologue() and SyncAwaitEpilogue() Signed-off-by: James Jones jajo...@nvidia.com --- Xext/sync.c | 110

[PATCH xserver (v4) 07/10] Require xextproto 7.1.99

Subsequent changes rely on fence sync protocol in the sync extension. This protocol is only complete in xextproto version 7.1.99 and above. Signed-off-by: James Jones jajo...@nvidia.com --- configure.ac |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/configure.ac b

[PATCH xserver (v4) 10/10] Expose Sync Fence Object protocol

Add the new protocol handlers for XSync 3.1 to the dispatch tables and report support for Sync protocol version 3.1. Signed-off-by: James Jones jajo...@nvidia.com --- Xext/sync.c | 24 include/protocol-versions.h |2 +- 2 files changed, 25

[PATCH xserver (v4) 06/10] Add fence sync driver interface

functions to notify driver when adding/removing triggers to/ from the sync object. Signed-off-by: James Jones jajo...@nvidia.com --- Xext/sync.c |6 +- dix/privates.c |1 + hw/xfree86/loader/sdksyms.sh |3 + include/privates.h |1 + miext/sync

[PATCH xserver (v4) 09/10] Add XSyncAwaitFence() handler

-Add the actual ProcSyncAwaitFence() dispatch func -Add support for fence sync triggers. Signed-off-by: James Jones jajo...@nvidia.com --- Xext/sync.c| 183 ++-- Xext/syncsrv.h |1 - 2 files changed, 152 insertions(+), 32 deletions

[PATCH xserver (v4) 08/10] Create/Destroy/Trigger/Reset/Query Fence Sync objs

operation. However, it is also desireable to associate a screen with fence sync objects at creation time so that the associated screen's driver can allocate any HW- specific resources needed by the fence object up front. Signed-off-by: James Jones jajo...@nvidia.com --- Xext/Makefile.am

[PATCH xserver (v4) 00/10] X Server support for Fence Sync

the damage 1.2 support for DamageSubtractAndTrigger. Re- uses X Sync Counter code wherever possible. A driver interface has also been added so DDX drivers can redirect fence sync operations to HW rendering backend operations. James Jones (10): Add and use SERVER_SYNC_*_VERSION Create SyncObject base

[PATCH xserver (v4) 01/10] Add and use SERVER_SYNC_*_VERSION

the server was built against. Signed-off-by: James Jones jajo...@nvidia.com --- Xext/sync.c |5 +++-- include/protocol-versions.h |4 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/Xext/sync.c b/Xext/sync.c index f23df6c..4da06ac 100644 --- a/Xext/sync.c

[PATCH xserver (v3) 04/10] Create SyncObject base type.

SyncObject is now the base type for SyncCounter and SyncFence. Data to be used by both types is stored in the base object. Both SyncCounter and SyncFence can be safely cast to SyncObject, and a SyncObject can be cast to the correct type based on SyncObject::type. Signed-off-by: James Jones jajo

[PATCH xserver (v3) 02/10] Create/Destroy/Trigger/Reset Fence Sync objects

. However, it is also desireable to associate a screen with fence sync objects at creation time so that the associated screen's driver can allocate any HW- specific resources needed by the fence object up front. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt

[PATCH xserver (v3) 01/10] Require xextproto 7.1.99

Subsequent changes rely on fence sync protocol in the sync extension. This protocol is only complete in xextproto version 7.1.99 and above. Signed-off-by: James Jones jajo...@nvidia.com --- configure.ac |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/configure.ac b

[PATCH xserver (v3) 00/10] X Server support for Fence Sync

backend operations. James Jones (10): Require xextproto 7.1.99 Create/Destroy/Trigger/Reset Fence Sync objects Add XSyncQueryFence() Create SyncObject base type. Make Await SyncTrigger functions generic Generalize comment above Sync CheckTriggered funcs Add XSyncAwaitFence() handler

[PATCH xserver (v3) 03/10] Add XSyncQueryFence()

Allows callers to query whether or not a given fence sync object is currently triggered. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com Reviewed-by: Robert Morell rmor...@nvidia.com Reviewed-by: Adam Jackson a...@redhat.com --- Xext/sync.c | 49

[PATCH xserver (v3) 05/10] Make Await SyncTrigger functions generic

Update all the functions dealing with Await sync triggers handle generic sync objects instead of just counters. This will facilitate code sharing between the counter sync waits and the fence sync waits. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt

[PATCH xserver (v3) 06/10] Generalize comment above Sync CheckTriggered funcs

The comment referred only to counter sync objects and did not include the new fence sync CheckTriggered function. Generalize the language so it applies to all the CheckTriggered functions. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com Reviewed

[PATCH xserver (v3) 10/10] Export SyncVerifyFence() in new SDK header

Add syncsdk.h, a new xorg SDK header. It contains SyncVerifyFence() and the helper functions that use it to look up fence sync objects. Exporting this functionality in an SDK header allows 3rd party extensions to look up fence objects in their interop APIs. Signed-off-by: James Jones jajo

[PATCH xserver (v3) 09/10] Add fence sync driver interface

to notify driver when adding/removing triggers to/ from the sync object. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com Reviewed-by: Robert Morell rmor...@nvidia.com Reviewed-by: Adam Jackson a...@redhat.com --- Xext/sync.c | 38

[PATCH xserver (v3) 07/10] Add XSyncAwaitFence() handler

in the previous refactoring changes. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com Reviewed-by: Robert Morell rmor...@nvidia.com Reviewed-by: Adam Jackson a...@redhat.com --- Xext/sync.c | 300

[PATCH xserver (v3) 08/10] Move some sync code to miext

As a precursor to exposing fence sync objects to video drivers and other extensions, move some operations from Xext to miext/sync. Expose macros for looking up sync objects out- side of Xext/sync.c as well. Signed-off-by: James Jones jajo...@nvidia.com --- COPYING|2 +- Xext

[PATCH xserver] Bump extension ABI to 5

Commit 606e079cc4d9a9db3197652ca51683c36f74efb8 moved the visual field in WindowOptRec, breaking the extension module ABI. Signed-off-by: James Jones jajo...@nvidia.com --- hw/xfree86/common/xf86Module.h |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/hw/xfree86/common

[PATCH xextproto (rev4) 0/5] XSync Fence Objects

can wait for fence sync objcts to reach the triggered state using XSync APIs or using interop functionality in other APIs. This allows for efficient cross-API synchronization with X rendering operations. James Jones (5): Document changes in XSync version 3.1 Initial Fence Sync support Add

[PATCH xextproto (rev4) 5/5] Bump version to 7.1.99.0

Use version 7.1.99.0 to mark the inclusion of Fence Sync protocol support. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com --- configure.ac |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/configure.ac b/configure.ac index

[PATCH xextproto (rev4) 1/5] Document changes in XSync version 3.1

Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Pierre-Loup Griffais pgriff...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com Reviewed-by: Robert Morell rmor...@nvidia.com --- specs/sync.xml | 229 +-- 1 files changed

[PATCH xextproto (rev4) 4/5] Add protocol for XSyncAwaitFence()

Add the fence sync object equivalent of XSyncAwait() Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com --- syncproto.h | 12 1 files changed, 12 insertions(+), 0 deletions(-) diff --git a/syncproto.h b/syncproto.h index 7e0a568

[PATCH xextproto (rev4) 3/5] Add XSyncQueryFence()

Allows callers to query whether a given fence sync object is currently triggered or not. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com --- syncproto.h | 28 1 files changed, 28 insertions(+), 0 deletions(-) diff

[PATCH xextproto (rev4) 2/5] Initial Fence Sync support

Defines the protocol for creation and basic management of binary state sync objects. The following operations are defined: -Creation -Destruction -Trigger -Reset Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com --- syncconst.h |6

[PATCH damageproto (rev3) 1/3] Document changes in damage proto version 1.2

Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Pierre-Loup Griffais pgriff...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com Reviewed-by: Robert Morell rmor...@nvidia.com --- damageproto.txt | 57 +- 1 files changed

[PATCH damageproto (rev3) 2/3] Add XDamageSubtractAndTrigger operation

XDamageSubtractAndTrigger behaves exactly like XDamageSubtract except it receives an optional fence sync object. If the value of this object is not None, it is triggered by X once all the rendering associated with the damage regions being subtracted has completed. Signed-off-by: James Jones jajo

[PATCH damageproto (rev3) 3/3] Bump version to 1.2.99.0

Use version 1.2.99.0 to mark the inclusion of Fence Sync protocol support. Really this should be 1.2.0, but that version was already incorrectly used. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com --- configure.ac |2 +- 1 files changed, 1

[PATCH damageproto (rev3) 0/3] Add XDamageSubtractAndTrigger

. James Jones (3): Document changes in damage proto version 1.2 Add XDamageSubtractAndTrigger operation Bump version to 1.2.99.0 configure.ac|2 +- damageproto.h | 15 ++ damageproto.txt | 57 +- damagewire.h

[PATCH libXext (rev3) 1/5] Backwards compat for newer XSync + older servers

extension. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com --- src/XSync.c | 125 +- 1 files changed, 97 insertions(+), 28 deletions(-) diff --git a/src/XSync.c b/src/XSync.c index c21749a

[PATCH libXext (rev3) 0/5] XSync Fence Objects, lib portion

Changes since last version: -Rebased at d35e95fdf433a249d0293744d3e1ef6196422700 -Added xextproto version check. Adds client library support for binary sync objects added in the X Synchronization protocol version 3.1. libXext remains compatible with servers that only implement version 3.0 James

[PATCH libXext (rev3) 2/5] Require xextproto = 7.1.99

Subsequent changes require fence sync protocol support in the XSync extension, which is only compete in version xextproto 7.1.99 and above. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com --- configure.ac |4 ++-- 1 files changed, 2 insertions

[PATCH libXext (rev3) 5/5] Add XSyncAwaitFence()

Add the XSynceFence version of XSyncAwait(). Waits for fence objects to reach the triggered state. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com --- include/X11/extensions/sync.h |6 ++ src/XSync.c | 21

[PATCH libXext (rev3) 3/5] Initial Fence Sync Object support

XSyncCreateFence() takes a drawable to identify which screen to create the fence on. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com --- include/X11/extensions/sync.h | 21 ++ src/XSync.c | 85

[PATCH libXext (rev3) 4/5] Add XSyncQueryFence()

Allows callers to query whether or not a given fence sync object is currently triggered. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com --- include/X11/extensions/sync.h |6 ++ src/XSync.c | 29

[PATCH libXdamage (rev2)] Add XDamageSubtractAndTrigger operation

with the damage regions being subtracted has completed. Bump version number to match protocol version, and require damageproto 1.2.99 Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com --- configure.ac |4 ++-- include/X11

[PATCH damageproto (rev4) 0/3] Add XDamageSubtractAndTrigger

Changes since the last version: -Changed new version from 1.2.99 - 1.3.0 Adds the XDamageSubtractAndTrigger() request and bumps the damage protocol to version 1.2. Now with protocol spec updates including overview, justification, and intended usage of the new reqeust. James Jones (3

[PATCH damageproto (rev4) 3/3] Bump version to 1.3.0

Use version 1.3.0 to mark the inclusion of Fence Sync protocol support. Really this should be 1.2.0, but that version was already incorrectly used. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com --- configure.ac |2 +- 1 files changed, 1

[PATCH damageproto (rev4) 2/3] Add XDamageSubtractAndTrigger operation

XDamageSubtractAndTrigger behaves exactly like XDamageSubtract except it receives an optional fence sync object. If the value of this object is not None, it is triggered by X once all the rendering associated with the damage regions being subtracted has completed. Signed-off-by: James Jones jajo

[PATCH damageproto (rev4) 1/3] Document changes in damage proto version 1.2

Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Pierre-Loup Griffais pgriff...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com Reviewed-by: Robert Morell rmor...@nvidia.com --- damageproto.txt | 57 +- 1 files changed

[PATCH xserver (rev2) 5/9] Generalize comment above Sync CheckTriggered funcs

The comment referred only to counter sync objects and did not include the new fence sync CheckTriggered function. Generalize the language so it applies to all the CheckTriggered functions. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com Reviewed

[PATCH xserver (rev2) 3/9] Create SyncObject base type.

SyncObject is now the base type for SyncCounter and SyncFence. Data to be used by both types is stored in the base object. Both SyncCounter and SyncFence can be safely cast to SyncObject, and a SyncObject can be cast to the correct type based on SyncObject::type. Signed-off-by: James Jones jajo

[PATCH xserver (rev2) 2/9] Add XSyncQueryFence()

Allows callers to query whether or not a given fence sync object is currently triggered. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com Reviewed-by: Robert Morell rmor...@nvidia.com --- Xext/sync.c | 49

[PATCH xserver (rev2) 8/9] Add fence sync driver interface

to notify driver when adding/removing triggers to/ from the sync object. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com Reviewed-by: Robert Morell rmor...@nvidia.com --- Xext/sync.c | 38 +++ dix/privates.c |1

[PATCH xserver (rev2) 6/9] Add XSyncAwaitFence() handler

in the previous refactoring changes. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com Reviewed-by: Robert Morell rmor...@nvidia.com --- Xext/sync.c | 300 +++ 1 files changed, 219 insertions(+), 81

[PATCH xserver (rev2) 4/9] Make Await SyncTrigger functions generic

Update all the functions dealing with Await sync triggers handle generic sync objects instead of just counters. This will facilitate code sharing between the counter sync waits and the fence sync waits. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt

[PATCH xserver (rev2) 9/9] Export SyncVerifyFence() in new SDK header

Add syncsdk.h, a new xorg SDK header. It contains SyncVerifyFence() and the helper functions that use it to look up fence sync objects. Exporting this functionality in an SDK header allows 3rd party extensions to look up fence objects in their interop APIs. Signed-off-by: James Jones jajo

[PATCH xserver (rev2) 7/9] Add XDamageSubtractAndTrigger operation

XDamageSubtractAndTrigger behaves exactly like XDamageSubtract except it receives an optional fence sync object. If the value of this object is not None, it is triggered by X once all the rendering associated with the damage regions being subtracted has completed. Signed-off-by: James Jones jajo

[PATCH xextproto 0/4] XSync Fence Objects (rev. 3)

is currently written such that it will refuse to work with any server advertising an XSync version below whatever the lib code picks up from compile-time constants in xextproto. James Jones (4): Document changes in XSync version 3.1 Initial Fence Sync support Add XSyncQueryFence() Add protocol

[PATCH xextproto 1/4] Document changes in XSync version 3.1

Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Pierre-Loup Griffais pgriff...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com Reviewed-by: Robert Morell rmor...@nvidia.com --- specs/sync.xml | 229 +-- 1 files changed

[PATCH xextproto 2/4] Initial Fence Sync support

Defines the protocol for creation and basic management of binary state sync objects. The following operations are defined: -Creation -Destruction -Trigger -Reset Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com --- syncconst.h |6

[PATCH xextproto 3/4] Add XSyncQueryFence()

Allows callers to query whether a given fence sync object is currently triggered or not. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com --- syncproto.h | 28 1 files changed, 28 insertions(+), 0 deletions(-) diff

[PATCH xextproto 4/4] Add protocol for XSyncAwaitFence()

Add the fence sync object equivalent of XSyncAwait() Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com --- syncproto.h | 12 1 files changed, 12 insertions(+), 0 deletions(-) diff --git a/syncproto.h b/syncproto.h index 7e0a568

[PATCH libXext] Backwards compat for newer XSync + older servers

extension. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com --- src/XSync.c | 125 +- 1 files changed, 97 insertions(+), 28 deletions(-) diff --git a/src/XSync.c b/src/XSync.c index 648c718

[PATCH libXext 0/3] XSync Fence Objects, lib portion

Adds client library support for binary sync objects added in the X Synchronization protocol version 3.1. libXext remains compatible with servers that only implement version 3.0 James Jones (3): Initial Fence Sync Object support Add XSyncQueryFence() Add XSyncAwaitFence() include/X11

[PATCH libXext 1/3] Initial Fence Sync Object support

XSyncCreateFence() takes a drawable to identify which screen to create the fence on. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com --- include/X11/extensions/sync.h | 21 ++ src/XSync.c | 85

[PATCH libXext 2/3] Add XSyncQueryFence()

Allows callers to query whether or not a given fence sync object is currently triggered. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com --- include/X11/extensions/sync.h |6 ++ src/XSync.c | 29

[PATCH libXext 3/3] Add XSyncAwaitFence()

Add the XSynceFence version of XSyncAwait(). Waits for fence objects to reach the triggered state. Signed-off-by: James Jones jajo...@nvidia.com Reviewed-by: Aaron Plattner aplatt...@nvidia.com --- include/X11/extensions/sync.h |6 ++ src/XSync.c | 21

[PATCH libXdamage] Add XDamageSubtractAndTrigger operation

XDamageSubtractAndTrigger behaves exactly like XDamageSubtract except it receives an optional fence sync object. If the value of this object is not None, it is triggered by X once all the rendering associated with the damage regions being subtracted has completed. Signed-off-by: James Jones jajo

[PATCH xserver 0/9] X Server support for Fence Sync

Implements X Sync Fence Objects in the server, including the damage 1.2 support for DamageSubtractAndTrigger. Re- uses X Sync Counter code wherever possible. A driver interface has also been added so DDX drivers can redirect fence sync operations to HW rendering backend operations. James Jones

  1   2   >