[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [xen-unstable test] 16788: regressions - FAIL

>>> On 02.03.13 at 13:34, xen.org <ian.jackson@xxxxxxxxxxxxx> wrote:
> flight 16788 xen-unstable real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/16788/ 
> Regressions :-(
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-i386-xend-qemut-winxpsp3  7 windows-install    fail REGR. vs. 
> 16772
>  test-amd64-i386-win           7 windows-install           fail REGR. vs. 
> 16772

So this (and presumably other Windows failures too) is apparently
a regression from 703ac3abcfc5f649c038070867ee12c67f730548
("x86: introduce create_perdomain_mapping()"), running into

        /* Hack: we map the pages into the vcpu's LDT space, since we
         * know that we're not going to need the LDT for HVM guests, 
         * and only HVM guests are allowed unaligned writes. */
        map = (void *)LDT_VIRT_START(v);
        offset = l1_linear_offset((unsigned long) map);
                  l1e_from_pfn(mfn_x(sh_ctxt->mfn1), __PAGE_HYPERVISOR));
        l1e_write(&__linear_l1_table[offset + 1],
                  l1e_from_pfn(mfn_x(sh_ctxt->mfn2), __PAGE_HYPERVISOR));
        map += (vaddr & ~PAGE_MASK);

Question - is there really no better way than this to deal with
cross page emulated writes? If not, I'll have to figure out where in
the shadow initialization code a call to create_perdomain_mapping()
would need to be added.


>  test-amd64-i386-xl-qemut-winxpsp3-vcpus1 7 windows-install fail REGR. vs. 
> 16772
>  test-amd64-amd64-xl-qemuu-winxpsp3  7 windows-install     fail REGR. vs. 
> 16772
>  test-amd64-i386-xend-winxpsp3  7 windows-install          fail REGR. vs. 
> 16772

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.