> The framebuffer that is displayed on the monitor is always in video card
> memory. There is a piece of hardware (CRTC) that continuously pulls data
> from the framebuffer and transmits it to the monitor.
So the framebuffer memory should normally be in the kernel (Perhaps in special
cases
On Sun, 27 Aug 2023, Ahmad Nouralizadeh wrote:
> In order to display anything on the screen the video card needs an array
>of data given color of each pixel. This is usually called "framebuffer"
>because it buffers data for one frame of video.
Thank you for the enlightening explanation! An
> In order to display anything on the screen the video card needs an array
>of data given color of each pixel. This is usually called "framebuffer"
>because it buffers data for one frame of video.
Thank you for the enlightening explanation! An unrelated question: IIUC the
framebuffer is a
On Sat, 26 Aug 2023, Ahmad Nouralizadeh wrote:
> > However, I would have expected that VLC would produce a lot
> > GPU/iGPU accesses even without drawing anything, because it would
> > try to use GPU decoder.
For the discrete GPU, the turned off screen requires much smaller bandwidth in
any
> > However, I would have expected that VLC would produce a lot
> > GPU/iGPU accesses even without drawing anything, because it would
> > try to use GPU decoder.
For the discrete GPU, the turned off screen requires much smaller bandwidth in
any benchmark (reduces from 2GB/s to several KB/s). The
On Sat, 26 Aug 2023 20:46:35 +0100, Dave Howorth wrote:
> On Sat, 26 Aug 2023 13:43:21 -0400 (EDT), Vladimir Dergachev wrote:
>
> > On Sat, 26 Aug 2023, Ahmad Nouralizadeh wrote:
> >
> > > >> Those accesses might not stop with just the display off - some
> > > >> applications may keep
On Sat, 26 Aug 2023 13:43:21 -0400 (EDT), Vladimir Dergachev wrote:
> On Sat, 26 Aug 2023, Ahmad Nouralizadeh wrote:
>
> > >> Those accesses might not stop with just the display off - some
> > >> applications may keep redrawing.
> > Will these accesses cause iGPU or dedicated GPU accesses to
On Sat, 26 Aug 2023, Ahmad Nouralizadeh wrote:
>> Those accesses might not stop with just the display off - some
>> applications may keep redrawing.
Will these accesses cause iGPU or dedicated GPU accesses to the DRAM? I think
that those redrawings originate from the processor.
>I'm not
>> Those accesses might not stop with just the display off - some
>> applications may keep redrawing.
Will these accesses cause iGPU or dedicated GPU accesses to the DRAM? I think
that those redrawings originate from the processor.
>I'm not sure a graphical benchmark will run without a
On Sat, 26 Aug 2023 12:11:03 -0400 (EDT)
Vladimir Dergachev wrote:
> On Sat, 26 Aug 2023, Ahmad Nouralizadeh wrote:
>
> > I want to count the processor-initiated memory accesses. On my 4K
> > display, a huge number of accesses originate from the iGPU and
> > dedicated GPU. I want to exclude
On Sat, 26 Aug 2023, Ahmad Nouralizadeh wrote:
I want to count the processor-initiated memory accesses. On my 4K display, a
huge number of accesses originate from the iGPU and dedicated GPU. I want to
exclude these accesses. The IMC counter can
only track the dedicated GPU accesses.
I want to count the processor-initiated memory accesses. On my 4K display, a
huge number of accesses originate from the iGPU and dedicated GPU. I want to
exclude these accesses. The IMC counter can only track the dedicated GPU
accesses. Therefore, I have to turn the screen off to exclude those
On Sat, 26 Aug 2023 15:28:52 + (UTC)
Ahmad Nouralizadeh wrote:
> I need to run a set of (graphical) benchmarks with the screen
> disabled.
Can I ask why? What is you're trying to accomplish? Somehow affect the
benchmarks? Stop people seeing the benchmarks being performed?
And what is the
Hi,
I need to run a set of (graphical) benchmarks with the screen disabled. The
following command did not work:
xset dpms force off
Because any keyboard/mouse input would re-enable the screen. The other option
was the following:
xrandr --output eDP-1 --off
This turns off the screen for a
14 matches
Mail list logo
