|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [xen-unstable test] 133390: regressions - trouble: broken/fail/pass
flight 133390 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/133390/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-freebsd10-i386 <job status> broken test-amd64-i386-xl-qemut-debianhvm-amd64 <job status> broken test-armhf-armhf-xl-credit1 <job status> broken test-amd64-i386-xl <job status> broken test-amd64-amd64-xl-qemuu-debianhvm-amd64 <job status> broken test-amd64-amd64-xl-qemut-win10-i386 <job status> broken test-amd64-i386-rumprun-i386 <job status> broken test-amd64-amd64-rumprun-amd64 <job status> broken test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm <job status> broken test-amd64-amd64-xl-credit2 <job status> broken test-amd64-i386-qemuu-rhel6hvm-intel <job status> broken test-amd64-amd64-xl-qemut-debianhvm-amd64 <job status> broken test-amd64-i386-xl-qemut-ws16-amd64 <job status> broken test-amd64-i386-qemuu-rhel6hvm-intel 4 host-install(4) broken REGR. vs. 133300 test-amd64-i386-rumprun-i386 4 host-install(4) broken REGR. vs. 133300 test-amd64-amd64-rumprun-amd64 4 host-install(4) broken REGR. vs. 133300 test-amd64-amd64-xl-qemut-win10-i386 4 host-install(4) broken REGR. vs. 133300 test-amd64-i386-xl-qemut-ws16-amd64 4 host-install(4) broken REGR. vs. 133300 test-amd64-amd64-xl-qemut-debianhvm-amd64 4 host-install(4) broken REGR. vs. 133300 test-amd64-i386-xl-qemut-debianhvm-amd64 4 host-install(4) broken REGR. vs. 133300 test-amd64-amd64-xl-credit2 4 host-install(4) broken REGR. vs. 133300 test-amd64-amd64-xl-qemuu-debianhvm-amd64 4 host-install(4) broken REGR. vs. 133300 test-amd64-i386-freebsd10-i386 4 host-install(4) broken REGR. vs. 133300 test-amd64-i386-xl 4 host-install(4) broken REGR. vs. 133300 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 4 host-install(4) broken REGR. vs. 133300 test-armhf-armhf-xl-credit1 4 host-install(4) broken REGR. vs. 133300 test-armhf-armhf-xl-arndale 7 xen-boot fail REGR. vs. 133300 test-amd64-i386-xl-qemuu-debianhvm-amd64 10 debian-hvm-install fail REGR. vs. 133300 test-amd64-amd64-qemuu-nested-intel 10 debian-hvm-install fail REGR. vs. 133300 test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 10 debian-hvm-install fail REGR. vs. 133300 test-amd64-amd64-qemuu-nested-amd 10 debian-hvm-install fail REGR. vs. 133300 test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm 10 debian-hvm-install fail REGR. vs. 133300 test-amd64-i386-xl-qemuu-dmrestrict-amd64-dmrestrict 10 debian-hvm-install fail REGR. vs. 133300 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 debian-hvm-install fail REGR. vs. 133300 test-amd64-amd64-i386-pvgrub 10 debian-di-install fail REGR. vs. 133300 test-amd64-amd64-xl-qcow2 10 debian-di-install fail REGR. vs. 133300 test-amd64-amd64-libvirt-vhd 10 debian-di-install fail REGR. vs. 133300 test-amd64-i386-xl-qemut-debianhvm-amd64-xsm 10 debian-hvm-install fail REGR. vs. 133300 test-amd64-i386-xl-raw 10 debian-di-install fail REGR. vs. 133300 test-armhf-armhf-xl-vhd 10 debian-di-install fail REGR. vs. 133300 Tests which did not succeed, but are not blocking: test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop fail like 133282 test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail like 133300 test-amd64-i386-xl-qemut-win7-amd64 17 guest-stop fail like 133300 test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail like 133300 test-armhf-armhf-libvirt 14 saverestore-support-check fail like 133300 test-amd64-amd64-xl-qemut-ws16-amd64 17 guest-stop fail like 133300 test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stop fail like 133300 test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stop fail like 133300 test-armhf-armhf-libvirt-raw 13 saverestore-support-check fail like 133300 test-amd64-i386-libvirt-xsm 13 migrate-support-check fail never pass test-amd64-i386-xl-pvshim 12 guest-start fail never pass test-arm64-arm64-xl-credit1 13 migrate-support-check fail never pass test-arm64-arm64-xl-credit1 14 saverestore-support-check fail never pass test-arm64-arm64-xl 13 migrate-support-check fail never pass test-arm64-arm64-xl 14 saverestore-support-check fail never pass test-arm64-arm64-xl-credit2 13 migrate-support-check fail never pass test-arm64-arm64-xl-credit2 14 saverestore-support-check fail never pass test-arm64-arm64-libvirt-xsm 13 migrate-support-check fail never pass test-arm64-arm64-libvirt-xsm 14 saverestore-support-check fail never pass test-arm64-arm64-xl-xsm 13 migrate-support-check fail never pass test-arm64-arm64-xl-xsm 14 saverestore-support-check fail never pass test-amd64-amd64-libvirt 13 migrate-support-check fail never pass test-amd64-amd64-libvirt-xsm 13 migrate-support-check fail never pass test-armhf-armhf-xl-rtds 13 migrate-support-check fail never pass test-armhf-armhf-xl-rtds 14 saverestore-support-check fail never pass test-armhf-armhf-xl-cubietruck 13 migrate-support-check fail never pass test-armhf-armhf-xl-cubietruck 14 saverestore-support-check fail never pass test-amd64-i386-libvirt 13 migrate-support-check fail never pass test-armhf-armhf-libvirt 13 migrate-support-check fail never pass test-armhf-armhf-libvirt-raw 12 migrate-support-check fail never pass test-amd64-amd64-xl-qemuu-win10-i386 10 windows-install fail never pass test-amd64-i386-xl-qemuu-win10-i386 10 windows-install fail never pass test-amd64-i386-xl-qemut-win10-i386 10 windows-install fail never pass test-armhf-armhf-xl-multivcpu 13 migrate-support-check fail never pass test-armhf-armhf-xl-multivcpu 14 saverestore-support-check fail never pass test-armhf-armhf-xl-credit2 13 migrate-support-check fail never pass test-armhf-armhf-xl-credit2 14 saverestore-support-check fail never pass test-armhf-armhf-xl 13 migrate-support-check fail never pass test-armhf-armhf-xl 14 saverestore-support-check fail never pass version targeted for testing: xen e72ecc7615410e5bf1a1c9a4c7772322c16eeb82 baseline version: xen 365aabb6e5023cee476adf81106729efd49c644f Last test of basis 133300 2019-02-18 10:44:15 Z 6 days Failing since 133316 2019-02-19 22:18:02 Z 5 days 3 attempts Testing same since 133390 2019-02-23 06:56:39 Z 1 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> George Dunlap <george.dunlap@xxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> Roger Pau Monne <roger.pau@xxxxxxxxxx> Roger Pau Monné <roger.pau@xxxxxxxxxx> Varad Gautam <vrd@xxxxxxxxx> Wei Liu <wei.liu2@xxxxxxxxxx> jobs: build-amd64-xsm pass build-arm64-xsm pass build-i386-xsm pass build-amd64-xtf pass build-amd64 pass build-arm64 pass build-armhf pass build-i386 pass build-amd64-libvirt pass build-arm64-libvirt pass build-armhf-libvirt pass build-i386-libvirt pass build-amd64-prev pass build-i386-prev pass build-amd64-pvops pass build-arm64-pvops pass build-armhf-pvops pass build-i386-pvops pass build-amd64-rumprun pass build-i386-rumprun pass test-xtf-amd64-amd64-1 pass test-xtf-amd64-amd64-2 pass test-xtf-amd64-amd64-3 pass test-xtf-amd64-amd64-4 pass test-xtf-amd64-amd64-5 pass test-amd64-amd64-xl pass test-arm64-arm64-xl pass test-armhf-armhf-xl pass test-amd64-i386-xl broken test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm fail test-amd64-i386-xl-qemut-debianhvm-amd64-xsm fail test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm fail test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm broken test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm pass test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm pass test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm fail test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm pass test-amd64-amd64-libvirt-xsm pass test-arm64-arm64-libvirt-xsm pass test-amd64-i386-libvirt-xsm pass test-amd64-amd64-xl-xsm pass test-arm64-arm64-xl-xsm pass test-amd64-i386-xl-xsm pass test-amd64-amd64-qemuu-nested-amd fail test-amd64-amd64-xl-pvhv2-amd pass test-amd64-i386-qemut-rhel6hvm-amd pass test-amd64-i386-qemuu-rhel6hvm-amd pass test-amd64-amd64-xl-qemut-debianhvm-amd64 broken test-amd64-i386-xl-qemut-debianhvm-amd64 broken test-amd64-amd64-xl-qemuu-debianhvm-amd64 broken test-amd64-i386-xl-qemuu-debianhvm-amd64 fail test-amd64-i386-freebsd10-amd64 pass test-amd64-amd64-xl-qemuu-ovmf-amd64 pass test-amd64-i386-xl-qemuu-ovmf-amd64 pass test-amd64-amd64-rumprun-amd64 broken test-amd64-amd64-xl-qemut-win7-amd64 fail test-amd64-i386-xl-qemut-win7-amd64 fail test-amd64-amd64-xl-qemuu-win7-amd64 fail test-amd64-i386-xl-qemuu-win7-amd64 fail test-amd64-amd64-xl-qemut-ws16-amd64 fail test-amd64-i386-xl-qemut-ws16-amd64 broken test-amd64-amd64-xl-qemuu-ws16-amd64 fail test-amd64-i386-xl-qemuu-ws16-amd64 fail test-armhf-armhf-xl-arndale fail test-amd64-amd64-xl-credit1 pass test-arm64-arm64-xl-credit1 pass test-armhf-armhf-xl-credit1 broken test-amd64-amd64-xl-credit2 broken test-arm64-arm64-xl-credit2 pass test-armhf-armhf-xl-credit2 pass test-armhf-armhf-xl-cubietruck pass test-amd64-amd64-xl-qemuu-dmrestrict-amd64-dmrestrict pass test-amd64-i386-xl-qemuu-dmrestrict-amd64-dmrestrict fail test-amd64-amd64-examine pass test-arm64-arm64-examine pass test-armhf-armhf-examine pass test-amd64-i386-examine pass test-amd64-i386-freebsd10-i386 broken test-amd64-i386-rumprun-i386 broken test-amd64-amd64-xl-qemut-win10-i386 broken test-amd64-i386-xl-qemut-win10-i386 fail test-amd64-amd64-xl-qemuu-win10-i386 fail test-amd64-i386-xl-qemuu-win10-i386 fail test-amd64-amd64-qemuu-nested-intel fail test-amd64-amd64-xl-pvhv2-intel pass test-amd64-i386-qemut-rhel6hvm-intel pass test-amd64-i386-qemuu-rhel6hvm-intel broken test-amd64-amd64-libvirt pass test-armhf-armhf-libvirt pass test-amd64-i386-libvirt pass test-amd64-amd64-livepatch pass test-amd64-i386-livepatch pass test-amd64-amd64-migrupgrade pass test-amd64-i386-migrupgrade pass test-amd64-amd64-xl-multivcpu pass test-armhf-armhf-xl-multivcpu pass test-amd64-amd64-pair pass test-amd64-i386-pair pass test-amd64-amd64-libvirt-pair pass test-amd64-i386-libvirt-pair pass test-amd64-amd64-amd64-pvgrub pass test-amd64-amd64-i386-pvgrub fail test-amd64-amd64-xl-pvshim pass test-amd64-i386-xl-pvshim fail test-amd64-amd64-pygrub pass test-amd64-amd64-xl-qcow2 fail test-armhf-armhf-libvirt-raw pass test-amd64-i386-xl-raw fail test-amd64-amd64-xl-rtds pass test-armhf-armhf-xl-rtds pass test-amd64-amd64-xl-qemuu-debianhvm-amd64-shadow pass test-amd64-i386-xl-qemuu-debianhvm-amd64-shadow pass test-amd64-amd64-xl-shadow pass test-amd64-i386-xl-shadow pass test-amd64-amd64-libvirt-vhd fail test-armhf-armhf-xl-vhd fail ------------------------------------------------------------ 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 broken-job test-amd64-i386-freebsd10-i386 broken broken-job test-amd64-i386-xl-qemut-debianhvm-amd64 broken broken-job test-armhf-armhf-xl-credit1 broken broken-job test-amd64-i386-xl broken broken-job test-amd64-amd64-xl-qemuu-debianhvm-amd64 broken broken-job test-amd64-amd64-xl-qemut-win10-i386 broken broken-job test-amd64-i386-rumprun-i386 broken broken-job test-amd64-amd64-rumprun-amd64 broken broken-job test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm broken broken-job test-amd64-amd64-xl-credit2 broken broken-job test-amd64-i386-qemuu-rhel6hvm-intel broken broken-job test-amd64-amd64-xl-qemut-debianhvm-amd64 broken broken-job test-amd64-i386-xl-qemut-ws16-amd64 broken broken-step test-amd64-i386-qemuu-rhel6hvm-intel host-install(4) broken-step test-amd64-i386-rumprun-i386 host-install(4) broken-step test-amd64-amd64-rumprun-amd64 host-install(4) broken-step test-amd64-amd64-xl-qemut-win10-i386 host-install(4) broken-step test-amd64-i386-xl-qemut-ws16-amd64 host-install(4) broken-step test-amd64-amd64-xl-qemut-debianhvm-amd64 host-install(4) broken-step test-amd64-i386-xl-qemut-debianhvm-amd64 host-install(4) broken-step test-amd64-amd64-xl-credit2 host-install(4) broken-step test-amd64-amd64-xl-qemuu-debianhvm-amd64 host-install(4) broken-step test-amd64-i386-freebsd10-i386 host-install(4) broken-step test-amd64-i386-xl host-install(4) broken-step test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm host-install(4) broken-step test-armhf-armhf-xl-credit1 host-install(4) Not pushing. ------------------------------------------------------------ commit e72ecc7615410e5bf1a1c9a4c7772322c16eeb82 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Thu Jan 17 12:26:17 2019 +0000 x86/altp2m: Rework #VE enable/disable paths Split altp2m_vcpu_{enable,disable}_ve() out of the HVMOP_altp2m_vcpu_{enable,disable}_notify marshalling logic. A future change is going to need to call altp2m_vcpu_disable_ve() from the domain_kill() path. While at it, clean up the logic in altp2m_vcpu_{initialise,destroy}(). altp2m_vcpu_reset() has no external callers, so fold it into its two callsites. This in turn allows for altp2m_vcpu_destroy() to reuse altp2m_vcpu_disable_ve() rather than opencoding it. No practical change. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> commit 0dfffe01d5681ede6a50c6b57131320d9f4a3361 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Feb 20 13:39:20 2019 +0000 x86: Improve the efficiency of domain_relinquish_resources() pci_release_devices() takes the global PCI lock. Once pci_release_devices() has completed, it will be called redundantly each time paging_teardown() and vcpu_destroy_pagetables() continue. This is liable to be millions of times for a reasonably sized guest, and is a serialising bottleneck now that domain_kill() can be run concurrently on different domains. Instead of propagating the opencoding of the relinquish state machine, take the opportunity to clean it up. Leave a proper set of comments explaining that domain_relinquish_resources() implements a co-routine. Introduce a documented PROGRESS() macro to avoid latent bugs such as the RELMEM_xen case, and make the new PROG_* states private to domain_relinquish_resources(). Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> commit db2af23d15077605f286d8ef86c8f5d9c1b8302a Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Wed Feb 20 17:07:17 2019 +0100 x86/shadow: don't pass wrong L4 MFN to guest_walk_tables() 64-bit PV guest user mode runs on a different L4 table. Make sure - the accessed bit gets set in the correct table (and in log-dirty mode the correct page gets marked dirty) during guest walks, - the correct table gets audited by sh_audit_gw(), - correct info gets logged by print_gw(). Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: George Dunlap <george.dunlap@xxxxxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> commit b22c900c44a2db8db1c53e269e152206e55c273f Author: Varad Gautam <vrd@xxxxxxxxx> Date: Wed Feb 20 17:06:25 2019 +0100 x86/pmtimer: fix hvm_acpi_sleep_button behavior Commit 19fb14622e941 "x86/pmtimer: move ACPI registers from PMTState to hvm_domain" misconfigures pm1a_sts for hvm_acpi_sleep_button with PWRBTN_STS instead of SLPBTN_STS, which leads to XEN_DOMCTL_SENDTRIGGER_SLEEP causing guest powerdowns. Fix this. Signed-off-by: Varad Gautam <vrd@xxxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit 3c5552954c5c63860ccc01c6bc4f9c077bc26072 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Fri Feb 1 16:56:38 2019 +0000 x86/vpmu: Improve documentation and parsing for vpmu= The behaviour of vpmu=<bool> being exclusive of vpmu=bts|ipc|arch is odd and contrary to Xen's normal command line parsing behaviour. Rewrite the parsing to use the normal form, but retain the previous behaviour where the use of bts/ipc/arch implies vpmu=true. Parts of the documenation are stale, most notibly the HVM-only statement. Update it for consistency and correctness. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 1e12872d29cc36c61894e347dd3409d7d206699d Author: Roger Pau Monne <roger.pau@xxxxxxxxxx> Date: Tue Feb 19 16:26:08 2019 +0100 libs/gnttab: add missing FreeBSD functions The FreeBSD implementation is missing the following functions: osdep_gnttab_dmabuf_exp_from_refs osdep_gnttab_dmabuf_exp_wait_released osdep_gnttab_dmabuf_imp_to_refs osdep_gnttab_dmabuf_imp_release Which all deal with dmabufs, that only exists on Linux. Implement them using abort, since such functions should never be called on FreeBSD. FTR, I realized those functions where missing when attempting to use pygrub: Traceback (most recent call last): File "/usr/local/lib/xen/bin/pygrub", line 19, in <module> import xen.lowlevel.xc ImportError: /usr/local/lib/libxengnttab.so.1: Undefined symbol "osdep_gnttab_dmabuf_exp_from_refs" Fixes: ee8105 ("libgnttab: Add support for Linux dma-buf") Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> Reviewed-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@xxxxxxxx> commit 1bcd0b43a16b7a48ec9afce3887c6c841b687abb Author: Roger Pau Monne <roger.pau@xxxxxxxxxx> Date: Mon Feb 18 17:24:28 2019 +0100 vpci: reduce verboseness of BAR write warnings Avoid printing a warning message when writing to a BAR register with memory decoding enabled if the value written is the same as the current one. No functional change. Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> commit 24d5282527f4647907b3572820b5335c15cd0356 Author: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> Date: Mon Feb 18 13:46:02 2019 +0100 x86/altp2m: fix HVMOP_altp2m_set_domain_state race HVMOP_altp2m_set_domain_state does not domain_pause(), presumably on purpose (as it was originally supposed to cater to a in-guest agent, and a domain pausing itself is not a good idea). This can lead to domain crashes in the vmx_vmexit_handler() code that checks if the guest has the ability to switch EPTP without an exit. That code can __vmread() the host p2m's EPT_POINTER (before HVMOP_altp2m_set_domain_state "for_each_vcpu()" has a chance to run altp2m_vcpu_initialise(), but after d->arch.altp2m_active is set). Signed-off-by: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> commit 29d28b29190ba09d53ae7e475108def84e16e363 Author: George Dunlap <george.dunlap@xxxxxxxxxx> Date: Mon Feb 18 13:45:24 2019 +0100 altp2m: Prevent deadlocks when a domain performs altp2m operations on itself domain_pause_except_self() was introduced to allow a domain to pause itself while doing altp2m operations. However, as written, it has a risk fo deadlock if two vcpus enter the loop at the same time. Luckily, there's already a solution for this: Attempt to call domain's hypercall_deadlock_mutex, and restart the entire hypercall if you fail. Make domain_pause_except_self() attempt to grab this mutex when pausing itself, returning -ERESTART if it fails. Have the callers check for errors and pass the value up. In both cases, the top-level do_hvm_op() should DTRT when -ERESTART is returned. The (necessary) reuse of the hypercall deadlock mutex poses the risk of getting called from a context where the lock was already acquired (e.g. someone may (say) call domctl_lock(), then afterwards call domain_pause_except_self()). However, in the interest of not overcomplicating things, no changes are made here to the mutex. Attempted nesting of this lock isn't a security issue, because all that will happen is that the vcpu will livelock taking continuations. Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxxx> Tested-by: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> commit fbaa0e58f39ae23263ad0935d88a7e61e0dd9ef1 Author: Roger Pau Monné <roger.pau@xxxxxxxxxx> Date: Mon Feb 18 13:44:53 2019 +0100 pvh/dom0: warn when dom0_mem is not set There have been several reports of the dom0 builder running out of memory when building a PVH dom0 without having specified a dom0_mem value. Print a warning message if dom0_mem is not set when booting in PVH mode. This is a temporary workaround until accounting for internal memory required by Xen (ie: paging structures) is improved. Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> commit 6fa1755644d0e63793007c8d911b4b520ca95301 Author: Roger Pau Monné <roger.pau@xxxxxxxxxx> Date: Mon Feb 18 13:44:24 2019 +0100 amd/npt/shadow: replace assert that prevents creating 2M/1G MMIO entries The assert was originally added to make sure that higher order regions (> PAGE_ORDER_4K) could not be used to bypass the mmio_ro_ranges check performed by p2m_type_to_flags. This however is already checked in set_mmio_p2m_entry, which makes sure that higher order mappings don't overlap with mmio_ro_ranges, thus allowing the creation of high order MMIO mappings safely. Replace the assert to allow 2M/1G entries to be created for MMIO regions and add some extra asserts as a replacement to make sure there's no overlapping with MMIO read-only ranges. Note that 1G MMIO entries will not be created unless mmio_order is changed to allow it. Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: George Dunlap <george.dunlap@xxxxxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> commit 036c6cbddca28be5a526da045bb379fedfad8255 Author: Roger Pau Monné <roger.pau@xxxxxxxxxx> Date: Mon Feb 18 13:43:50 2019 +0100 x86/pvh: reorder PVH dom0 iommu initialization So that the iommu is initialized before populating the p2m, and entries added get the corresponding iommu page table entries if required. This requires splitting the current pvh_setup_p2m into two different functions. One that crafts dom0 physmap and sets the paging allocation, and another one that actually populates the p2m with RAM regions. Note that this allows to remove the special casing done for the low 1MB in hwdom_iommu_map. Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> commit dc0b0b1f2d5792ecd9e26f2e65b36682f8ec2b27 Author: Roger Pau Monné <roger.pau@xxxxxxxxxx> Date: Mon Feb 18 13:42:51 2019 +0100 dom0/pvh: align allocation and mapping order to start address The p2m and iommu mapping code always had the requirement that addresses and orders must be aligned when populating the p2m or the iommu page tables. PVH dom0 builder didn't take this requirement into account, and can call into the p2m/iommu mapping helpers with addresses and orders that are not aligned. Fix this by making sure the orders passed to the physmap population helpers are always aligned to the guest address to be populated. Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> (qemu changes not included) _______________________________________________ osstest-output mailing list osstest-output@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/osstest-output
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |