Ignore:
Timestamp:
Jun 17, 2013, 11:38:40 PM (11 years ago)
Author:
alain
Message:

Introducing a new global vseg : seg_boot_data, in order
to clearly separate the seg_boot_code (Read-Only) and
the seg_boot_data (Read/Write?). This is mandatory,
if the boot code is stored in a real ROM.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • soft/giet_vm/boot/boot_init.c

    r240 r245  
    8989
    9090// Page table addresses arrays
     91__attribute__((section (".wdata")))
    9192paddr_t      boot_ptabs_paddr[GIET_NB_VSPACE_MAX];
     93
     94__attribute__((section (".wdata")))
    9295unsigned int boot_ptabs_vaddr[GIET_NB_VSPACE_MAX];
    9396
    9497// Scheduler pointers array (virtual addresses)
     98__attribute__((section (".wdata")))
    9599static_scheduler_t* boot_schedulers[NB_CLUSTERS * NB_PROCS_MAX];
    96100
    97101// Next free PT2 index array
     102__attribute__((section (".wdata")))
    98103unsigned int boot_next_free_pt2[GIET_NB_VSPACE_MAX] =
    99104{ [0 ... GIET_NB_VSPACE_MAX - 1] = 0 };
    100105
    101106// Max PT2 index
     107__attribute__((section (".wdata")))
    102108unsigned int boot_max_pt2[GIET_NB_VSPACE_MAX] =
    103109{ [0 ... GIET_NB_VSPACE_MAX - 1] = 0 };
Note: See TracChangeset for help on using the changeset viewer.