pciconf: Use VM_MEMATTR_DEVICE on supported architectures
ClosedPublic
Actions

Authored by kd on Apr 6 2021, 1:35 PM.

Tags

None

Referenced Files

	F122763520: D29603.id86902.diff
	Tue, Jul 8, 2:07 AM

	Unknown Object (File)
	Mon, Jul 7, 6:54 AM

	Unknown Object (File)
	Sat, Jun 14, 5:54 PM

	Unknown Object (File)
	Tue, Jun 10, 5:38 AM

	Unknown Object (File)
	May 30 2025, 6:03 PM

	Unknown Object (File)
	May 17 2025, 3:10 PM

	Unknown Object (File)
	May 13 2025, 11:50 AM

	Unknown Object (File)
	May 9 2025, 2:17 AM

View All Files

Subscribers

None

Details

Reviewers

kib
mw

Commits

rG2a8921c5d187: pciconf: Use VM_MEMATTR_DEVICE on supported architectures
rG1c1ead9b94a1: pciconf: Use VM_MEMATTR_DEVICE on supported architectures

Summary

Some architectures - armv7, armv8 and riscv use VM_MEMATTR_DEVICE when mapping device registers in kernel.
Do the same in pciconf when mmaping BARs.
On armada8k SoC all reads from BARs mapped with VM_MEMATTR_UNCACHEABLE return 0xffs.

Diff Detail

Repository

rG FreeBSD src repository

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

kd requested review of this revision.Apr 6 2021, 1:35 PM

kd created this revision.

kib accepted this revision.Apr 6 2021, 2:50 PM

This revision is now accepted and ready to land.Apr 6 2021, 2:50 PM

Closed by commit rG1c1ead9b94a1: pciconf: Use VM_MEMATTR_DEVICE on supported architectures (authored by mw). · Explain WhyApr 6 2021, 3:17 PM

This revision was automatically updated to reflect the committed changes.

mw added a commit: rG1c1ead9b94a1: pciconf: Use VM_MEMATTR_DEVICE on supported architectures.

andrew added a commit: rG2a8921c5d187: pciconf: Use VM_MEMATTR_DEVICE on supported architectures.Jun 13 2021, 7:16 PM

Revision Contents
Changeset List

Path

Size

usr.sbin/

pciconf/

pciconf.c

6 lines

Diff 86909

View Options

usr.sbin/pciconf/pciconf.c

pciconf: Use VM_MEMATTR_DEVICE on supported architecturesClosedPublicActions