Re: [seL4] [HelenOS-devel] FYI: microkernel.info community site

PM if there are any issues pertaining your project's > cartouche that cannot be dealt with using Github. -- Vasily A. Sartakov sarta...@ksyslabs.org signature.asc Description: Message signed with OpenPGP using GPGMail ___ Devel mailing list Devel@sel4.systems https://sel4.systems/lists/listinfo/devel

[seL4] syscalls and tlb

t, is there any syscall for delivery tlb traps? (I see nothing similar) Is there any check inside, for example, SEND call, about a presence of page in TLB? thank you. -- Vasily A. Sartakov sarta...@ksyslabs.org signature.asc Description: Message signed with OpenPGP using GP

Re: [seL4] syscalls and tlb

ing with «hello-4». Previous programs are ok, thus, now my port supports creation of threads, context switching, messaging and syscalls and more. There are some issues with PD creation. So, before the end of September, alpha version of seL4/MIPS will be done, I hope. -- Vasily A. Sartakov sa

[seL4] syscall.c

that I understand this test correct. Can we help me? Thank you -- Vasily A. Sartakov sarta...@ksyslabs.org ___ Devel mailing list Devel@sel4.systems https://sel4.systems/lists/listinfo/devel

Re: [seL4] syscall.c

ls modify stack, since these values are popped from it after the end of a syscall routine, right? > For arm, this just means checking any registers that are not caller saved are > preserved across the system calls. Not sure what this means for MIPS, but > hopefully that clears it

[seL4] endpoint.c

cteRecycle and do not see anything platform specific. I know that it is a complicated question, but any ideas or hints where to look? Thank you -- Vasily A. Sartakov sarta...@ksyslabs.org ___ Devel mailing list Devel@sel4.systems https://sel4.systems

Re: [seL4] endpoint.c

as far I understand, cnode_recycle does not > work at all. I am pretty sure that my seL4_Call syscall was implemented > properly. I have looked inside the kernel, and tried to track everything > related to cteRecycle and do not see anything platform specific. I

Re: [seL4] endpoint.c

> we take address that causes syscall from the ksCurThread and set them back. > Thus, FaultInstruction should point to something different, right? > I have add FaultInstruction in the same manner as it made in ARM platform: sub lr, lr, #4 /* Store FaultInstruction */ str lr, [sp, #(

[seL4] Fwd: Microkernels / Component-based OSes devroom - Call for Participation

> > > Important dates recap > > * 04.12.2016: Deadline for submissions > * 11.12.2016: Schedule published and speakers notified of acceptance > * 04.02.2017: The devroom takes places > > > Links > > [1] http://fosdem.org/ > [2] https://fosdem.org/2017/pr

Re: [seL4] endpoint.c

e a bit different in that it is the > user level fault handler that gets to pick the next instruction. > > Adrian > > On Sat 15-Oct-2016 11:02 PM, Vasily A. Sartakov wrote: >>> we take address that causes syscall from the ksCurThread and set them back. >>> Thus,

[seL4] need ideas

o gradually reduce the amount of code with keeping this 'border' situation, until I will not have very small set of system functions. Thank you -- Vasily A. Sartakov sarta...@ksyslabs.org ___ Devel mailing list Devel@sel4.systems https://sel4.systems/lists/listinfo/devel

Re: [seL4] need ideas

of my binary changes. Thus, maybe I still have an error, but I cannot trigger it with current tests. > On Tue 01-Nov-2016 7:37 AM, Vasily A. Sartakov wrote: >> as you might see, this is little bit modified version of trivial.c tests. >> Usual, when I am testing all tests, there i

Re: [seL4] need ideas

> I already changed my message registers to S0-S3 (Callee saved registers), and > I do not see original issue anymore this is not a 100% true, but I am working in this direction) -- Vasily A. Sartakov sarta...@ksyslabs.org ___ Devel m

[seL4] malloc and SCHED0004

Greetings. I am keep working, and now I would like to discuss my second memory-related issue. In contrast with first one, the second issue happens only in SCHED004 test, in malloc function: helper_thread_t **threads = (helper_thread_t **) malloc(sizeof(helper_thread_t*) * NUM_PRIOS); mall

