Dear all,

            I am trying to write configuration files for the root and the non-root cells for an arm64 based system. I have checked the video https://youtu.be/7fiJbwmhnRw and also the pdf. I could just infer from these that I have to write the config files using the already existing ones eg: amd-seatle.c and other files. But what I am not able to understand is how do I come up with the different values in the config files as in other files.

For Example:

This is small portion of amd-seattle.c how do we come up with the values in the mem_regions[] as 20, irqchips[] as 3, hypervisor_memory. phys_start = 0x83e0000000, and all othe r values in the config files. Which document has been used. Any pointer to any of the documents of the various config files listed in the configs would be a lot helpful.


#include <jailhouse/types.h>

        #include <jailhouse/cell-config.h>

        

        struct {

        struct jailhouse_system header;

        __u64 cpus[1];

        struct jailhouse_memory mem_regions[20];

        struct jailhouse_irqchip irqchips[3];

        struct jailhouse_pci_device pci_devices[3];

        } __attribute__((packed)) config = {

        .header = {

        .signature = JAILHOUSE_SYSTEM_SIGNATURE,

        .revision = JAILHOUSE_CONFIG_REVISION,

        .flags = JAILHOUSE_SYS_VIRTUAL_DEBUG_CONSOLE,

        .hypervisor_memory = {

        .phys_start = 0x83e0000000,

        .size = 0x4000000,

        },

        .debug_console = {

        .address = 0xe1010000,

        .size = 0x1000,

        .type = JAILHOUSE_CON_TYPE_PL011,

        .flags = JAILHOUSE_CON_ACCESS_MMIO |

        JAILHOUSE_CON_REGDIST_4,

        },

        

        

--
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/989156a0-b5d6-7672-a109-9860c5f94867%40cimware.in.

Reply via email to