Hello,
We have got now some model instances up in our local lava instance.
What I would like to find out is ‘how best to manipulate the model parameters’.
From my logs I can see
<LAVA_DISPATCHER>2013-11-06 06:27:33 PM INFO: launching fastmodel with command u'sudo -u www-data ARMLMD_LICENSE_FILE="<license-server-loc>" /fastmodels/current/FVP_Base_Cortex-A57x4-A53x4 -C bp.virtioblockdevice.image_path=/srv/lava/instances/production/var/www/lava-server/images/tmppF_EKI/sd.img
-C bp.secure_memory=0 -C bp.smsc_91c111.mac_address="02:90:00:03:00:06" -C pctl.startup=0.0.0.0 -C bp.pl011_uart0.untimed_fifos=1 -C bp.flashloader0.fname=/srv/lava/instances/production/var/www/lava-server/images/tmppF_EKI/uefi_fvp-base.bin -C bp.secureflashloader.fname=/srv/lava/instances/production/var/www/lava-server/images/tmppF_EKI/bl1.bin
-C bp.smsc_91c111.enabled=true -C bp.hostbridge.interfaceName="armv8_06" -C cache_state_modelled=0'
I can see some of these parameters defined at the above link.
Q1. Is there an easy way to have any of these parameters, for example cache_state_modelled , modified via the json file itself, which define the job?
I can see from one of Linaro’s json files has the following entry.
"command": "boot_linaro_image",
"parameters": {
"options": [
"boot_cmds=boot_cmds_oe"
]
}
Is this it correct for me to assume that this corresponds to the kernel command line arguments passed via UEFI?
- Arguments: console=ttyAMA0 earlyprintk=pl011,0x1c090000 debug user_debug=31 loglevel=9 root=/dev/vda2
Can anyone please confirm?
On a related theme, I can see the following being defined in the dispatched device_type def
simulator_dtb = fvp-base-gicv2-psci.dtb
and then this getting subsequently used in the UEFI fdt argument
- FDT: VenHw(C5B9C74A-6D72-4719-99AB-C59F199091EB)/fvp-base-gicv2-psci.dtb
Q2. Since the hardware pack do have additionally fvp-base-gicv2legacy-psci.dtb and fvp-base-gicv3-psci.dtb, how can I specify the UEFI to pick the alternate dtbs during the run? What is the easiest option?
Thanks
Basil Eljuse…