Re: [seL4] malloc and SCHED0004

and corresponding libraries (3.2.x). The last sync with master trees was made just before MCP was added (mid of September), thus, the diff with master is just the last x86-related commit :( > Adrian > > On Fri 04-Nov-2016 8:58 AM, Vasily A. Sartakov wrote: >> Greetings. >&

Re: [seL4] malloc and SCHED0004

I am using musllibc library from ‘b5c66eef4a8bb274d7a4b9b5b82bce412224dbf9' commit > Adrian > > On Fri 04-Nov-2016 10:19 AM, Vasily A. Sartakov wrote: >>> We have made some changes to muslc. If you diff against changeset >>> '615629bd6fcd6ddb69ad762e679f088c7bd878e2' you

Re: [seL4] malloc and SCHED0004

xpand_heap(size_t *pn) does not work. Now I have OOM due stack allocation, but I think I will solve it. Thank you > Adrian > > On Fri 04-Nov-2016 10:52 AM, Vasily A. Sartakov wrote: >>> I don't understand what you are saying. If you're on a recent version of >>&g

Re: [seL4] Reading executable of the first process in kernel

: where/when does the seL4 kernel start the root process? > I see the end of the same file (boot.c) that it just calls try_init_kernel() > but does not load the root process. try_init_kernel prepares context of the ‘root process’ (and some other things) via create_initial_thread() and after that kernel

[seL4] pic/no-pic and some other questions

sub sp, sp, #4 push {r5,r6} adr r5, 1f ldr r6, 1f ldr r5, [r5,r6] str r5, [sp, #8] pop {r5, r6} pop {pc} .hidden __sysinfo 1: .word __sysinfo-1b something similar to __syscall6 from libmuslc/arch/_sel4/syscall_arch.h, right? Thank you. P/sHappy new

Re: [seL4] pic/no-pic and some other questions

first test. Have no idea why. I will take another look -- Vasily A. Sartakov sarta...@ksyslabs.org signature.asc Description: Message signed with OpenPGP ___ Devel mailing list Devel@sel4.systems https://sel4.systems/lists/listinfo/devel

[seL4] how to debug libsel4allocman

Greetings I am using a 4.0 compatible seL4 snapshot derived from mainline several months ago as a base for seL4/MIPS port. Currently, I am debugging sel4tests. My goal — make everything working before moving to hardware. By «everything» I mean different configurations of the system (optimizat

Re: [seL4] Running Linux on top of seL4

Greetings > Is there any guide about how to run Linux on top of seL4? Or has anyone done > that before that can give me some hints? This FAQ may help: https://wiki.sel4.systems/FrequentlyAskedQuestions#Can_I_run_Linux_on_top_of_seL4.3F ___ Devel

Re: [seL4] seL4SharedData

Hello > Having a flush method on seL4SharedData would be the ideal solution. > > We are not in a position to upgrade our CAmkES version on this product at the > moment. > > Any thoughts? I would also consider a development of CPU-bound memory encryption __

Re: [seL4] Questions about Allocman

Hello > > The physical address is not necessarily stored anywhere, as this is dependent > on the specific untyped manager. There is an interface function > `allocman_utspace_paddr` > (https://github.com/seL4/seL4_libs/blob/master/libsel4allocman/include/allocman/allocman.h#L410) > that will

[seL4] Hardware-aided Trusted Computing devroom at FOSDEM

Hello I would like to invite your to participate in a new devroom: Hardware-aided Trusted Computing. The devroom is devoted to open source projects on top of modern TEEs like Intel SGX, AMD SEV/SVE, Arm TrustZone. You can find the schedule here: https://fosdem.org/2020/schedule/track/hardware_aid

Re: [seL4] Userland components in Ring 1/2 (where kernel is in ring 0) to provide protection from less trusted components

Hello > I was wondering if it makes sense for someone building a system on seL4 to > run certain drivers or other critical components in a more privileged > environment, but still outside the kernel. Does using a different CPU mode > in this context make sense? My hunch is that the case is no, be