build_image: set verity_depth default to 3

build_image: set verity_depth default to 3

This is in preparation for moving to a level 0 count of 1.

Seems to give about 200ms boot speedup.

Before(verity_depth = 1):

  seconds_power_on_to_login                                       7.73
  seconds_power_on_to_login{1}                                    7.97
  seconds_power_on_to_login{2}                                    7.8
  seconds_power_on_to_login{3}                                    7.86
  seconds_power_on_to_login{4}                                    7.84
  seconds_power_on_to_login{5}                                    7.81
  seconds_power_on_to_login{6}                                    7.85
  seconds_power_on_to_login{7}                                    7.85
  seconds_power_on_to_login{8}                                    7.85
  seconds_power_on_to_login{9}                                    7.82

After(verity_depth = 3)

  seconds_power_on_to_login                                       7.57
  seconds_power_on_to_login{1}                                    7.89
  seconds_power_on_to_login{2}                                    7.54
  seconds_power_on_to_login{3}                                    7.56
  seconds_power_on_to_login{4}                                    7.53
  seconds_power_on_to_login{5}                                    7.56
  seconds_power_on_to_login{6}                                    7.79
  seconds_power_on_to_login{7}                                    7.58
  seconds_power_on_to_login{8}                                    7.56
  seconds_power_on_to_login{9}                                    7.62

BUG=chromium-os:9752
TEST=platform_BootPerfServer

Change-Id: I7f6e39ad2ed2c2e8ebc463860578c3f97b8295a2

R=wad@chromium.org,jrbarnette@chromium.org

Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=63ca269

[Will Drewry, 2011-03-30 01:19:24]

LGTM

It's probably worth creating two images - installing the first via recovery then
generating an AU payload and upgrading it.  That should exercise all code paths
that parse/interact with the verity args.

This is exciting!
will

[Mandeep Singh Baines, 2011-03-30 01:28:58]

On 2011/03/30 01:19:24, Will Drewry wrote:
> LGTM
> 
> It's probably worth creating two images - installing the first via recovery
then
> generating an AU payload and upgrading it.  That should exercise all code
paths
> that parse/interact with the verity args.
> 

I've tested USB install and update_kernel.

Will image_to_live test the AU case?

> This is exciting!
> will

[Will Drewry, 2011-03-30 01:33:06]

On 2011/03/30 01:28:58, Mandeep Singh Baines wrote:
> On 2011/03/30 01:19:24, Will Drewry wrote:
> > LGTM
> > 
> > It's probably worth creating two images - installing the first via recovery
> then
> > generating an AU payload and upgrading it.  That should exercise all code
> paths
> > that parse/interact with the verity args.
> > 
> 
> I've tested USB install and update_kernel.

Awesome

> Will image_to_live test the AU case?

I think so!