From: sashiko-bot@kernel.org
To: "Matt Thompson" <matt@boondocker.io>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH RFC v2 2/3] arm64: Allow synchronous abort fixups for guarded MMIO reads
Date: Sat, 14 Nov 2026 01:02:27 +0000 [thread overview]
Message-ID: <sashiko-outbox-213974@kernel.org> (raw)
In-Reply-To: <20261113-rfc-b4-v2-2-d6b14f95c1d6@boondocker.io>
> From: Matt Thompson <matt@boondocker.io>
>
> An RK3399 PCI configuration read can raise a synchronous external data
> abort if it does not get a usable response. Allow an explicitly annotated
> MMIO load to return an error in this case.
>
> Match only a current-EL synchronous external abort on a read instruction
> with the new exception table type. Keep existing handling for other
> faults, including asynchronous SError and translation table walk aborts.
>
> Signed-off-by: Matt Thompson <matt@boondocker.io>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261113-rfc-b4-v2-0-d6b14f95c1d6@boondocker.io?part=2
next prev parent reply other threads:[~2026-11-14 1:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 0:52 [PATCH RFC v2 0/3] PCI: rockchip-host: Handle unavailable downstream config space Matt Thompson
2026-11-14 0:52 ` Matt Thompson via B4 Relay
2026-11-14 0:52 ` Matt Thompson via B4 Relay
2026-11-14 0:52 ` [PATCH RFC v2 1/3] PCI: rockchip-host: Skip downstream config access while link is down Matt Thompson via B4 Relay
2026-11-14 0:52 ` Matt Thompson via B4 Relay
2026-11-14 0:52 ` Matt Thompson
2026-11-14 1:03 ` sashiko-bot
2026-11-14 0:52 ` [PATCH RFC v2 2/3] arm64: Allow synchronous abort fixups for guarded MMIO reads Matt Thompson
2026-11-14 0:52 ` Matt Thompson via B4 Relay
2026-11-14 0:52 ` Matt Thompson via B4 Relay
2026-11-14 1:02 ` sashiko-bot [this message]
2026-11-14 0:52 ` [PATCH RFC v2 3/3] PCI: rockchip-host: Recover downstream configuration access Matt Thompson
2026-11-14 0:52 ` Matt Thompson via B4 Relay
2026-11-14 0:52 ` Matt Thompson via B4 Relay
2026-11-14 1:01 ` sashiko-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=sashiko-outbox-213974@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matt@boondocker.io \
--cc=sashiko-reviews@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.