On Tue, Apr 11, 2017 at 3:50 AM, Stefano Stabellini
wrote:
> On Mon, 10 Apr 2017, Stefano Stabellini wrote:
>> On Mon, 10 Apr 2017, hrg wrote:
>> > On Sun, Apr 9, 2017 at 11:55 PM, hrg wrote:
>> > > On Sun, Apr 9, 2017 at 11:52 PM, hrg wrote:
On Sun, Apr 9, 2017 at 11:55 PM, hrg wrote:
> On Sun, Apr 9, 2017 at 11:52 PM, hrg wrote:
>> Hi,
>>
>> In xen_map_cache_unlocked(), map to guest memory maybe in entry->next
>> instead of first level entry (if map to rom other than guest memory
>> comes first
On Sun, Apr 9, 2017 at 11:52 PM, hrg wrote:
> Hi,
>
> In xen_map_cache_unlocked(), map to guest memory maybe in entry->next
> instead of first level entry (if map to rom other than guest memory
> comes first), while in xen_invalidate_map_cache(), when VM ballooned
> out
Hi,
In xen_map_cache_unlocked(), map to guest memory maybe in entry->next
instead of first level entry (if map to rom other than guest memory
comes first), while in xen_invalidate_map_cache(), when VM ballooned
out memory, qemu did not invalidate cache entries in linked
list(entry->next), so when
