Add an RF_CACHEABLE flag for rman activations
AbandonedPublic
Actions

Authored by jhibbits on Feb 22 2016, 1:38 AM.

Tags

Referenced Files

	F133154607: D5384.id13587.diff
	Thu, Oct 23, 11:28 AM

	F133154599: D5384.id.diff
	Thu, Oct 23, 11:28 AM

	Unknown Object (File)
	Thu, Oct 23, 2:48 AM

	Unknown Object (File)
	Sun, Oct 19, 10:20 PM

	Unknown Object (File)
	Tue, Oct 14, 3:36 PM

	Unknown Object (File)
	Sun, Oct 5, 11:34 PM

	Unknown Object (File)
	Tue, Sep 30, 7:24 PM

	Unknown Object (File)
	Tue, Sep 30, 2:34 PM

View All 84 Files

Subscribers

None

Details

Reviewers

jhb
imp

Summary

This is intended for devices where the default memory flags don't suffice, for
example if a device has cache-inhibited and cache-enabled regions (Freescale
QorIQ DPAA portals).

Diff Detail

Repository

rS FreeBSD src repository - subversion

Lint

Lint Skipped

Unit

Tests Skipped

Event Timeline

jhibbits updated this revision to Diff 13587.Feb 22 2016, 1:38 AM

jhibbits retitled this revision from to Add an RF_CACHEABLE flag for rman activations.

jhibbits updated this object.

jhibbits edited the test plan for this revision. (Show Details)

jhibbits added reviewers: jhb, imp.

jhibbits set the repository for this revision to rS FreeBSD src repository - subversion.

jhibbits added a project: Src Committers.

I've thought about having a RF_WC for WC mappings as well, but I'd really rather finish bus_map_resource() and use that for handling non-default memory attributes instead.

Abandoning in favor of D5471