Thanks a lot Tyler,

Cool that is precisely what I was looking for. Will give a try.

I am hoping that I can specify both fast models parameters and having 
interactive boot args specified together in a job. Will give it a go and let 
you know.

Thanks
Basil Eljuse...

From: Tyler Baker [mailto:tyler.ba...@linaro.org]
Sent: 06 November 2013 20:46
To: Basil Eljuse
Cc: Linaro Validation
Subject: Re: [Linaro-validation] What is the best way to configure fast model 
parameters...

Hi Basil,

On 6 November 2013 12:28, Basil Eljuse 
<basil.elj...@arm.com<mailto:basil.elj...@arm.com>> wrote:
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'

Also from 
http://git.linaro.org/gitweb?p=lava/lava-dispatcher.git;a=blob;f=lava_dispatcher/default-config/lava-dispatcher/device-types/rtsm_fvp_base_cortex-a57x4-a53x4.conf;h=69d37721856e6428fbcfbc1b575463285078229f;hb=HEAD

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"
                ]
            }


You can modify any of the parameters in the boot_options stanza. Here is an 
example I have created showing how to use set the cache_modeled_state:

http://community.validation.linaro.org/scheduler/job/2637/definition

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?

The kernel arguments are hard coded into the UEFI configuration. You can 
override these values with interactive boot commands. Here is an example of 
this on an older model:

http://community.validation.linaro.org/scheduler/job/1552/definition

The new models have slightly different menu options so you will have to modify 
the send / expect logic to handle these differences.





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?

Again this binary name is hard coded in the UEFI configuration. You will have 
to use interactive boot commands to override these values.


Thanks
Basil Eljuse...

-- IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.

ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered 
in England & Wales, Company No: 2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, 
Registered in England & Wales, Company No: 2548782

_______________________________________________
linaro-validation mailing list
linaro-validation@lists.linaro.org<mailto:linaro-validation@lists.linaro.org>
http://lists.linaro.org/mailman/listinfo/linaro-validation

Hope that helps!


--
Tyler Baker
Technical Architect, LAVA
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

-- IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.

ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered 
in England & Wales, Company No: 2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, 
Registered in England & Wales, Company No: 2548782
_______________________________________________
linaro-validation mailing list
linaro-validation@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-validation

Reply via email to