15.0.0: Difference between revisions

Line 126:

*** KMemoryState_Io now supports the CanAlignedDeviceMap and CanDeviceMap flags.

*** KPageTableBase::GetContiguousMemoryRangeWithState no longer checks that the passed memory address is heap.

**** KPageTable::MemoryRange now tracks whether the range is reference counted, and Close() only closes the pages if they are.

*** KPageTableBase::OpenMemoryRangeForMapDeviceAddressSpace no longer checks passes KMemoryState_FlagReferenceCounted.

*** KPageTableBase::LockForMapDeviceAddressSpace takes two new arguments, an output bool * to write whether the state was io, and a bool for whether to check KMemoryState_FlagReferenceCounted.

Line 149:

Line 150:

*** When a process is created with system resource size > 0, it now creates a KSecureSystemResource (which manages allocation with KSystemControl).

**** All actual underlying logic is the same, this just abstracts the KSystemControl/secure memory interaction out of KProcess.

* KPageTable::MemoryRange now tracks whether the range is reference counted, and Close() only closes the pages if they are.

* KInterruptEventTask was removed and no longer exists.

** KInterruptEvent now inherits from KInterruptTask directly.

@@ Line 126: / Line 126: @@
 *** KMemoryState_Io now supports the CanAlignedDeviceMap and CanDeviceMap flags.
 *** KPageTableBase::GetContiguousMemoryRangeWithState no longer checks that the passed memory address is heap.
+**** KPageTable::MemoryRange now tracks whether the range is reference counted, and Close() only closes the pages if they are.
 *** KPageTableBase::OpenMemoryRangeForMapDeviceAddressSpace no longer checks passes KMemoryState_FlagReferenceCounted.
 *** KPageTableBase::LockForMapDeviceAddressSpace takes two new arguments, an output bool * to write whether the state was io, and a bool for whether to check KMemoryState_FlagReferenceCounted.
@@ Line 149: / Line 150: @@
 *** When a process is created with system resource size > 0, it now creates a KSecureSystemResource (which manages allocation with KSystemControl).
 **** All actual underlying logic is the same, this just abstracts the KSystemControl/secure memory interaction out of KProcess.
-* KPageTable::MemoryRange now tracks whether the range is reference counted, and Close() only closes the pages if they are.
 * KInterruptEventTask was removed and no longer exists.
 ** KInterruptEvent now inherits from KInterruptTask directly.