Feature #6732
closed
Support non-system architectures
Added by Evgeny Novikov about 8 years ago.
Updated almost 7 years ago.
Category:
* Build commands extracting
Description
At the moment any architecture where Klever and its addons are built, installed and run are supported. But likely it is very-very hard or even impossible to built some specific addons, e.g. CIF, as well as to ensure all run-time dependencies on some specific architectures. Moreover running Klever on them will be a disaster since they are intended for other purposes. That is why it has sense to support non-system architectures (likely everything except x86 and x86_64) when we have just a corresponding cross compiler. This will require many works at the level of CIF as well.
- Subject changed from Support ARM to Support non-system architectures
- Description updated (diff)
- Assignee set to Evgeny Novikov
- Priority changed from Normal to Immediate
I would say: Support cross-verification
Alexey Khoroshilov wrote:
I would say: Support cross-verification
This particular issue covers just building of the Linux kernel for non-system architectures when a cross compiler is available, although it isn't obvious from the description. For other components and tools I would like to have other issues.
- Assignee deleted (
Evgeny Novikov)
- Priority changed from Immediate to High
Let's postpone it until it will be really necessary.
- Assignee set to Ilja Zakharov
- Priority changed from High to Immediate
Currently, it is a quite important issue.
- Priority changed from Immediate to Urgent
It isn't a bug that breaks common workflows.
- Status changed from New to Resolved
Implemented for ARM in 'cross-verification' branch.
- Status changed from Resolved to Open
Ilja Zakharov wrote:
Implemented for ARM in 'cross-verification' branch.
This issue requested for basic support for any architecture. That's why the ARM support isn't enough. From the other side I guess that actually any architecture is theoretically supported within Klever in this branch (perhaps just very small improvements in source code should be done). If so, it can be really marked as resolved.
The real pain is to develop cross CIF for target architectures.
- Status changed from Open to Resolved
Yes, a new architecture can be supported by adding a couple of source lines with additional build command options. However, you should have corresponding CIF cross-compiler and working CIL for your platform.
Ilja Zakharov wrote:
Yes, a new architecture can be supported by adding a couple of source lines with additional build command options. However, you should have corresponding CIF cross-compiler and working CIL for your platform.
Is it documented anywhere?
Alexey Khoroshilov wrote:
Ilja Zakharov wrote:
Yes, a new architecture can be supported by adding a couple of source lines with additional build command options. However, you should have corresponding CIF cross-compiler and working CIL for your platform.
Is it documented anywhere?
The idea was just to have basic support of non-system target architectures for the Linux kernel within Klever. Building and providing cross-compiling CIF, non-x86 CIL, etc. and corresponding documentation are out of the scope of this issue.
But what is about documenting
adding a couple of source lines with additional build command options.
?
Alexey Khoroshilov wrote:
But what is about documenting
adding a couple of source lines with additional build command options.
?
Klever hasn't documentation almost at all, in particular for such the internal thing. I think that it won't have it in any near future. Just some standard features like verification objects generation strategies will be documented somehow. There are several opened issues but they don't have very high priorities.
- Status changed from Resolved to Closed
Merged in 5baf5c80.
Evgeny correctly stated that we have almost no documentation for Klever (unfortunately) but CIF cross-compiler I obtained with Docker and corresponding notes and final Docker file I have added to the master branch of the CIF project, so it will not be lost.
Also available in: Atom
PDF