Comments (8)
setvar_vaddr
is optional, so is the only problematic variable microkit_name
?
from microkit.
Having an option such as --no-elf-patching
to the tool may be possible, but I would only want to do this if this is a problem across multiple/all systems programming languages.
Changing Microkit to work around a limitation in Rust seems weird.
from microkit.
This Rust scenario is just the specific reason why I've found myself wishing the tool had this slightly more general behavior.
I see the change I'm proposing as a slight generalization of the current behavior. From:
Patch each variable
To:
Patch each variable that actually exists in the binary
Making the tool more permissive in this way would simplify PD constructions by reducing the assumptions made about their structure.
from microkit.
But it seems there is only one assumption we are talking about here, and that is the existence of microkit_name
, right?
from microkit.
I would find the behaviour of the tool weird if you had in your system description setvar_vaddr
and then it didn't actually do that because of some control flow that is hidden from the user.
from microkit.
The tool derives, from the system description, a set of variables that it would patch for each PD. The assumption that I'm talking about is the assumption that all of these variables are present in the corresponding PD binaries.
from microkit.
I would find the behaviour of the tool weird if you had in your system description setvar_vaddr and then it didn't actually do that because of some control flow that is hidden from the user.
A case where I think that behavior would be nice is during development, before a PD developer has built out the PD to the point where the relevant variable is actually used.
from microkit.
A case where I think that behavior would be nice is during development, before a PD developer has built out the PD to the point where the relevant variable is actually used.
Then during development just omit setvar_vaddr
?
The behaviour of the variable patching is I think very clear right now. You ask the tool to patch a variable, and it does it. If it can't patch the variable you get a clear error message.
This approach would remove that clear behaviour, and I am not convinced right now that it is beneficial to do that just because a compiler invalidates the assumption. It seems that you are working around the behaviour of a compiler. I do not think it is unreasonable for a compiler for a systems programming language to explicitly leave in a symbol at the request of its user.
I will continue thinking about the issue, I haven't reached a conclusion.
from microkit.
Related Issues (20)
- Do not assume kernel is configured with HAVE_SET_TRIGGER
- Add 1GiB page size for AArch64
- Check that registered IRQ numbers are sane
- API for dealing with cache-coherency on ARM HOT 1
- Please add versioned releases of the sdk HOT 2
- Please do not rely on **any** system headers for the microkit API HOT 1
- Declare stable API & ABI to ease implementation of Rust API HOT 15
- Make `static inline` optional HOT 4
- seL4 floating point compilation support HOT 6
- What is the purpose of the content of a passive server's initialization complete message HOT 2
- manual: typos and other questions HOT 1
- tool: Use `rustfmt` HOT 7
- 1.3.0 release archive permissions HOT 2
- Tutorial: part4 ppcall from VMM to less prioritized Wordle_server HOT 6
- Allow specifying `phys_addr` for non-device memory
- Use larger pages when mapping in large ELFs
- Complain at a microkit level of IRQ ACK is called on a non-irq channel HOT 1
- setvar_vaddr will happily patch the same variable twice HOT 1
- Microkit stack size HOT 1
- Have a "setvar" to reference Size of Memory Region from System Description in User Code
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from microkit.