KnownIssues: Difference between revisions
(Gather other system info pages, and add info about kernel modules with FLIX and L32R) |
(Moved hardware contents to another page) |
||
| Line 1: | Line 1: | ||
= Known Kernel Issues and Limitations = | = Known Kernel Issues and Limitations = | ||
This page contains recommendations, notes, limitations, and requirements for the development of software on systems using Xtensa processors running Linux. | |||
This | |||
Eventually all these should be duly reported and tracked in | Eventually all these should be duly reported and tracked in | ||
| Line 20: | Line 8: | ||
== 128 MB RAM Limit == | |||
Kernel highmem support has not yet been implemented, thus restricting generally usable RAM to the first 128 MB (starting from physical address zero). Implementing kernel highmem support should release this limitation, but it isn't yet clear whether an implementation is practical in the presence of cache aliasing (caches larger than 4 x N kB, for an N-way set-associative cache) on RB-200x release or earlier Tensilica processors. | Kernel highmem support has not yet been implemented, thus restricting generally usable RAM to the first 128 MB (starting from physical address zero). Implementing kernel highmem support should release this limitation, but it isn't yet clear whether an implementation is practical in the presence of cache aliasing (caches larger than 4 x N kB, for an N-way set-associative cache) on RB-200x release or earlier Tensilica processors. | ||
== Kernel loadable modules using FLIX with L32R == | |||
The kernel module loader (for the Xtensa architecture) supports only the limited set of relocations needed for module loading. This includes, for example, relocation of literals referenced by L32R instructions. This loader is not given specific information about any custom TIE configured in the processor, and thus is currently not able to relocate L32R instructions encoded in a FLIX bundle. | The kernel module loader (for the Xtensa architecture) supports only the limited set of relocations needed for module loading. This includes, for example, relocation of literals referenced by L32R instructions. This loader is not given specific information about any custom TIE configured in the processor, and thus is currently not able to relocate L32R instructions encoded in a FLIX bundle. | ||
Revision as of 22:02, 9 December 2008
Known Kernel Issues and Limitations
This page contains recommendations, notes, limitations, and requirements for the development of software on systems using Xtensa processors running Linux.
Eventually all these should be duly reported and tracked in the Mantis bug tracker. For the time being, here are some of the main known issues (this is by no means an exhaustive list!).
128 MB RAM Limit
Kernel highmem support has not yet been implemented, thus restricting generally usable RAM to the first 128 MB (starting from physical address zero). Implementing kernel highmem support should release this limitation, but it isn't yet clear whether an implementation is practical in the presence of cache aliasing (caches larger than 4 x N kB, for an N-way set-associative cache) on RB-200x release or earlier Tensilica processors.
Kernel loadable modules using FLIX with L32R
The kernel module loader (for the Xtensa architecture) supports only the limited set of relocations needed for module loading. This includes, for example, relocation of literals referenced by L32R instructions. This loader is not given specific information about any custom TIE configured in the processor, and thus is currently not able to relocate L32R instructions encoded in a FLIX bundle.
To ensure kernel modules load properly, they need to avoid L32R instructions within FLIX instruction bundles.
Existing kernel code does not generate such instructions, so it is not susceptible. However, it is possible to generate FLIX instructions using assembly code, or using the Tensilica XCC compiler. In the case of assembly code, simply avoid using L32R or MOVI instructions within a FLIX instruction bundle, unless a MOVI is known to fit without expanding ("relaxing") into an L32R instruction. In the case of XCC, pass the -mno-flix to the compiler (xt-xcc) to avoid generating FLIX bundles.