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

branch xen-unstable xenbranch xen-unstable job test-amd64-i386-xl-qemut-winxpsp3 testid guest-stop 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-traditi

Re: [Xen-devel] [PATCH v2 3/5] VT-d PI: restrict the vcpu number on a given pcpu

> From: Gao, Chao > Sent: Thursday, May 11, 2017 2:04 PM > > Currently, a blocked vCPU is put in its pCPU's pi blocking list. If > too many vCPUs are blocked on a given pCPU, it will incur that the list > grows too long. After a simple analysis, there are 32k domains and > 128 vcpu per domain, thu

[Xen-devel] [xen-unstable test] 109418: regressions - FAIL

flight 109418 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/109418/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-winxpsp3 16 guest-stop fail REGR. vs. 109165 Tests which are fa

[Xen-devel] [PATCH] acpi: enlarge NUM_FIXMAP_ACPI_PAGES to support larger scale boards

In acpi_tb_verify_table()->__acpi_map_table(), it suppose all ACPI tables may not exceed 4 pages, the tables includes SRAT/APIC/ERST etc. Please note that the table DSDT is not mapped through acpi_tb_verify_table(), thus we don't care its size although it's usually the largest table among all the A

Re: [Xen-devel] [PATCH v2 1/5] xentrace: add TRC_HVM_PI_LIST_ADD

> From: Gao, Chao > Sent: Thursday, May 11, 2017 2:04 PM > > This patch adds TRC_HVM_PI_LIST_ADD to track adding one entry to > the per-pcpu blocking list. Also introduce a 'counter' to track > the number of entries in the list. > > Signed-off-by: Chao Gao > --- > tools/xentrace/formats

Re: [Xen-devel] [PATCH v2 for-4.9] x86/mm: Fix incorrect unmapping of 2MB and 1GB pages

> From: Igor Druzhinin [mailto:igor.druzhi...@citrix.com] > Sent: Wednesday, May 10, 2017 7:13 PM > > The same set of functions is used to set as well as to clean > P2M entries, except that for clean operations INVALID_MFN (~0UL) > is passed as a parameter. Unfortunately, when calculating an > app

[Xen-devel] [linux-4.9 test] 109410: regressions - FAIL

flight 109410 linux-4.9 real [real] http://logs.test-lab.xenproject.org/osstest/logs/109410/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl-credit2 6 xen-boot fail REGR. vs. 107358 test-amd64-i386-xl-qe

[Xen-devel] [qemu-mainline test] 109416: regressions - FAIL

flight 109416 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/109416/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm 5 xen-buildfail REGR. vs. 107636 build-arm64

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

flight 109404 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/109404/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemut-winxpsp3 16 guest-stop fail REGR. vs. 59254 test-amd64-amd64-xl

Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?

On 05/14/17 08:39, Andrew Cooper wrote: > On 14/05/17 00:17, PGNet Dev wrote: >> On 5/13/17 3:15 PM, Valentin Vidic wrote: >>> Try booting without 'hpet=force,verbose clocksource=hpet' and it should >>> select xen by default: >> Nope. Well, not quite ... >> >> With both >> >> 'hpet=force,verb

Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?

On 13/05/17 22:16, Andrew Cooper wrote: > On 13/05/2017 21:05, PGNet Dev wrote: >> On 5/13/17 12:59 PM, Andrew Cooper wrote: >>> Ok. Lack of a clocksource is to be expected. >>> >>> The reason why the HPETs are unavailable is that dom0 is not a position >>> to program them; dom0 doesn't know what

Re: [Xen-devel] HPET enabled in BIOS, not presented as available_clocksource -- config, kernel code, &/or BIOS?

On 14/05/17 00:17, PGNet Dev wrote: > On 5/13/17 3:15 PM, Valentin Vidic wrote: >> Try booting without 'hpet=force,verbose clocksource=hpet' and it should >> select xen by default: > Nope. Well, not quite ... > > With both > > 'hpet=force,verbose clocksource=hpet' > > removed, I end up with

