From: "Jan Beulich" <JBeulich@suse.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
xen-devel@lists.xenproject.org
Subject: Re: Build error iasl/dsdt after commit "hvmloader: also cover PCI MMIO ranges above 4G with UC MTRR ranges"
Date: Thu, 22 May 2014 10:30:24 +0100 [thread overview]
Message-ID: <537DDFD00200007800014D5E@mail.emea.novell.com> (raw)
In-Reply-To: <1400750164.11409.34.camel@kazak.uk.xensource.com>
>>> On 22.05.14 at 11:16, <Ian.Campbell@eu.citrix.com> wrote:
> 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)
That last one is one off - the end address ought to be fffffffff. If
that works, it would still end up being an alignment issue... (The
reason for picking the original numbers was that I want the
range as far off as possible, but also not beyond the default
36-bit boundary. Minus eventual alignment requirements I'd like
to stick to that.)
Jan
Jan
next prev parent reply other threads:[~2014-05-22 9:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 18:58 Build error iasl/dsdt after commit "hvmloader: also cover PCI MMIO ranges above 4G with UC MTRR ranges" Sander Eikelenboom
2014-05-22 7:24 ` Jan Beulich
2014-05-22 9:16 ` Ian Campbell
2014-05-22 9:30 ` Jan Beulich [this message]
2014-05-22 9:56 ` Ian Campbell
2014-05-22 10:07 ` Jan Beulich
2014-05-22 10:12 ` Ian Campbell
2014-05-22 12:21 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=537DDFD00200007800014D5E@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).