On Thu, Feb 23, 2017 at 04:16:15PM +, Andrew Cooper wrote:
> On 23/02/17 16:09, Jan Beulich wrote:
> On 23.02.17 at 16:27, wrote:
> >> I also don't see much benefit from deviating from what HVM does, so I would
> >> just leave it as is.
> > Understood. The risk is that in a couple of year
On 23/02/17 16:09, Jan Beulich wrote:
On 23.02.17 at 16:27, wrote:
>> I also don't see much benefit from deviating from what HVM does, so I would
>> just leave it as is.
> Understood. The risk is that in a couple of years time understanding
> why it is the way it is and (whether that's necess
>>> On 23.02.17 at 16:27, wrote:
> I also don't see much benefit from deviating from what HVM does, so I would
> just leave it as is.
Understood. The risk is that in a couple of years time understanding
why it is the way it is and (whether that's necessary) may take as
much effort as did the deci
On Thu, Feb 23, 2017 at 06:39:53AM -0700, Jan Beulich wrote:
> >>> On 22.02.17 at 15:24, wrote:
> > Craft the Dom0 e820 memory map and populate it. Introduce a helper to remove
> > memory pages that are shared between Xen and a domain, and use it in order
> > to
> > remove low 1MB RAM regions fro
>>> On 22.02.17 at 15:24, wrote:
> Craft the Dom0 e820 memory map and populate it. Introduce a helper to remove
> memory pages that are shared between Xen and a domain, and use it in order to
> remove low 1MB RAM regions from dom_io in order to assign them to a PVHv2
> Dom0.
>
> On hardware lack
Craft the Dom0 e820 memory map and populate it. Introduce a helper to remove
memory pages that are shared between Xen and a domain, and use it in order to
remove low 1MB RAM regions from dom_io in order to assign them to a PVHv2 Dom0.
On hardware lacking support for unrestricted mode also craft th
