Re: [Xen-devel] Build error iasl/dsdt after commit "hvmloader: also cover PCI MMIO ranges above 4G with UC MTRR ranges"

[Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>]

On Thu, 2014-05-22 at 08:24 +0100, Jan Beulich wrote:
> >>> On 21.05.14 at 20:58, <linux@xxxxxxxxxxxxxx> wrote:
> > It seems commit "d06886694328a31369addc1f614cf326728d65a6: 
> > "hvmloader: also cover PCI MMIO ranges above 4G with UC MTRR ranges"
> > causes the build error below.
> > 
> > In case it's relevant it's with iasl from debian wheezy, which is version:  
> > iasl 20100528-3 
> 
> I tried a variety of iasl-s (ranging from 2006 to 2012), with none of
> them triggering this. So I'm afraid this is a bug of the specific iasl in
> Wheezy - I'm not sure how to deal with that.

FWIW I can reproduce on a Wheezy machine. The automated tests run under
Wheezy so this is probably going to block testing.

I think the chances of getting Wheezy fixed are pretty minimal, at least
soon. I think we will probably have to work around it.

>  Furthermore, as already
> indicated in a reply to an inquiry on it by Ian C, I'm having a physical
> machine here with exactly the same QWordMemory() template, so all
> zeros in there can't be entirely wrong. While we overwrite all three
> fields (HMIN, HMAX, and HLEN) anyway, I'm not sure putting in some
> random range deemed valid by that specific tool version is a good
> idea. But to help with the decision, could you try whether that
> 
>                     QWordMemory (
>                         ResourceProducer, PosDecode, MinFixed, MaxFixed,
>                         NonCacheable, ReadWrite,
>                         0x0000000000000000,
>                         0x0000000fffffffff,
>                         0x0000001000000000,
>                         0x0000000000000000,
>                         0x0000000000000001,
>                         ,, _Y02)
> 
> 
> would at least help?

Unfortunately not:
dsdt_anycpu.asl   164:                          0x0000000000000001,
Error    4118 -      Length is not equal to fixed Min/Max window ^ 

I also tried ...ffffffc + 4 and ..fffff8 + 8 in case it was a alignment
requirement or something, but apparently not since it didn't help.

I also tried a 100000000-100000001 span, no joy.

This worked though:
                  QWordMemory (
                         ResourceProducer, PosDecode, MinFixed, MaxFixed,
                         NonCacheable, ReadWrite,
                         0x0000000000000000,
                         0x0000001000000000,
                         0x000000100000000f,
                         0x0000000000000000,
                         0x0000000000000010,
                         ,, _Y02)

But this doesn't:
                  QWordMemory (
                         ResourceProducer, PosDecode, MinFixed, MaxFixed,
                         NonCacheable, ReadWrite,
                         0x0000000000000000,
                         0x0000000ffffffff0,
                         0x0000001000000000,
                         0x0000000000000000,
                         0x0000000000000010,
                         ,, _Y02)


Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel