On 08/02/17 10:02, Tim Deegan wrote:
> At 03:44 -0700 on 31 Jan (1485834259), Jan Beulich wrote:
> On 30.01.17 at 16:17, wrote:
>>> Commit 71bb7304e7a7a35ea6df4b0cedebc35028e4c159 added flushing of
>>> nested p2m tables whenever the host p2m table changed.
At 03:44 -0700 on 31 Jan (1485834259), Jan Beulich wrote:
> >>> On 30.01.17 at 16:17, wrote:
> > Commit 71bb7304e7a7a35ea6df4b0cedebc35028e4c159 added flushing of
> > nested p2m tables whenever the host p2m table changed. Unfortunately
> > in the process, it added a
On Tue, Jan 31, 2017 at 3:24 AM, George Dunlap wrote:
> On 30/01/17 17:07, Tamas K Lengyel wrote:
>> Hi George,
>> yeap, this solves old mem_access settings being triggered when I
>> recreate altp2m views. Thanks!
>>
>> On Mon, Jan 30, 2017 at 8:17 AM, George Dunlap
On 31/01/17 10:44, Jan Beulich wrote:
On 30.01.17 at 16:17, wrote:
>> Commit 71bb7304e7a7a35ea6df4b0cedebc35028e4c159 added flushing of
>> nested p2m tables whenever the host p2m table changed. Unfortunately
>> in the process, it added a filter to the generic
>>> On 30.01.17 at 16:17, wrote:
> Commit 71bb7304e7a7a35ea6df4b0cedebc35028e4c159 added flushing of
> nested p2m tables whenever the host p2m table changed. Unfortunately
> in the process, it added a filter to the generic p2m_flush_table()
> function so that the p2m
On 30/01/17 17:07, Tamas K Lengyel wrote:
> Hi George,
> yeap, this solves old mem_access settings being triggered when I
> recreate altp2m views. Thanks!
>
> On Mon, Jan 30, 2017 at 8:17 AM, George Dunlap
> wrote:
>> Commit 71bb7304e7a7a35ea6df4b0cedebc35028e4c159
George / Tamas,
I'm away from my dev machine so I cannot test. Thank you both for
working so quickly to resolve this behavior!
Best regards,
--Matt
On 01/30/2017 11:07 AM, Tamas K Lengyel wrote:
> Hi George,
> yeap, this solves old mem_access settings being triggered when I
> recreate altp2m
Hi George,
yeap, this solves old mem_access settings being triggered when I
recreate altp2m views. Thanks!
On Mon, Jan 30, 2017 at 8:17 AM, George Dunlap wrote:
> Commit 71bb7304e7a7a35ea6df4b0cedebc35028e4c159 added flushing of
> nested p2m tables whenever the host p2m
Commit 71bb7304e7a7a35ea6df4b0cedebc35028e4c159 added flushing of
nested p2m tables whenever the host p2m table changed. Unfortunately
in the process, it added a filter to the generic p2m_flush_table()
function so that the p2m would only be flushed if it was being used as
a nested p2m. This