[xen-unstable-smoke test] 169361: regressions - FAIL

[osstest service owner <osstest-admin@xxxxxxxxxxxxxx>]

flight 169361 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/169361/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-arm64-xsm               6 xen-build                fail REGR. vs. 169320

Tests which did not succeed, but are not blocking:
 test-arm64-arm64-xl-xsm       1 build-check(1)               blocked  n/a
 test-amd64-amd64-libvirt     15 migrate-support-check        fail   never pass
 test-armhf-armhf-xl          15 migrate-support-check        fail   never pass
 test-armhf-armhf-xl          16 saverestore-support-check    fail   never pass

version targeted for testing:
 xen                  e509b5f932608e74deac96048b28a5e9b210c647
baseline version:
 xen                  5b752808ff37b7c819a26fd76329ef329c42774f

Last test of basis   169320  2022-04-12 02:00:26 Z    1 days
Testing same since   169361  2022-04-13 11:01:35 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Anthony PERARD <anthony.perard@xxxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxx>
  Julien Grall <jgrall@xxxxxxxxxx>
  Ross Lagerwall <ross.lagerwall@xxxxxxxxxx> # livepatch

jobs:
 build-arm64-xsm                                              fail    
 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-amd64-libvirt                                          pass    
 test-armhf-armhf-xl                                          pass    
 test-arm64-arm64-xl-xsm                                      blocked 
 test-amd64-amd64-xl-qemuu-debianhvm-amd64                    pass    
 test-amd64-amd64-libvirt                                     pass    


------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images

Logs, config files, etc. are available at
    http://logs.test-lab.xenproject.org/osstest/logs

Explanation of these reports, and of osstest in general, is at
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master

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


Not pushing.

------------------------------------------------------------
commit e509b5f932608e74deac96048b28a5e9b210c647
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Wed Apr 13 12:36:03 2022 +0200

    IOMMU: log appropriate SBDF
    
    To handle phantom devices, several functions are passed separate "devfn"
    arguments besides a PCI device. In such cases we want to log the phantom
    device's coordinates instead of the main one's. (Note that not all of
    the instances being changed are fallout from the referenced commit.)
    
    Fixes: 1ee1441835f4 ("print: introduce a format specifier for pci_sbdf_t")
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>

commit e687e72174b73bb1d23ff79f9ef580201243d35f
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Wed Apr 13 12:35:17 2022 +0200

    AMD/IOMMU: replace a few PCI_BDF2()
    
    struct pci_dev has the wanted value directly available; use it. Note
    that this fixes a - imo benign - mistake in reassign_device(): The unity
    map removal ought to be based on the passed in devfn (as is the case on
    the establishing side). This is benign because the mappings would be
    removed anyway a little later, when the "main" device gets processed.
    While there also limit the scope of two variables in that function.
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>

commit 7115fa562fe79c8a8733f6b821d4eea62ed56516
Author: Anthony PERARD <anthony.perard@xxxxxxxxxx>
Date:   Wed Apr 13 12:33:21 2022 +0200

    build: adding out-of-tree support to the xen build
    
    This implement out-of-tree support, there's two ways to create an
    out-of-tree build tree (after that, `make` in that new directory
    works):
        make O=build
        mkdir build; cd build; make -f ../Makefile
    also works with an absolute path for both.
    
    This implementation only works if the source tree is clean, as we use
    VPATH.
    
    This patch copies most new code with handling out-of-tree build from
    Linux v5.12.
    
    Signed-off-by: Anthony PERARD <anthony.perard@xxxxxxxxxx>
    Acked-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Daniel P. Smith <dpsmith@xxxxxxxxxxxxxxxxxxxx>
    Acked-by: Julien Grall <jgrall@xxxxxxxxxx>
    Tested-by: Julien Grall <jgrall@xxxxxxxxxx>
    Acked-by: Ross Lagerwall <ross.lagerwall@xxxxxxxxxx> # livepatch
(qemu changes not included)