public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: Simon Richter <Simon.Richter@hogyros.de>
To: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: Simon Richter <Simon.Richter@hogyros.de>
Subject: [PATCH 5.3-6.19 0/1] Avoid oops on illegal VGA register access
Date: Sat,  7 Mar 2026 00:23:46 +0900	[thread overview]
Message-ID: <20260306152413.758919-1-Simon.Richter@hogyros.de> (raw)

Hi,

this is a backport of https://patchwork.freedesktop.org/series/161721/ that
should apply to anything between 5.3-rc4 and 6.19.

It adds a way to avoid the illegal VGA accesses on non-x86 platforms by
letting these platforms report that VGA registers cannot be mapped.

This patch alone doesn't fully solve the problem, it also needs complementary
changes in vgaarb to actually report this, but since the interface is unchanged
and it is wrong to ignore the error code anyway, little coordination is needed
here.

   Simon

Simon Richter (1):
  drm/i915: handle failure from vga_get()

 drivers/gpu/drm/i915/display/intel_vga.c | 21 +++++++++++++++++++--
 1 file changed, 19 insertions(+), 2 deletions(-)


base-commit: 6a753907865e35ae986b7b2ad48daa1eab4bcf3a
-- 
2.47.3


             reply	other threads:[~2026-03-06 15:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06 15:23 Simon Richter [this message]
2026-03-06 15:23 ` [PATCH 1/1] drm/i915: handle failure from vga_get_uninterruptible() Simon Richter
2026-03-08 22:44   ` Claude review: " Claude Code Review Bot
2026-03-08 22:44 ` Claude review: Avoid oops on illegal VGA register access Claude Code Review Bot

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=20260306152413.758919-1-Simon.Richter@hogyros.de \
    --to=simon.richter@hogyros.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    /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