Jarkko Sakkinen / is on Nostr

I'm a Linux kernel engineer with the focus in TEE's and confidential computing. Right now I'm enabling Keystone and fTPM for RISC-V Linux

Last Notes

2024-08-06 06:38:39

I don't think #Rust should have any business in any core features of #Linux #kernel before there is GPL licensed toolchain for it. #rustlang

2024-07-21 15:37:00

https://github.com/m4b/goblin/issues/415

2024-06-28 05:31:02

https://www.theregister.com/2024/06/24/mozilla_product_chief_sues_over/

2024-06-27 11:50:35

#Python #IDLE is still rockin' :-) Always have it open as my calculator (and doing binary analysis and whatnot).
https://media.social.kernel.org/media/5181dee1c131532ee805b33f5a4df8295f3fef8d2b3c26953b8502f85e0d3aa2.png

2024-06-14 16:27:47

When cargo publish -p tpm2_cli , I need to
tpm2_call = "0.1.1"
… while building locally:
tpm2_call = { path = "../tpm2_call" }
How to sort this out in “idiomatic manner”?
#rust #rustlang

2024-05-07 12:08:57

- reply

@npub14zy…2z57 I have one SBC for RISC-V (VisionFive2) but would be nice to get one MMUless SBC too (i.e. without S-mode). I.e. kind of RISC-V "arduino".

2024-05-06 19:57:01

OK, so WFI on RISC-V is not detemistic! It can be same as HLT (x86) or WAIT (ARM) but could also be nop 🤷 Beyond me tbh. #riscv

2023-12-10 08:54:20

- reply

@npub1eqg…fncn given how tied the standard library is to vec, using collect is sort of encouraged in the API nothing to do with Rust as a language. rust is in binary level pretty much equivalent to C++.

2023-12-10 02:33:06

In Rust programs one common theme, which is not great for optimizing memory footprint, is the heavy use of collect(). Iterators are a great abstraction exactly for the reason that you can view items as a set without having to brute force deploy them as such in memory. One area where no language paradigm can protect against is the overuse of computing resource.
One good recipe against this e.g. in a commercial setting would be to set a constraint for core components to be no_std compatible and have total artistic freedom in user interfacing parts or e.g. storage backend interfacing part i.e. only in I/O code.
Then early steps are slower but sort of investments instead of debt when memory is considered early on…
There’s little gain with the added complexity of Rust to something like Go if this consideration is not done. Sometimes something like Go could do even a better job because then at least garbage collector considers memory constraints..
#rustlang