domains: switch from milliseconds to micro

Signed-off-by: Krishnan Winter <krishnan.winter@unsw.edu.au>

Author: Kswin01

docs/manual.md

@@ -1150,7 +1150,7 @@ The `domain_schedule` element, by default, has a list of up to 128 `domain` chil
 The `domain` element has the following attributes:
 
 * `name`: Name of the domain.
-* `length`: Length of time the domain will run each time it is active, in milliseconds on Aarch64 and Riscv64. On x86 this length is currently defined in ticks as we don't have a static definition of the timer frequency.
+* `length`: Length of time the domain will run each time it is active, in microseconds on Aarch64 and Riscv64. On x86 this length is currently defined in ticks as we don't have a static definition of the timer frequency.
 
 The `name` attribute of each `domain` element can be referenced in the `domain` attribute of a `protection_domain` element.
 

example/hello_domains/hello.system

@@ -6,9 +6,9 @@
 -->
 <system>
     <domain_schedule>
-        <domain name="domain_1" length="1000" />
-        <domain name="domain_2" length="1000" />
-        <domain name="domain_3" length="2000" />
+        <domain name="domain_1" length="1000000" />
+        <domain name="domain_2" length="1000000" />
+        <domain name="domain_3" length="2000000" />
     </domain_schedule>
 
     <protection_domain name="hello" domain="domain_1">
@@ -18,7 +18,7 @@
     <protection_domain name="hello_2" domain="domain_2">
         <program_image path="hello.elf" />
     </protection_domain>
-    
+
     <protection_domain name="hello_3" domain="domain_3">
         <program_image path="hello.elf" />
     </protection_domain>

tool/microkit/src/capdl/builder.rs

@@ -107,7 +107,7 @@ pub const SLOT_SIZE: u64 = 1 << SLOT_BITS;
 pub type FrameFill = Fill<ElfContent>;
 pub type CapDLNamedObject = NamedObject<FrameFill>;
 
-const MS_IN_S: u64 = 1000;
+const US_IN_S: u64 = 1000000;
 
 pub struct ExpectedAllocation {
     pub ut_idx: usize,
@@ -1127,12 +1127,12 @@ pub fn build_capdl_spec(
 
     if system.domain_schedule.is_some() {
         let mut domain_schedule: Vec<DomainSchedEntry> = Vec::new();
-        // We want to convert from the milliseconds that the user defines in the
+        // We want to convert from the microseconds that the user defines in the
         // sdf to the kernel scheduler ticks. If we are on x86, we won't necessarily
         // have a static definition of the timer frequency. We will express the
         // domain timeslices in ticks.
         let ticks_in_ms = if kernel_config.timer_freq.is_some() {
-            kernel_config.timer_freq.unwrap() / MS_IN_S
+            kernel_config.timer_freq.unwrap() / US_IN_S
         } else {
             1
         };