On 20 May 2016 at 08:36, Alex Goins wrote:
> Hi Dave,
>
> Any update on this? Anything I can do to help?
Hey,
can you take a look at
prime: clean up slave bo properly. (v3)
I think with this rebased onto that, we should be pretty much good to merge.
Dave.
Friendly ping, as it would be very nice to see this merged!
On Fri, May 13, 2016 at 7:36 PM, Alexandre Courbot wrote:
> On 05/13/2016 01:04 AM, Adam Jackson wrote:
>>
>> On Thu, 2016-05-12 at 16:04 +0900, Alexandre Courbot wrote:
>>>
>>> There is currently no reliable way to
In prime configurations master's last set time may not be latest
and greatest, adjust it with slaves last set time, pick up greatest
one. Otherwise xserver may end with events which has
lastSetTime < lastConfigTime even if that's not
the case and confuse xrandr client.
Signed-off-by: Nikhil
On 05/27/2016 01:40 AM, Hans de Goede wrote:
Hi,
On 26-05-16 18:20, Nikhil Mahale wrote:
In prime configurations master's last set time may not be latest
and greatest, adjust it with slaves last set time, pick up greatest
one. Otherwise xserver may end with events which has
lastSetTime <
Replace use of select(2) to avoid fd limits
Signed-off-by: Keith Packard
---
os/inputthread.c | 85
1 file changed, 48 insertions(+), 37 deletions(-)
diff --git a/os/inputthread.c b/os/inputthread.c
index
This provides a wrapper around poll, epoll or WSAPoll providing a
callback-based interface for monitoring activity on a large set of
file descriptors.
Signed-off-by: Keith Packard
---
configure.ac| 2 +-
include/dix-config.h.in | 9 +
os/Makefile.am |
There's no reason not to offer ridiculous numbers of clients; only a
few static data structures are arrays of this length.
Signed-off-by: Keith Packard
---
include/misc.h | 2 +-
os/utils.c | 6 --
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git
The intermediate grabState, "GrabKickout", was used to trigger
dispatch into going back to WaitForSomething after doing a GrabServer
so that the set of ready clients would be recomputed to match what the
server should be processing. As we only process one client per
WaitForSomething call, we will
Use SetNotifyFd instead, with the hope that someday someone will come
fix this to be more efficient -- right now, the wakeup handler is
doing the event reading, instead of the notify callback.
Signed-off-by: Keith Packard
---
hw/dmx/input/dmxcommon.c | 17 +
With no code depending on the range of file descriptors, checking
for that can be eliminated.
Signed-off-by: Keith Packard
---
os/connection.c | 81 -
os/osdep.h | 43 +-
2 files changed,
Eliminates all of the fd_set mangling in the server main thread
Signed-off-by: Keith Packard
---
dix/dispatch.c | 4 +
include/dixstruct.h | 25
os/WaitFor.c| 157 +++--
os/connection.c | 333
xf86WaitForInput and the xf86 SIGIO handling code.
Signed-off-by: Keith Packard
---
hw/xfree86/common/xf86Events.c | 1 -
hw/xfree86/os-support/shared/posix_tty.c | 33 ++---
hw/xfree86/os-support/shared/sigio.c | 63 +---
Remove code in xf86Wakeup for dealing with other input and switch to
using the new NotifyFd interface.
Signed-off-by: Keith Packard
---
hw/xfree86/common/xf86Events.c | 76 --
1 file changed, 22 insertions(+), 54 deletions(-)
diff
The timeout resolution offered in the AdjustWaitForDelay call is
only milliseconds, so passing around the timeout as a pointer to a
struct timeval is not helpful. Doing everything in milliseconds up to
the point of the select call simplifies the code without affecting
functionality at all.
This converts the dispatch loop into using a list of ready clients
instead of an array. This changes the WaitForSomething API so that it
notifies DIX when a client becomes ready to read, instead of returning
the set of ready clients.
Signed-off-by: Keith Packard
---
This is a cleanup, proposed by Adam Jackson, but wasn't merged with
the original NotifyFD changes.
Signed-off-by: Keith Packard
---
hw/kdrive/linux/linux.c | 64 -
1 file changed, 31 insertions(+), 33 deletions(-)
diff --git
Instead of having scheduling done in two places (one in
WaitForSomething, and the other in SmartScheduleClient), just stick
all of the scheduling in SmartScheduleClient.
Signed-off-by: Keith Packard
---
dix/dispatch.c | 22 --
os/WaitFor.c | 33
With no users of the interface needing the readmask anymore, we can
remove it from the argument passed to these functions.
Signed-off-by: Keith Packard
---
composite/compalloc.c | 4 +--
dix/dixutils.c | 18 --
This new libXfont API eliminates exposing internal X server symbols to
the font library, replacing those with a struct full of the entire API
needed to use that library.
v2: Use libXfont2 instead of libXfont_2
Signed-off-by: Keith Packard
---
Xext/xf86bigfont.c | 4 +-
Ok, I've reworked this patch series to try and have it make some
semblance of sense. There's two scary patches, 18/23 and 19/23;
everything else is pretty self contained.
The first patch flips to the new font API:
[PATCH xserver 01/23] dix: Switch to the libXfont2 API (v2)
Then changes
This removes the last uses of fd_set from the server interfaces
outside of the OS layer itself.
Signed-off-by: Keith Packard
---
Xext/sleepuntil.c | 17 +++--
Xext/sync.c | 12 ++--
dix/dixfonts.c | 7
All uses of these interfaces should instead be using the NotifyFd API
instead.
Signed-off-by: Keith Packard
---
include/os.h| 8
os/WaitFor.c| 4 +---
os/connection.c | 43 ---
3 files changed, 9 insertions(+), 46
Signed-off-by: Keith Packard
---
hw/dmx/input/lnx-ms.c | 19 ++-
hw/dmx/input/lnx-ps2.c | 12 +---
2 files changed, 15 insertions(+), 16 deletions(-)
diff --git a/hw/dmx/input/lnx-ms.c b/hw/dmx/input/lnx-ms.c
index 621f0fe..3d028be 100644
---
There's no reason to close these now that we don't care what file
descriptors we use.
Signed-off-by: Keith Packard
---
os/osinit.c | 11 ---
1 file changed, 11 deletions(-)
diff --git a/os/osinit.c b/os/osinit.c
index 6ec2f11..e269957 100644
--- a/os/osinit.c
+++
This avoids problems if the file descriptor is too large for select(2)
Signed-off-by: Keith Packard
---
os/connection.c | 12
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/os/connection.c b/os/connection.c
index 4c1ba4b..488672c 100644
---
This is a cleanup, proposed by Adam Jackson, but wasn't merged with
the original NotifyFD changes.
Signed-off-by: Keith Packard
---
hw/xfree86/drivers/modesetting/vblank.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This avoids fd limits
Signed-off-by: Keith Packard
---
hw/kdrive/fake/mouse.c | 1 -
hw/kdrive/linux/evdev.c | 14 +-
hw/kdrive/linux/mouse.c | 34 +-
hw/kdrive/linux/ms.c| 13 +
hw/kdrive/linux/ps2.c | 13
This matches a change made in xcb and improves performance for a small
increase in memory usage.
Signed-off-by: Keith Packard
---
os/io.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/os/io.c b/os/io.c
index 19a449a..d04ebd8 100644
--- a/os/io.c
+++
The screen block and wakeup handlers are the only ones which provide a
well known ordering between the wrapping layers; placing these as
close as possible to the server blocking provides a way for the driver
to control the flow of execution correctly.
Switch the shadow code to run in the screen
Hi,
On 26-05-16 18:20, Nikhil Mahale wrote:
In prime configurations master's last set time may not be latest
and greatest, adjust it with slaves last set time, pick up greatest
one. Otherwise xserver may end with events which has
lastSetTime < lastConfigTime even if that's not
the case and
Adam Jackson writes:
> Exposing edge/level in ospoll_add is a bit funky, you're silently
> degrading edge to level if the OS backend can't do edge. kqueue could do
> it if the code were written, and I suspect win32's WaitForMultipleObjects
> could be made to do it if we got really
On Wed, 2016-05-25 at 22:44 -0700, Keith Packard wrote:
> It's similar to the NotifyFd interfaces added to the OS layer, but has
> the ability to support both level-triggered and edge-triggered
> notifications. Using edge-triggered notifications along with epoll
> reduces the notifications
In prime configurations master's last set time may not be latest
and greatest, adjust it with slaves last set time, pick up greatest
one. Otherwise xserver may end with events which has
lastSetTime < lastConfigTime even if that's not
the case and confuse xrandr client.
---
randr/randr.c | 9
Michel Dänzer writes:
> The glamor_set_composite_texture related change in this patch needs to
> be moved to patch 3, or this patch fails to build. With that fixed,
> patches 1 & 2 are
That was also mentioned by Emil Velikov and was fixed in [v4] 1/3 and [v2] 3/3
>
Peter Hutterer writes:
>> Signed-off-by: Keith Packard
>
> Acked-by: Peter Hutterer
Merged.
b64108f..f5670b4 master -> master
--
-keith
signature.asc
Description: PGP signature
On 25 May 2016 at 08:41, Ian Ray wrote:
> posix_fallocate() does an explicit rollback if it gets EINTR, and
> this is a problem on slow systems because when the allocation size
> is sufficiently large posix_fallocate() will always be interrupted
> by the smart scheduler's SIGALRM.
Hi,
On 26-05-16 12:04, Michel Dänzer wrote:
From: Michel Dänzer
Commit b64108fa ("glamor: Check for composite operations which are
equivalent to copies") failed to copy conditions from exaComposite which
ensure that the composite operation doesn't access outside of the
Hi,
On 20-05-16 07:01, Nikhil Mahale wrote:
In prime configurations master's last set time may not be latest
and greatest, adjust it with slaves last set time, pick up greatest
one. Otherwise xserver may end with events which has
lastSetTime < lastConfigTime even if that's not
the case and
On 17.05.2016 06:05, Keith Packard wrote:
> Michel Dänzer writes:
>
>> https://bugs.freedesktop.org/show_bug.cgi?id=63397#c24
>
> Some day I'll think to look at bugzilla when I fix a bug :-)
>
> I've added a comment and copy of the patch to that bug.
The
From: Michel Dänzer
Commit b64108fa ("glamor: Check for composite operations which are
equivalent to copies") failed to copy conditions from exaComposite which
ensure that the composite operation doesn't access outside of the source
picture.
This fixes rendercheck
On 26.05.2016 11:21, Nikhil Mahale wrote:
> On 05/26/2016 01:31 PM, Timo Aaltonen wrote:
>> On 20.05.2016 08:00, Nikhil Mahale wrote:
>>> For gpu screen, CrtcSet set/adjust the master screen size along
>>> mode in following callstack -
>>>
>>> ProcRRSetCrtcConfig()
>>> |
>>> ->
On 05/26/2016 01:31 PM, Timo Aaltonen wrote:
On 20.05.2016 08:00, Nikhil Mahale wrote:
For gpu screen, CrtcSet set/adjust the master screen size along
mode in following callstack -
ProcRRSetCrtcConfig()
|
-> RRCrtcSet()
|
-> rrCheckPixmapBounding()
|
On 20.05.2016 08:00, Nikhil Mahale wrote:
> For gpu screen, CrtcSet set/adjust the master screen size along
> mode in following callstack -
>
> ProcRRSetCrtcConfig()
> |
> -> RRCrtcSet()
> |
> -> rrCheckPixmapBounding()
> |
> ->
epoll is designed to reduce the cost of having many file descriptors
in a process which are mostly idle. The kernel only reports data about
active descriptors.
I changed MAXCLIENTS from 512 to 2048 so I could get some 'worst case'
measurements. I figured x11perf -noop would be a nice test, and
Mark Kettenis writes:
> Hmm. This is marked as _X_EXPORT, so presumably part of the driver
> ABI. Exporting variables like this is generally a bad idea, at least
> for ELF DSOs. Copy relocations and all that.
even libc exposes a pile of data, including stdin, stderr
45 matches
Mail list logo