This is completely wrong. The _entire point_ of XShm, as the name implies, is to have _shared memory_ between the client and the X server. And the server controls the card's framebuffer (at least, in traditional X). There's absolutely no copy and that was the entire point of the extension.
(if compositing is enabled, and therefore the GPU is in between, the server eventually has to call texture_from_surface; at that point, whether there is a copy or not depends on the GPU's driver).
You could literally read the PREVIOUS contents of your card's framebuffer by doing XShmGetImage on the root window.
> No, for video, the GPU is used in the middle so you can do post-processing without copying everything into main memory and stalling the whole pipeline.
You can do many types of card-accelerated zero-copy post-processing using XV: colorspace conversion, scaling, etc., which, again, was the point of the extension. At the time, scaling the video in software or even just doing a memory copy per frame would have completely tanked frame rate. How do you think I used Xine to watch DVDs on Pentium II-level hardware? Obviously you cannot put the video in faces of rotating 3D cube, but this is precisely what I call "fancy animations".
Fair enough. Even with XShmCreatePixmap, you are still never simply mmaping the card's actual entire framebuffer, unlike what BDirectWindow allows (if https://www.haiku-os.org/legacy-docs/benewsletter/Issue3-12.... is to believed, which is closer to something like DGA). In XShm, the server still has to copy your shared memory segment to the actual framebuffer.
(sorry for previous answer here, I misunderstood your comment)
> No, for video, the GPU is used in the middle so you can do post-processing without copying everything into main memory and stalling the whole pipeline.
Depends on what you mean by "post-processing". You can do many types of card-accelerated zero-copy post-processing using XV: colorspace conversion, scaling, etc. At the time, scaling the video in software or even just doing an extra memory copy per frame would have tanked frame rate -- Xine can be used to watch DVDs in PentiumII-level hardware. Obviously you cannot put the video in the faces of rotating 3D cubes, but this is precisely what I call "fancy animations".
Anyway, discussing about this is besides the point, and forgive me from the rant above.
If you really need GPU video filters then the GPU is obviously going to be the best way to implement them, there's no discussion possible about that. But the entire point of TFA is to (dynamically) go back to a model where the GPU is _not_ in the middle. And that model -- sans GPU -- happens to match what Xv was doing and is actually faster and less power consuming than to always blindly use the GPU which is where we are now post-Xv.
No, XShm doesn't do that and the way XV does it is completely dependent on drivers. If you're using Glamour then XV won't use overlays at all. XShm uses a buffer created in CPU memory allocated by the client that the X server then has to copy to the screen.
> Of course then everyone got rid of this in order to have the GPU in the middle for fancier animations
No, for video, the GPU is used in the middle so you can do post-processing without copying everything into main memory and stalling the whole pipeline. I'd like to see an actual benchmark for how a fullscreen 5k video with post-processing plays on Haiku without any hardware acceleration.