flight 65765 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65765/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-freebsd10-i386 6 xen-bootfail REGR. vs. 59254
test-amd64-i386-xl-qe
This run is configured for baseline tests only.
flight 38503 qemu-mainline real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38503/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvh-amd 6 xen-boot
flight 65763 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65763/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-rumpuserxen-i386 10 guest-start fail REGR. vs. 60684
test-amd64
This run is configured for baseline tests only.
flight 38501 xen-4.3-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38501/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-migrupgrade 21 guest-migrate/src_hos
flight 65748 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65748/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 15 guest-start/debian.repeat fail REGR. vs. 65635
Regressions which ar
Using MMUEXT_TLB_FLUSH_MULTI doesn't buy us much since the hypervisor
will likely perform same IPIs as would have the guest.
More importantly, using MMUEXT_INVLPG_MULTI may not to invalidate the
guest's address on remote CPU (when, for example, VCPU from another guest
is running there).
Signed-of
On 12/12/2015 22:30, Joshua Otto wrote:
> On Sat, Dec 12, 2015 at 10:19:31AM +0800, Yang Hongyang wrote:
>> On 2015年12月11日 01:23, Andrew Cooper wrote:
>>> Hello - thankyou for your interest.
>>>
>>> One area to look at might be the parameters to the live migration
>>> looping. As part of the migra
flight 65756 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65756/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt5 libvirt-build fail REGR. vs. 63340
build-amd64-libvirt
This run is configured for baseline tests only.
flight 38500 xen-4.5-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38500/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-xl-qemuu-win7-amd64 15 guest-localmig
On Sat, Dec 12, 2015 at 10:19:31AM +0800, Yang Hongyang wrote:
> On 2015年12月11日 01:23, Andrew Cooper wrote:
> >
> >Hello - thankyou for your interest.
> >
> >One area to look at might be the parameters to the live migration
> >looping. As part of the migration v2 rework I did in the 4.6 dev
> >per
On Fri, Dec 11, 2015 at 01:52:41PM +, Ian Campbell wrote:
> Cool! Just to be clear, you are looking for one project for the 3 of you to
> work on as a group (vs 3 individual projects), is that right?
Yes, that's right.
> It's been a while since there has been a scan run, I did one yesterday b
flight 65737 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65737/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail
REGR. vs. 65608
Regre
flight 65709 linux-3.14 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65709/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-rumpuserxen-i386 10 guest-start fail REGR. vs. 64562
Regressions which are
flight 65699 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65699/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-rumpuserxen-i386 10 guest-start fail REGR. vs. 63996
Tests which are failing
If IOTLB/Context/IETC flush is timeout, we should think
all devices under this IOMMU cannot function correctly.
So for each device under this IOMMU we'll mark it as
unassignable and kill the domain owning the device.
If Device-TLB flush is timeout, we'll mark the target
ATS device as unassignable
This patches are based on Kevin Tian's previous discussion 'Revisit VT-d
asynchronous flush issue'.
Fix current timeout concern and also allow limited ATS support in a light way:
1. Reduce spin timeout to 1ms, which can be boot-time changed with
'iommu_qi_timeout_ms'.
For example:
Signed-off-by: Quan Xu
---
xen/drivers/passthrough/vtd/qinval.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/xen/drivers/passthrough/vtd/qinval.c
b/xen/drivers/passthrough/vtd/qinval.c
index b81b0bd..990baf2 100644
--- a/xen/drivers/passthrough/vtd/qinval.c
+++
This run is configured for baseline tests only.
flight 38496 xen-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38496/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 3 host-install(
flight 65697 linux-3.10 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65697/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-rumpuserxen-i386 10 guest-start fail REGR. vs. 64456
Regressions which are
In case of HVM guests, where is the sh_page_fault function called?
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
El 11/12/15 a les 18.22, Ian Campbell ha escrit:
> On Wed, 2015-12-09 at 16:17 +, Ian Jackson wrote:
>> Ian Campbell writes ("[PATCH XEN v6 29/32] tools/libs/call: Use O_CLOEXEC
>> when opening /dev/xen/privcmd on Linux"):
>>> We stick with using FD_CLOEXEC on the legacy /proc/xen/privcmd
>>> f
>On 11.12.2015 at 6:01pm, wrpte:
> >>> On 10.12.15 at 10:33, wrote:
> > @@ -167,10 +172,12 @@ static int queue_invalidate_wait(struct iommu
> *iommu,
> > start_time = NOW();
> > while ( poll_slot != QINVAL_STAT_DONE )
> > {
> > -if ( NOW() > (start_time + DM
22 matches
Mail list logo
