On Tue, Oct 30, 2018 at 10:25:20AM -0600, Jan Beulich wrote:
> >>> On 29.10.18 at 13:40, wrote:
> > @@ -316,6 +339,22 @@ void p2m_memory_type_changed(struct domain *d)
> > }
> > }
> >
> > +void p2m_memory_type_changed(struct domain *d)
> > +{
> > +
>>> On 29.10.18 at 13:40, wrote:
> @@ -316,6 +339,22 @@ void p2m_memory_type_changed(struct domain *d)
> }
> }
>
> +void p2m_memory_type_changed(struct domain *d)
> +{
> +_memory_type_changed(p2m_get_hostp2m(d));
> +
> +#ifdef CONFIG_HVM
> +if ( unlikely(altp2m_active(d)) )
> +
On Mon, Oct 29, 2018 at 6:41 AM Razvan Cojocaru
wrote:
>
> When an new altp2m view is created very early on guest boot, the
> display will freeze (although the guest will run normally). This
> may also happen on resizing the display. The reason is the way
> Xen currently (mis)handles logdirty
When an new altp2m view is created very early on guest boot, the
display will freeze (although the guest will run normally). This
may also happen on resizing the display. The reason is the way
Xen currently (mis)handles logdirty VGA: it intentionally
misconfigures VGA pages so that they will
