Fork of alistair23 Linux kernel for reMarkable from https://github.com/alistair23/linux
4e1b20246e
Instead of hardcoding checks for qman cacheable mmio region physical addresses extract mapping information from the user-space mapping. The involves several steps; - get access to a pte part of the user-space mapping by using get_locked_pte() / pte_unmap_unlock() apis - extract memtype (normal / device), shareability from the pte - convert to S2 translation bits in newly added function stage1_to_stage2_pgprot() - finish making the s2 translation with the obtained bits Another explored option was using vm_area_struct::vm_page_prot which is set in vfio-mc mmap code to the correct page bits. However, experiments show that these bits are later altered in the generic mmap code (e.g. the shareability bit is always set on arm64). The only place where the original bits can still be found is the user-space mapping, using the method described above. Signed-off-by: Laurentiu Tudor <laurentiu.tudor@nxp.com> [Bharat - Fixed mem_type check issue] [changed "ifdef ARM64" to CONFIG_ARM64] Signed-off-by: Bharat Bhushan <Bharat.Bhushan@nxp.com> [Ioana - added a sanity check for hugepages] Signed-off-by: Ioana Ciornei <ioana.ciornei@nxp.com> [Fixed format issues] Signed-off-by: Diana Craciun <diana.craciun@nxp.com> |
||
|---|---|---|
| Documentation | ||
| LICENSES | ||
| arch | ||
| block | ||
| certs | ||
| crypto | ||
| drivers | ||
| fs | ||
| include | ||
| init | ||
| ipc | ||
| kernel | ||
| lib | ||
| mm | ||
| net | ||
| samples | ||
| scripts | ||
| security | ||
| sound | ||
| tools | ||
| usr | ||
| virt | ||
| .clang-format | ||
| .cocciconfig | ||
| .get_maintainer.ignore | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| COPYING | ||
| CREDITS | ||
| Kbuild | ||
| Kconfig | ||
| MAINTAINERS | ||
| Makefile | ||
| README | ||
README
Linux kernel
============
There are several guides for kernel developers and users. These guides can
be rendered in a number of formats, like HTML and PDF. Please read
Documentation/admin-guide/README.rst first.
In order to build the documentation, use ``make htmldocs`` or
``make pdfdocs``. The formatted documentation can also be read online at:
https://www.kernel.org/doc/html/latest/
There are various text files in the Documentation/ subdirectory,
several of them using the Restructured Text markup notation.
Please read the Documentation/process/changes.rst file, as it contains the
requirements for building and running the kernel, and information about
the problems which may result by upgrading your kernel.