Access flag fault?

[pittma]

In an aarch64 build, the child processes don't seem to be able to use their VSpaces. The access for the pc faults before the process even starts, and it also cannot dump its stack:

vm fault on code at address 0x44ae98 with status 0x82000006
in thread 0xff800fff2c00 "child of: 'rootserver'" at address 0x44ae98
With stack:
0x312000: INVALID
0x312008: INVALID
0x312010: INVALID
0x312018: INVALID
0x312020: INVALID
0x312028: INVALID
0x312030: INVALID
0x312038: INVALID
0x312040: INVALID
0x312048: INVALID
0x312050: INVALID
0x312058: INVALID
0x312060: INVALID
0x312068: INVALID
0x312070: INVALID
0x312078: INVALID

My best effort at translating what that status means (0x82000006) I gather from some arm documentation on the instruction fault status register:

b000110 access flag fault, page

This leads me to wonder if there are some broken details w/r/t rights? flags? settings for paging mapping when using aarch64.

Here's some information on the meaning of access flags: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0211k/Caceaije.html

However, I'm unsure what or how those tie into the use of CapRight in seL4.

[pittma]

our ProgramStart constant wasn't relevant for aarch64. ff94484 fixes that; now we're bombing likely on the stack and reg setup. I'm working on rewriting that now.