[Xen-devel] [xen-unstable test] 109395: regressions - FAIL

flight 109395 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/109395/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-winxpsp3 16 guest-stop fail REGR. vs. 109165 Tests which did no

[Xen-devel] [qemu-mainline test] 109399: regressions - FAIL

flight 109399 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/109399/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-arm64-xsm 5 xen-buildfail REGR. vs. 107636 build-arm64

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

flight 109413 xen-unstable-coverity real [real] http://logs.test-lab.xenproject.org/osstest/logs/109413/ Perfect :-) All tests in this flight passed as required version targeted for testing: xen 17880a0f10421c5e456d593c70da03b1688d34ac baseline version: xen cbca

Re: [Xen-devel] 4.9rc4: Cannot build with higher than -j4 - was: linux.c:27:28: fatal error: xen/sys/evtchn.h: No such file or directory

On 10/05/17 23:02, Steven Haigh wrote: > On 10/05/17 01:20, M A Young wrote: >> On Tue, 9 May 2017, Steven Haigh wrote: >> >>> I'm trying to use the same build procedure I had for working correctly >>> for Xen 4.7 & 4.8.1 - but am coming across this error: >>> >>> gcc -DPIC -m64 -DBUILD_ID -fno-st

[Xen-devel] [linux-4.9 test] 109393: regressions - FAIL

flight 109393 linux-4.9 real [real] http://logs.test-lab.xenproject.org/osstest/logs/109393/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl-credit2 6 xen-boot fail REGR. vs. 107358 test-amd64-i386-xl-qe

Re: [Xen-devel] [PATCH v7 2/3] * util/grub.d/20_linux_xen.in: Add xen_boot command support for aarch64

Hi Vladimir, On 11 May 2017 at 22:25, Fu Wei wrote: > Hi Vladimir, > > On 11 May 2017 at 06:01, Vladimir 'phcoder' Serbinenko > wrote: >> >> >> On Tue, May 9, 2017, 11:02 Fu Wei wrote: >>> >>> Hi Vladimir >>> >>> On 9 May 2017 at 14:59, Vladimir 'phcoder' Serbinenko >>> wrote: >>> > >>> > >>>

[Xen-devel] [PATCH v8 0/3] arm64, xen: add xen_boot support into grub-mkconfig

From: Fu Wei This patchset add xen_boot support into grub-mkconfig for generating xen boot entrances automatically Also update the docs/grub.texi for new xen_boot commands. ChangeLog: v8: http://lists.gnu.org/archive/html/grub-devel/2017-05/ Delete the redundant "#include " in patch 0001.

[Xen-devel] [PATCH v8 2/3] * util/grub.d/20_linux_xen.in: Add xen_boot command support for aarch64

From: Fu Wei This patch adds the support of xen_boot command for aarch64: xen_hypervisor xen_module These two commands are only for aarch64, since it has its own protocol and commands to boot xen hypervisor and Dom0, but not multiboot. For other architectures, they are still using multib

[Xen-devel] [PATCH v8 3/3] arm64: update the introduction of xen boot commands in docs/grub.texi

From: Fu Wei delete: xen_linux, xen_initrd, xen_xsm add: xen_module This update bases on commit 0edd750e50698854068358ea53528100a9192902 Author: Vladimir Serbinenko Date: Fri Jan 22 10:18:47 2016 +0100 xen_boot: Remove obsolete module type distinctions. Also bases on the

[Xen-devel] [PATCH v8 1/3] arm64: add "--nounzip" option support in xen_module command

From: Fu Wei This patch adds "--nounzip" option support in order to be compatible with the module command of multiboot on other architecture, by this way we can simplify grub-mkconfig support code. This patch also allow us to use zip compressed module(like Linux kernel for Dom0). Signed-off-by: