(Yes, the kernel has hardware-model-specific quirk routines to work around known hardware bugs but getting deeper than that and bypassing the ACPI abstraction provided by the system firmware would require a great deal more effort, something like coreboot. If any run-time access is possible, I would expect it to be through the ACPI firmware routines otherwise the kernel would have to have specific routines for each chipset. Just saying.Īs far as I know, the "routing table" for memory remapping is at least partly implemented in chipset hardware, and is very chipset-specific, so it is normally set up at boot time by the system firmware. Close to 8GB because my Motherboard has only a maximum addressable of 8GB, so it is really likely that it has only 33 lines of ABUS, so regardless of processor and chipset. On my system, the resulting mapping for GPU looks like this: 6000000000-600fffffff : 0000:01:00.0Īlso, 250MB is just about 1.5% of 16 GB if getting the last 1.5% of memory is truly critical, you might get a noticeable performance benefit from getting more RAM if at all possible. Close to 64GB because my Processor has got only 36bit of ABUS, regardless of motherboard and chipset (I have a E6600 now) 2. With that setting enabled, any MMIO hardware that is capable of dealing with 64-bit addresses gets mapped to addresses outside the traditional 32-bit range, minimizing the conflicts with memory and so reducing the need for remapping slots. As you have a 64-bit operating system, you could enable the BIOS setting "Above 4G Decoding", "64-bit I/O address decoding" or whatever it's called by your system/motherboard vendor.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |