[Xen-devel] [PATCH 0/2] x86/xen: avoid 32-bit writes to PTEs in PV PAE guests

2018-08-19 Thread Juergen Gross
While the hypervisor emulates plain writes to PTEs happily, this is much slower than issuing a hypercall for PTE modifcations. And writing a PTE via two 32-bit write instructions (especially when clearing the PTE) will result in an intermediate L1TF vulnerable PTE. Writes to PAE PTEs should

[Xen-devel] [PATCH 2/2] x86/pae: use 64 bit atomic xchg function in native_ptep_get_and_clear

2018-08-19 Thread Juergen Gross
Using only 32-bit writes for the pte will result in an intermediate L1TF vulnerable PTE. When running as a Xen PV guest this will at once switch the guest to shadow mode resulting in a loss of performance. Use arch_atomic64_xchg() instead which will perform the requested operation atomically with

[Xen-devel] [PATCH 1/2] x86/xen: don't write ptes directly in 32-bit PV guests

2018-08-19 Thread Juergen Gross
In some cases 32-bit PAE PV guests still write PTEs directly instead of using hypercalls. This is especially bad when clearing a PTE as this is done via 32-bit writes which will produce intermediate L1TF attackable PTEs. Change the code to use hypercalls instead. Signed-off-by: Juergen Gross

[Xen-devel] [linux-4.14 test] 126149: regressions - FAIL

2018-08-19 Thread osstest service owner
flight 126149 linux-4.14 real [real] http://logs.test-lab.xenproject.org/osstest/logs/126149/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-examine 4 memdisk-try-append fail REGR. vs. 125904 Tests which did not

Re: [Xen-devel] [PATCH v2 2/2] x86/mmcfg/drhd: Move acpi_mmcfg_init() call before calling acpi_parse_dmar()

2018-08-19 Thread Zhenzhong Duan
On 2018/8/17 20:28, Jan Beulich wrote: On 17.08.18 at 09:01, wrote: pci_conf_read8() needs pci mmcfg mapping to work on multiple pci segments system such as HPE Superdome-Flex. Move acpi_mmcfg_init() call in acpi_boot_init() before calling acpi_parse_dmar() so that when pci_conf_read8() is

[Xen-devel] [PATCH 1/2] dmar: iommu mem leak fix

2018-08-19 Thread Zhenzhong Duan
Release memory allocated for drhd iommu in error path. Signed-off-by: Zhenzhong Duan --- xen/drivers/passthrough/vtd/dmar.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/xen/drivers/passthrough/vtd/dmar.c b/xen/drivers/passthrough/vtd/dmar.c index 46decd4..8c5fa80

[Xen-devel] [PATCH 2/2] x86/dmar: zap DMAR signature for dom0 once in TBOOT case

2018-08-19 Thread Zhenzhong Duan
When TBOOT enabled, acpi_parse_dmar() zap a copy of DMAR table rather than the real table, so make it controled by config option based on the fact that we already have done the real zapping in tboot_parse_dmar_table(). As said above, acpi_parse_dmar() doesn't zaps APCI DMAR signature in real TXT

[Xen-devel] [xen-4.8-testing test] 126163: tolerable FAIL - PUSHED

2018-08-19 Thread osstest service owner
flight 126163 xen-4.8-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/126163/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-armhf-armhf-xl-rtds 16 guest-start/debian.repeatfail like 125679 test-xtf-amd64-amd64-2 50

[Xen-devel] [linux-linus bisection] complete test-amd64-i386-xl-shadow

2018-08-19 Thread osstest service owner
branch xen-unstable xenbranch xen-unstable job test-amd64-i386-xl-shadow testid xen-boot Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git

[Xen-devel] [xen-4.7-testing test] 126094: regressions - FAIL

2018-08-19 Thread osstest service owner
flight 126094 xen-4.7-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/126094/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-libvirt-pair 22 guest-migrate/src_host/dst_host fail REGR. vs. 125057

[Xen-devel] [qemu-mainline baseline-only test] 75089: regressions - FAIL

2018-08-19 Thread Platform Team regression test user
This run is configured for baseline tests only. flight 75089 qemu-mainline real [real] http://osstest.xensource.com/osstest/logs/75089/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm 10

Re: [Xen-devel] [PATCH 24/34] x86/mem_access: put HVM only function under CONFIG_HVM

2018-08-19 Thread Razvan Cojocaru
On 8/17/18 6:12 PM, Wei Liu wrote: > Signed-off-by: Wei Liu > --- > xen/arch/x86/mm/mem_access.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/xen/arch/x86/mm/mem_access.c b/xen/arch/x86/mm/mem_access.c > index 03a8641..e1525fd 100644 > --- a/xen/arch/x86/mm/mem_access.c > +++

Re: [Xen-devel] [PATCH 22/34] x86/mm: put HVM only code under CONFIG_HVM

2018-08-19 Thread Razvan Cojocaru
On 8/17/18 6:12 PM, Wei Liu wrote: > Going through the code, nested EPT, EPT, and ALTP2M depend on HVM code. Put > these components under CONFIG_HVM. This further requires putting one > of the vm event under CONFIG_HVM. > > Also make hap_enabled evaluate to false when !CONFIG_HVM. This in turn >

[Xen-devel] [PATCH v4 12/16] x86/xen: enable Hygon support to Xen

2018-08-19 Thread Pu Wen
To make Xen works functionly on Hygon platforms, reuse AMD's Xen support code path for Hygon. There are six core performance events counters per thread, so there are six MSRs for these counters(0-5). Also there are four legacy PMC MSRs, they are alias of the counters(0-3). In this version of

[Xen-devel] [PATCH v4 00/16] Add support for Hygon Dhyana Family 18h processor

2018-08-19 Thread Pu Wen
As a new x86 CPU Vendor, Chengdu Haiguang IC Design Co., Ltd (Hygon) is a Joint Venture between AMD and Haiguang Information Technology Co., Ltd., and aims at providing high performance x86 processor for China server market. The first generation Hygon's processor(Dhyana) originates from AMD

[Xen-devel] [linux-next test] 126051: regressions - FAIL

2018-08-19 Thread osstest service owner
flight 126051 linux-next real [real] http://logs.test-lab.xenproject.org/osstest/logs/126051/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qcow210 debian-di-installfail REGR. vs. 125898

[Xen-devel] [linux-linus test] 126069: regressions - FAIL

2018-08-19 Thread osstest service owner
flight 126069 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/126069/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-shadow 7 xen-boot fail REGR. vs. 125898

[Xen-devel] [xen-4.9-testing test] 126075: regressions - FAIL

2018-08-19 Thread osstest service owner
flight 126075 xen-4.9-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/126075/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-libvirt-pair 22 guest-migrate/src_host/dst_host fail REGR. vs. 124328 Tests

[Xen-devel] [xen-4.11-testing baseline-only test] 75088: regressions - FAIL

2018-08-19 Thread Platform Team regression test user
This run is configured for baseline tests only. flight 75088 xen-4.11-testing real [real] http://osstest.xensource.com/osstest/logs/75088/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-freebsd10-amd64 22 leak-check/check

[Xen-devel] [xen-unstable-coverity test] 126197: all pass - PUSHED

2018-08-19 Thread osstest service owner
flight 126197 xen-unstable-coverity real [real] http://logs.test-lab.xenproject.org/osstest/logs/126197/ Perfect :-) All tests in this flight passed as required version targeted for testing: xen b8f33431f3dd23fb43a879f4bdb4283fdc9465ad baseline version: xen

[Xen-devel] [libvirt test] 126073: regressions - FAIL

2018-08-19 Thread osstest service owner
flight 126073 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/126073/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-libvirt6 libvirt-buildfail REGR. vs. 123814 build-amd64-libvirt