xenomai.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard.weinberger@gmail.com>
To: "Chen, Hongzhan" <hongzhan.chen@intel.com>
Cc: Xenomai <xenomai@lists.linux.dev>
Subject: Re: i915 GPU woes
Date: Tue, 7 May 2024 11:39:38 +0200	[thread overview]
Message-ID: <CAFLxGvwUW-+DuMGuEX8oRFQYXvPcs3GiEz5uCuZa_uDCQBx-wg@mail.gmail.com> (raw)
In-Reply-To: <PH7PR11MB749982301BE568CE531BB6FEF2082@PH7PR11MB7499.namprd11.prod.outlook.com>

On Tue, Apr 16, 2024 at 4:02 AM Chen, Hongzhan <hongzhan.chen@intel.com> wrote:
> >What do you think about the i915 module parameters I have configured?
>
> You already set all the parameters we suggest to set for i915 like " i915.disable_power_well=0
> i915.enable_dc=0 i915.enable_rc6=0" which is to prevent integrated graphics from changing power states.
> If you already narrow down to graphics MMIO related, I do not know if it may help improve performance to limit
> mem used by graphics via DVMT but there is no such options in your bios.

The riddle is more or less solved.

It turned(sic!) out that the problem occurs only on systems with a
rotated screen.
Plus, only when the Intel xorg driver is in use.
By switching to xorg modsetting the problem is gone. Looks like the
modesetting driver
causes the GPU to do the screen rotation differently and the GPU no
longer blocks other
cores.
Further I had to disable frame buffer compression (i915.enable_fbc=0)
to get decent results.

-- 
Thanks,
//richard

      reply	other threads:[~2024-05-07  9:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-14 20:54 i915 GPU woes Richard Weinberger
2024-04-15  4:28 ` Chen, Hongzhan
2024-04-15  4:38   ` Chen, Hongzhan
2024-04-15 21:46     ` Richard Weinberger
2024-04-16  2:02       ` Chen, Hongzhan
2024-05-07  9:39         ` Richard Weinberger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFLxGvwUW-+DuMGuEX8oRFQYXvPcs3GiEz5uCuZa_uDCQBx-wg@mail.gmail.com \
    --to=richard.weinberger@gmail.com \
    --cc=hongzhan.chen@intel.com \
    --cc=xenomai@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).