On Tue, Dec 7, 2021 at 2:09 PM <[email protected]> wrote:
>
> Thank you very much for answering my question. I still have a doubt about the 
> TimeServer. I can manually modify the cdl file and then I get the the 
> expected source file(capdl_spec.c) from using capdl-parse. I also need to 
> change the return value of timeserver <IF>_notification API. I have try and I 
> can run the program as I expected. Is there any way to create adapted cdl 
> file automatic by modifying the ADL parse project?

There isn't a supported way to modify the generated cdl file as CAmkES
expects to generate a full system specification.

What is your motivation for trying to make the timeserver a group
component instead of a separate component? As part of a group
component it will still have its own kernel objects for its threads,
code, data and heap memories so you still have the costs of isolation
but without the benefits because it still shares the virtual address
space and capability space with other components in the same group.


> I am looking forward to getting your answer again. Thank you very much.
>
> my ADL file:
> import <std_connector.camkes>;
> import <global-connectors.camkes>;
> import <TimeServer/TimeServer.camkes>;
>
> component Client {
>     control;
>     uses Timer timeout;
> }
>
> assembly {
>     composition {
>         group grp {
>             component Client c1;
>             component Client c2;
>         }
>         component TimeServer time_server;
>
>         connection seL4TimeServer ts1(
>             from grp.c1.timeout, to time_server.the_timer);
>         connection seL4TimeServer ts2(
>             from grp.c2.timeout, to time_server.the_timer);
>     }
>
>     configuration {
>         time_server.timers_per_client = 1;
>     }
> }
> _______________________________________________
> Devel mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
_______________________________________________
Devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to