>>> On 01.11.16 at 15:39, wrote:
> Also I realized that "Range Size and Alignment Requirement" aren't meet
> with the code I wrote - as the size (2^n) must be aligned on the
> 2^n boundary, and that is certainly not meet.
Yes, this would better be obeyed to.
> Anyhow the
. snip..
> I modified it be subtractive, and got it to start with
> large areas and then smaller and smaller:
>
> (d2) - CPU0 ... 36-bit phys ... fixed MTRRs ... Cover @04344(MB) to
> 65536(M
> (d2) B) with 7 MTRRs.
> (d2) MTRR 1 @04344(MB) 37112(MB)
> (d2) MTRR 2
On Thu, Oct 13, 2016 at 03:20:24AM -0600, Jan Beulich wrote:
> >>> On 12.10.16 at 23:15, wrote:
> > On Wed, Sep 28, 2016 at 03:21:08AM -0600, Jan Beulich wrote:
> >> >>> On 27.09.16 at 16:43, wrote:
> >> > If the guest is booted with 'pci' we
>>> On 12.10.16 at 23:15, wrote:
> On Wed, Sep 28, 2016 at 03:21:08AM -0600, Jan Beulich wrote:
>> >>> On 27.09.16 at 16:43, wrote:
>> > If the guest is booted with 'pci' we nicely expand the MMIO region below
>> > 4GB and try to fit in the BARs in
On Wed, Sep 28, 2016 at 03:21:08AM -0600, Jan Beulich wrote:
> >>> On 27.09.16 at 16:43, wrote:
> > If the guest is booted with 'pci' we nicely expand the MMIO region below
> > 4GB and try to fit in the BARs in there. If that fails (not enough
> > space) we move it above
On Wed, Sep 28, 2016 at 03:21:08AM -0600, Jan Beulich wrote:
> >>> On 27.09.16 at 16:43, wrote:
> > If the guest is booted with 'pci' we nicely expand the MMIO region below
> > 4GB and try to fit in the BARs in there. If that fails (not enough
> > space) we move it above
>>> On 27.09.16 at 16:43, wrote:
> If the guest is booted with 'pci' we nicely expand the MMIO region below
> 4GB and try to fit in the BARs in there. If that fails (not enough
> space) we move it above the memory (64-bit). And throughout all of this
> we also update the
Hey!
If the guest is booted with 'pci' we nicely expand the MMIO region below
4GB and try to fit in the BARs in there. If that fails (not enough
space) we move it above the memory (64-bit). And throughout all of this
we also update the _CRS field to cover these ranges.
(Note, I need to check if