Hi Basil,

On 6 November 2013 13:20, Basil Eljuse Basil.Eljuse@arm.com wrote:

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.

I have never tried both at the same time. If it does not work for you, let me know I can come up with a fix. :)

Cheers,

Thanks

Basil Eljuse…

*From:* Tyler Baker [mailto:tyler.baker@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.Eljuse@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%3Ba=blob%3Bf=lava_di...

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 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/#%21/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

Hi Basil,

This is a bug. I've reported it here: https://bugs.launchpad.net/lava-dispatcher/+bug/1248969 and will be working on a fix today.

On 6 November 2013 17:07, Basil Eljuse Basil.Eljuse@arm.com wrote:

Hi Tyler,

It works when used independently. But if used together it does not work.

The following is my json fragment

    {

        "command": "boot_linaro_image",

        "parameters": {

            "interactive_boot_cmds": true,

            "options": [

                "cache_state_modelled=1",

                "sendline a",

                "expect Choice:",

                "sendline 1",

                "expect Select the Boot Device:",

                "sendline 1",

                "expect File path of the EFI Application or the

kernel:",

                "sendline Image",

                "expect Boot Type: [a] ATAGS, [g] Global FDT or [l]

Local FDT? [a/g/l]",

                "sendline l",

                "expect Add an initrd: [y/n]",

                "sendline n",

                "expect Arguments to pass to the binary:",

                "sendline console=ttyAMA0 earlyprintk=pl011,0x1c090000

debug user_debug=31 loglevel=9 root=/dev/vda2",

                "expect File path of the local FDT:",

                "sendline  fvp-base-gicv3-psci.dtb",

                "expect Description for this new Entry:",

                "sendline Linaro disk image on virtio gicv3 fdt",

                "expect Choice:",

                "sendline 5",

                "expect Start:",

                "sendline 2"

            ]

        }

    },

Here the cache_state_modelled parameter is getting mistaken for uefi interactive option!

Thanks

Basil Eljuse…

*From:* Tyler Baker [mailto:tyler.baker@linaro.org] *Sent:* 06 November 2013 23:57 *To:* Basil Eljuse *Cc:* Linaro Validation; Dean Arnold

*Subject:* Re: [Linaro-validation] What is the best way to configure fast model parameters...

Hi Basil,

On 6 November 2013 13:20, Basil Eljuse Basil.Eljuse@arm.com wrote:

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.

I have never tried both at the same time. If it does not work for you, let me know I can come up with a fix. :)

Cheers,

Thanks

Basil Eljuse…

*From:* Tyler Baker [mailto:tyler.baker@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.Eljuse@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%3Ba=blob%3Bf=lava_di...

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 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/#%21/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

--

Tyler Baker Technical Architect, LAVA Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/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

Hi Tyler,

We got our setup upgraded yesterday when Dave / Matt and Esla visited us onsite.

I re-tried this json fragment again, however I get the following json validation error.

ValidationError: Object has unknown property u'interactive_boot_cmds' but additional properties are disallowed object_expr='object', schema_expr='schema.additionalProperties')

The fragment I am trying is

{ "command": "boot_linaro_image", "parameters": { "interactive_boot_cmds": true, "options": [ "cache_state_modelled=1", "bp.secureflashloader.fname=/test-binaries/CI-job-binaries-cortex1x1/bl1.bin", "cluster0.cpu0.semihosting-cwd=/test-binaries/CI-job-binaries-cortex1x1/", "bp.flashloader0.fname=/test-binaries/CI-job-binaries-cortex1x1/uefi_fvp-base.bin", "sendline a", "expect Choice:", "sendline 1", "expect Select the Boot Device:", "sendline 1", "expect File path of the EFI Application or the kernel:", "sendline Image", "expect Boot Type: [a] ATAGS, [g] Global FDT or [l] Local FDT? [a/g/l]", "sendline l", "expect Add an initrd: [y/n]", "sendline n", "expect Arguments to pass to the binary:", "sendline console=ttyAMA0 earlyprintk=pl011,0x1c090000 debug user_debug=31 loglevel=9 root=/dev/vda2", "expect File path of the local FDT:", "sendline fvp-base-gicv3-psci.dtb", "expect Description for this new Entry:", "sendline Linaro disk image on virtio gicv3 fdt", "expect Choice:", "sendline 5", "expect Start:", "sendline 2" ] } },

Do note, that I want to both specify the uefi interactive boot arguments plus the boot options for the fast model together!

If I comment out the "interactive_boot_cmds":true Then json stops complaining however the job applies on the fast models boot options and treats all uefi interactive boot commands as invalid boot options

<LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline a <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect Choice: <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline 1 <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect Select the Boot Device: <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline 1 <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect File path of the EFI Application or the kernel: <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline Image <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect Boot Type: [a] ATAGS, [g] Global FDT or [l] Local FDT? [a/g/l] <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline l <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect Add an initrd: [y/n] <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline n <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect Arguments to pass to the binary: <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline console=ttyAMA0 earlyprintk=pl011,0x1c090000 debug user_debug=31 loglevel=9 root=/dev/vda2 <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect File path of the local FDT: <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline fvp-base-gicv3-psci.dtb <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect Description for this new Entry: <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline Linaro disk image on virtio gicv3 fdt <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect Choice: <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline 5 <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect Start: <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline 2 <LAVA_DISPATCHER>2014-01-31 09:35:10 AM INFO: launching fastmodel with command u'sudo -u www-data ARMLMD_LICENSE_FILE="7010@euhpc-lic03.euhpc.arm.com:7010@euhpc-lic04.euhpc.arm.com:7010@euhpc-lic05.euhpc.arm.com:7010@euhpc-lic07.euhpc.arm.com" /fastmodels/current/FVP_Base_Cortex-A57x1-A53x1 -C bp.virtioblockdevice.image_path=/srv/lava/instances/production/var/www/lava-server/images/tmpWknzmy/sd.img -C cluster0.cpu0.semihosting-cwd=/test-binaries/CI-job-binaries-cortex1x1/ -C bp.secure_memory=0 -C bp.smsc_91c111.mac_address="02:90:00:03:00:03" -C pctl.startup=0.0.0.0 -C bp.pl011_uart0.untimed_fifos=1 -C bp.flashloader0.fname=/test-binaries/CI-job-binaries-cortex1x1/uefi_fvp-base.bin -C bp.secureflashloader.fname=/test-binaries/CI-job-binaries-cortex1x1/bl1.bin -C bp.smsc_91c111.enabled=true -C bp.hostbridge.interfaceName="armv8_05" -C cache_state_modelled=1'

Thanks Basil Eljuse...

From: Tyler Baker [mailto:tyler.baker@linaro.org] Sent: 07 November 2013 14:44 To: Basil Eljuse Cc: Linaro Validation; Dean Arnold Subject: Re: [Linaro-validation] What is the best way to configure fast model parameters...

Hi Basil,

This is a bug. I've reported it here: https://bugs.launchpad.net/lava-dispatcher/+bug/1248969 and will be working on a fix today.

On 6 November 2013 17:07, Basil Eljuse <Basil.Eljuse@arm.commailto:Basil.Eljuse@arm.com> wrote: Hi Tyler,

It works when used independently. But if used together it does not work.

The following is my json fragment

{ "command": "boot_linaro_image", "parameters": { "interactive_boot_cmds": true, "options": [ "cache_state_modelled=1", "sendline a", "expect Choice:", "sendline 1", "expect Select the Boot Device:", "sendline 1", "expect File path of the EFI Application or the kernel:", "sendline Image", "expect Boot Type: [a] ATAGS, [g] Global FDT or [l] Local FDT? [a/g/l]", "sendline l", "expect Add an initrd: [y/n]", "sendline n", "expect Arguments to pass to the binary:", "sendline console=ttyAMA0 earlyprintk=pl011,0x1c090000 debug user_debug=31 loglevel=9 root=/dev/vda2", "expect File path of the local FDT:", "sendline fvp-base-gicv3-psci.dtb", "expect Description for this new Entry:", "sendline Linaro disk image on virtio gicv3 fdt", "expect Choice:", "sendline 5", "expect Start:", "sendline 2" ] } },

Here the cache_state_modelled parameter is getting mistaken for uefi interactive option!

Thanks Basil Eljuse...

From: Tyler Baker [mailto:tyler.baker@linaro.orgmailto:tyler.baker@linaro.org] Sent: 06 November 2013 23:57 To: Basil Eljuse Cc: Linaro Validation; Dean Arnold

Subject: Re: [Linaro-validation] What is the best way to configure fast model parameters...

Hi Basil,

On 6 November 2013 13:20, Basil Eljuse <Basil.Eljuse@arm.commailto:Basil.Eljuse@arm.com> wrote: 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.

I have never tried both at the same time. If it does not work for you, let me know I can come up with a fix. :)

Cheers,

Thanks Basil Eljuse...

From: Tyler Baker [mailto:tyler.baker@linaro.orgmailto:tyler.baker@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.Eljuse@arm.commailto:Basil.Eljuse@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%3Ba=blob%3Bf=lava_di...

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.orgmailto: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/#%21/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

-- Tyler Baker Technical Architect, LAVA Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/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

-- Tyler Baker Technical Architect, LAVA Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/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

To confirm,

This below fragment worked perfectly.

{ "command": "boot_linaro_image", "parameters": { "boot_cmds": [ "sendline a", "expect Choice:", "sendline 1", "expect Select the Boot Device:", "sendline 1", "expect File path of the EFI Application or the kernel:", "sendline Image", "expect Boot Type: [a] ATAGS, [g] Global FDT or [l] Local FDT? [a/g/l]", "sendline l", "expect Add an initrd: [y/n]", "sendline n", "expect Arguments to pass to the binary:", "sendline console=ttyAMA0 earlyprintk=pl011,0x1c090000 debug user_debug=31 loglevel=9 root=/dev/vda2", "expect File path of the local FDT:", "sendline fvp-base-gicv3-psci.dtb", "expect Description for this new Entry:", "sendline Linaro disk image on virtio gicv3 fdt", "expect Choice:", "sendline 5", "expect Start:", "sendline 2" ], "options": [ "cache_state_modelled=1", "bp.secureflashloader.fname=/test-binaries/CI-job-binaries-cortex1x1/bl1.bin", "cluster0.cpu0.semihosting-cwd=/test-binaries/CI-job-binaries-cortex1x1/", "bp.flashloader0.fname=/test-binaries/CI-job-binaries-cortex1x1/uefi_fvp-base.bin" ] }

I could see the correct model arguments overridden and the new boot device created and booted from it.

Only there was a kernel panic, but that is a DUT issue not LAVA related (:

Thanks a lot for enabling this cool feature.

Thanks Basil Eljuse...

From: Basil Eljuse Sent: 31 January 2014 09:54 To: Basil Eljuse; 'Tyler Baker' Cc: 'Linaro Validation'; Dean Arnold Subject: RE: [Linaro-validation] What is the best way to configure fast model parameters...

Sorry, just now saw Tyler's example usage after the fix in a subsequent thread.

{ "command": "boot_linaro_image", "parameters": { "boot_cmds": [ "1" ], "options": [ "cache_state_modelled=1" ] } } Will try and let you know (:

I keep jumping the gun ):

Thanks Basil Eljuse...

From: Basil Eljuse Sent: 31 January 2014 09:50 To: 'Tyler Baker' Cc: Linaro Validation; Dean Arnold Subject: RE: [Linaro-validation] What is the best way to configure fast model parameters...

Hi Tyler,

We got our setup upgraded yesterday when Dave / Matt and Esla visited us onsite.

I re-tried this json fragment again, however I get the following json validation error.

ValidationError: Object has unknown property u'interactive_boot_cmds' but additional properties are disallowed object_expr='object', schema_expr='schema.additionalProperties')

The fragment I am trying is

{ "command": "boot_linaro_image", "parameters": { "interactive_boot_cmds": true, "options": [ "cache_state_modelled=1", "bp.secureflashloader.fname=/test-binaries/CI-job-binaries-cortex1x1/bl1.bin", "cluster0.cpu0.semihosting-cwd=/test-binaries/CI-job-binaries-cortex1x1/", "bp.flashloader0.fname=/test-binaries/CI-job-binaries-cortex1x1/uefi_fvp-base.bin", "sendline a", "expect Choice:", "sendline 1", "expect Select the Boot Device:", "sendline 1", "expect File path of the EFI Application or the kernel:", "sendline Image", "expect Boot Type: [a] ATAGS, [g] Global FDT or [l] Local FDT? [a/g/l]", "sendline l", "expect Add an initrd: [y/n]", "sendline n", "expect Arguments to pass to the binary:", "sendline console=ttyAMA0 earlyprintk=pl011,0x1c090000 debug user_debug=31 loglevel=9 root=/dev/vda2", "expect File path of the local FDT:", "sendline fvp-base-gicv3-psci.dtb", "expect Description for this new Entry:", "sendline Linaro disk image on virtio gicv3 fdt", "expect Choice:", "sendline 5", "expect Start:", "sendline 2" ] } },

Do note, that I want to both specify the uefi interactive boot arguments plus the boot options for the fast model together!

If I comment out the "interactive_boot_cmds":true Then json stops complaining however the job applies on the fast models boot options and treats all uefi interactive boot commands as invalid boot options

<LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline a <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect Choice: <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline 1 <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect Select the Boot Device: <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline 1 <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect File path of the EFI Application or the kernel: <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline Image <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect Boot Type: [a] ATAGS, [g] Global FDT or [l] Local FDT? [a/g/l] <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline l <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect Add an initrd: [y/n] <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline n <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect Arguments to pass to the binary: <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline console=ttyAMA0 earlyprintk=pl011,0x1c090000 debug user_debug=31 loglevel=9 root=/dev/vda2 <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect File path of the local FDT: <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline fvp-base-gicv3-psci.dtb <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect Description for this new Entry: <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline Linaro disk image on virtio gicv3 fdt <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect Choice: <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline 5 <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: expect Start: <LAVA_DISPATCHER>2014-01-31 09:35:10 AM WARNING: Invalid boot option format: sendline 2 <LAVA_DISPATCHER>2014-01-31 09:35:10 AM INFO: launching fastmodel with command u'sudo -u www-data ARMLMD_LICENSE_FILE="7010@euhpc-lic03.euhpc.arm.com:7010@euhpc-lic04.euhpc.arm.com:7010@euhpc-lic05.euhpc.arm.com:7010@euhpc-lic07.euhpc.arm.commailto:7010@euhpc-lic03.euhpc.arm.com:7010@euhpc-lic04.euhpc.arm.com:7010@euhpc-lic05.euhpc.arm.com:7010@euhpc-lic07.euhpc.arm.com" /fastmodels/current/FVP_Base_Cortex-A57x1-A53x1 -C bp.virtioblockdevice.image_path=/srv/lava/instances/production/var/www/lava-server/images/tmpWknzmy/sd.img -C cluster0.cpu0.semihosting-cwd=/test-binaries/CI-job-binaries-cortex1x1/ -C bp.secure_memory=0 -C bp.smsc_91c111.mac_address="02:90:00:03:00:03" -C pctl.startup=0.0.0.0 -C bp.pl011_uart0.untimed_fifos=1 -C bp.flashloader0.fname=/test-binaries/CI-job-binaries-cortex1x1/uefi_fvp-base.bin -C bp.secureflashloader.fname=/test-binaries/CI-job-binaries-cortex1x1/bl1.bin -C bp.smsc_91c111.enabled=true -C bp.hostbridge.interfaceName="armv8_05" -C cache_state_modelled=1'

Thanks Basil Eljuse...

From: Tyler Baker [mailto:tyler.baker@linaro.org] Sent: 07 November 2013 14:44 To: Basil Eljuse Cc: Linaro Validation; Dean Arnold Subject: Re: [Linaro-validation] What is the best way to configure fast model parameters...

Hi Basil,

This is a bug. I've reported it here: https://bugs.launchpad.net/lava-dispatcher/+bug/1248969 and will be working on a fix today.

On 6 November 2013 17:07, Basil Eljuse <Basil.Eljuse@arm.commailto:Basil.Eljuse@arm.com> wrote: Hi Tyler,

It works when used independently. But if used together it does not work.

The following is my json fragment

{ "command": "boot_linaro_image", "parameters": { "interactive_boot_cmds": true, "options": [ "cache_state_modelled=1", "sendline a", "expect Choice:", "sendline 1", "expect Select the Boot Device:", "sendline 1", "expect File path of the EFI Application or the kernel:", "sendline Image", "expect Boot Type: [a] ATAGS, [g] Global FDT or [l] Local FDT? [a/g/l]", "sendline l", "expect Add an initrd: [y/n]", "sendline n", "expect Arguments to pass to the binary:", "sendline console=ttyAMA0 earlyprintk=pl011,0x1c090000 debug user_debug=31 loglevel=9 root=/dev/vda2", "expect File path of the local FDT:", "sendline fvp-base-gicv3-psci.dtb", "expect Description for this new Entry:", "sendline Linaro disk image on virtio gicv3 fdt", "expect Choice:", "sendline 5", "expect Start:", "sendline 2" ] } },

Here the cache_state_modelled parameter is getting mistaken for uefi interactive option!

Thanks Basil Eljuse...

From: Tyler Baker [mailto:tyler.baker@linaro.orgmailto:tyler.baker@linaro.org] Sent: 06 November 2013 23:57 To: Basil Eljuse Cc: Linaro Validation; Dean Arnold

Subject: Re: [Linaro-validation] What is the best way to configure fast model parameters...

Hi Basil,

On 6 November 2013 13:20, Basil Eljuse <Basil.Eljuse@arm.commailto:Basil.Eljuse@arm.com> wrote: 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.

I have never tried both at the same time. If it does not work for you, let me know I can come up with a fix. :)

Cheers,

Thanks Basil Eljuse...

From: Tyler Baker [mailto:tyler.baker@linaro.orgmailto:tyler.baker@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.Eljuse@arm.commailto:Basil.Eljuse@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%3Ba=blob%3Bf=lava_di...

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.orgmailto: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/#%21/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

-- Tyler Baker Technical Architect, LAVA Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/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

-- Tyler Baker Technical Architect, LAVA Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/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