Thanks to everyone for the information.

I think the work done so far on microkit and its verification process (i.e., 
the gordian) is more in line with a lot of the Army platforms compared to the 
existing CAmkES implementations. I wanted to follow up to see if there was any 
status on the microkit x86 version ?  I need to write a proposal soon to 
specific the statement of work for building the libvmm and sDDF drivers for the 
specific x86-64 platform and would appreciate any possible timeline information 
or a best guess so I can set up a work schedule in my proposal.  Thanks so much!

Best Regards,
Peter R

-----Original Message-----
From: Peter Chubb <peter.ch...@unsw.edu.au>
Sent: Friday, June 14, 2024 3:39 PM
To: Peter Relich <prel...@intellisenseinc.com>
Cc: devel@sel4.systems
Subject: Re: [seL4] I am interested in porting LionOS to X64 architecture

CAUTION: This email originated from outside of Intellisense. Do NOT click links 
or open attachments unless you recognize the sender and know the content is 
safe.


Hi Peter,
>>>>> "Peter" == Peter Relich via Devel <devel@sel4.systems> writes:


Peter> I just started learning microkit through your available tutorials
Peter> and I am aware that building a comprehensive VMM is no easy task.
Peter> However, I was wondering if you had some intuition or if you
Peter> could provide me an estimate of the libraries in the LionOS that
Peter> I would need to adjust/redesign to make an X64 architecture fork?
Peter> Is this even a feasible approach?  It looks like I just need to
Peter> swap out the aarch64 libraries with compatible x64 libraries anvd
Peter> do some testing. Before I commit, I just wanted to get some
Peter> advice on the endeavor.

   We're currently working on getting the microkit working on X86.
   It's all out-of-public-tree work at the moment;  but expect pull
   requests soon.

   In addition to a microkit that enables hypervisor mode, you'll need
   to look at https://github.com/au-ts/libvmm and either clone and
   modify for a libvmm-x86 or adapt it to be cover more architectures.

   Likewise, the sDDF (seL4 Device Driver Framework) will be needed
   for device sharing: it's intended to be architecture independent
   except or the drivers themselves.  It's at
   https://github.com/au-ts/sddf

   Peter C
--
Dr Peter Chubb                https://trustworthy.systems/
Trustworthy Systems Group                        CSE, UNSW
Core hours: Mon 8am-3pm; Wed: 8am-5pm; Fri 8am-12pm.
________________________________
The information contained in this e-mail and any attachments from Intellisense 
Systems may contain confidential and/or proprietary information, and is 
intended only for the named recipient to whom it was originally addressed. If 
you are not the intended recipient, any disclosure, distribution, or copying of 
this e-mail or its attachments is strictly prohibited. If you have received 
this e-mail in error, please notify the sender immediately by return e-mail and 
permanently delete the e-mail and any attachments.
_______________________________________________
Devel mailing list -- devel@sel4.systems
To unsubscribe send an email to devel-leave@sel4.systems

Reply via email to