mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2024-12-30 22:54:35 +03:00
05ba034000
This class is intended to replace all IOAddress usages in the Kernel
codebase altogether. The idea is to ensure IO can be done in
arch-specific manner that is determined mostly in compile-time, but to
still be able to use most of the Kernel code in non-x86 builds. Specific
devices that rely on x86-specific IO instructions are already placed in
the Arch/x86 directory and are omitted for non-x86 builds.
The reason this works so well is the fact that x86 IO space acts in a
similar fashion to the traditional memory space being available in most
CPU architectures - the x86 IO space is essentially just an array of
bytes like the physical memory address space, but requires x86 IO
instructions to load and store data. Therefore, many devices allow host
software to interact with the hardware registers in both ways, with a
noticeable trend even in the modern x86 hardware to move away from the
old x86 IO space to exclusively using memory-mapped IO.
Therefore, the IOWindow class encapsulates both methods for x86 builds.
The idea is to allow PCI devices to be used in either way in x86 builds,
so when trying to map an IOWindow on a PCI BAR, the Kernel will try to
find the proper method being declared with the PCI BAR flags.
For old PCI hardware on non-x86 builds this might turn into a problem as
we can't use port mapped IO, so the Kernel will gracefully fail with
ENOTSUP error code if that's the case, as there's really nothing we can
do within such case.
For general IO, the read{8,16,32} and write{8,16,32} methods are
available as a convenient API for other places in the Kernel. There are
simply no direct 64-bit IO API methods yet, as it's not needed right now
and is not considered to be Arch-agnostic too - the x86 IO space doesn't
support generating 64 bit cycle on IO bus and instead requires two 2
32-bit accesses. If for whatever reason it appears to be necessary to do
IO in such manner, it could probably be added with some neat tricks to
do so. It is recommended to use Memory::TypedMapping struct if direct 64
bit IO is actually needed.
|
||
|---|---|---|
| .. | ||
| AddressSpace.cpp | ||
| AddressSpace.h | ||
| AllocationStrategy.h | ||
| AnonymousVMObject.cpp | ||
| AnonymousVMObject.h | ||
| InodeVMObject.cpp | ||
| InodeVMObject.h | ||
| MappedROM.h | ||
| MemoryManager.cpp | ||
| MemoryManager.h | ||
| PageDirectory.cpp | ||
| PageDirectory.h | ||
| PageFaultResponse.h | ||
| PhysicalPage.cpp | ||
| PhysicalPage.h | ||
| PhysicalRegion.cpp | ||
| PhysicalRegion.h | ||
| PhysicalZone.cpp | ||
| PhysicalZone.h | ||
| PrivateInodeVMObject.cpp | ||
| PrivateInodeVMObject.h | ||
| Region.cpp | ||
| Region.h | ||
| RegionTree.cpp | ||
| RegionTree.h | ||
| RingBuffer.cpp | ||
| RingBuffer.h | ||
| ScatterGatherList.cpp | ||
| ScatterGatherList.h | ||
| ScopedAddressSpaceSwitcher.cpp | ||
| ScopedAddressSpaceSwitcher.h | ||
| SharedFramebufferVMObject.cpp | ||
| SharedFramebufferVMObject.h | ||
| SharedInodeVMObject.cpp | ||
| SharedInodeVMObject.h | ||
| TypedMapping.h | ||
| VirtualRange.cpp | ||
| VirtualRange.h | ||
| VMObject.cpp | ||
| VMObject.h | ||