On 05.12.14 at 07:24, kevin.t...@intel.com wrote:
From: Jan Beulich [mailto:jbeul...@suse.com]
Sent: Friday, December 05, 2014 12:29 AM
On 01.12.14 at 10:24, tiejun.c...@intel.com wrote:
In some cases like igd_opregion_pgbase, guest will use mem_hole_alloc
to allocate some memory to
From: Chen, Tiejun
Sent: Monday, December 01, 2014 5:24 PM
In some cases like igd_opregion_pgbase, guest will use mem_hole_alloc
to allocate some memory to use in runtime cycle, so we alsoe need to
make sure all reserved device memory don't overlap such a region.
OK, seems you meant to use
On Mon, Dec 01, 2014 at 05:24:28PM +0800, Tiejun Chen wrote:
In some cases like igd_opregion_pgbase, guest will use mem_hole_alloc
to allocate some memory to use in runtime cycle, so we alsoe need to
s/cycle//
s/alsoe/also
make sure all reserved device memory don't overlap such a region.
In some cases like igd_opregion_pgbase, guest will use mem_hole_alloc
to allocate some memory to use in runtime cycle, so we alsoe need to
make sure all reserved device memory don't overlap such a region.
Signed-off-by: Tiejun Chen tiejun.c...@intel.com
---
tools/firmware/hvmloader/util.c | 22
