All of lore.kernel.org
 help / color / mirror / Atom feed
From: Platform Team regression test user <citrix-osstest@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [ovmf baseline-only test] 74657: all pass
Date: Wed, 2 May 2018 08:45:05 +0100	[thread overview]
Message-ID: <osstest-74657-mainreport@xen.org> (raw)

This run is configured for baseline tests only.

flight 74657 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74657/

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 f9dff90289507191f299331e44601c5ef83c1948
baseline version:
 ovmf                 78e759910c8d3627f8ba6a0412b85f0868c1b203

Last test of basis    74648  2018-04-29 13:51:41 Z    2 days
Testing same since    74657  2018-05-01 21:23:41 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Laszlo Ersek <lersek@redhat.com>

jobs:
 build-amd64-xsm                                              pass    
 build-i386-xsm                                               pass    
 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-i386-libvirt                                           pass    
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         pass    
 test-amd64-i386-xl-qemuu-ovmf-amd64                          pass    


------------------------------------------------------------
sg-report-flight on osstest.xs.citrite.net
logs: /home/osstest/logs
images: /home/osstest/images

Logs, config files, etc. are available at
    http://osstest.xs.citrite.net/~osstest/testlogs/logs

Test harness code can be found at
    http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary


Push not applicable.

------------------------------------------------------------
commit f9dff90289507191f299331e44601c5ef83c1948
Author: Laszlo Ersek <lersek@redhat.com>
Date:   Tue Apr 24 01:36:27 2018 +0200

    ArmVirtPkg: use protocol-based DevicePathLib instance for most DXE modules
    
    Port OvmfPkg commit 5c3481b0b611e to ArmVirtPkg. Some explanation should
    be in order (because 5c3481b0b611e doesn't offer any):
    
    - The UefiDevicePathLibDevicePathProtocol instance uses the Device Path
      Utilities Protocol, produced by DevicePathDxe, for formatting and
      parsing the textual device path representation. This allows for a
      lighter weight lib instance that gets linked into several DXE modules.
      In comparison, the more standalone UefiDevicePathLib instance includes
      the formatting and parsing routines in every client module.
    
    - The DXE core needs DevicePathLib before it dispatches DevicePathDxe, so
      it needs to stick with the standalone instance.
    
    - DevicePathDxe itself also needs the standalone instance, for
      implementing the protocol.
    
    - The DXE-phase PCD driver, "MdeModulePkg/Universal/PCD/Dxe/Pcd.inf",
      depends on DevicePathLib via UefiLib and DxeServicesLib at the least; so
      with this update, it inherits a dependency on the protocol. In reverse,
      DevicePathDxe depends on the PCD Protocol, via PcdLib. The cycle is
      broken by using BasePcdLibNull in DevicePathDxe. That restricts it to
      FixedAtBuild, Patch, and FeatureFlag PCDs, but that's fine.
    
    Example space savings (using ArmVirtQemu and the GCC5 toolchain):
    - NOOPT:   187KB in FVMAIN, 12KB in FVMAIN_COMPACT
    - DEBUG:   147KB in FVMAIN, 20KB in FVMAIN_COMPACT
    - RELEASE: 123KB in FVMAIN, 17KB in FVMAIN_COMPACT
    
    Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
    Cc: Julien Grall <julien.grall@linaro.org>
    Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=940
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Laszlo Ersek <lersek@redhat.com>
    Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

                 reply	other threads:[~2018-05-02  7:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=osstest-74657-mainreport@xen.org \
    --to=citrix-osstest@xenproject.org \
    --cc=osstest-admin@xenproject.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.