On 09/01/2017 06:07 PM, Andrew Cooper wrote:
> Having all of this logic together makes it easier to follow Xen's virtual
> setup across the whole system.
>
> No practical changes to the resulting L4, although the logic has been
> rearanged to avoid rewriting some slots. This changes the zap_ro_mp
>>> On 04.09.17 at 12:42, wrote:
> On 04/09/17 11:09, Jan Beulich wrote:
> On 01.09.17 at 19:07, wrote:
>>> Having all of this logic together makes it easier to follow Xen's virtual
>>> setup across the whole system.
>>>
>>> No practical changes to the resulting L4, although the logic has bee
On 04/09/17 11:09, Jan Beulich wrote:
On 01.09.17 at 19:07, wrote:
>> Having all of this logic together makes it easier to follow Xen's virtual
>> setup across the whole system.
>>
>> No practical changes to the resulting L4, although the logic has been
>> rearanged to avoid rewriting some sl
>>> On 01.09.17 at 19:07, wrote:
> Having all of this logic together makes it easier to follow Xen's virtual
> setup across the whole system.
>
> No practical changes to the resulting L4, although the logic has been
> rearanged to avoid rewriting some slots. This changes the zap_ro_mpt
> paramet
On 03/09/17 13:01, Tim Deegan wrote:
> At 18:07 +0100 on 01 Sep (1504289261), Andrew Cooper wrote:
>> if ( unlikely(root_pgt_pv_xen_slots < ROOT_PAGETABLE_PV_XEN_SLOTS) )
>> {
>> -l4_pgentry_t *next = &l4tab[ROOT_PAGETABLE_FIRST_XEN_SLOT +
>> -r
At 18:07 +0100 on 01 Sep (1504289261), Andrew Cooper wrote:
> if ( unlikely(root_pgt_pv_xen_slots < ROOT_PAGETABLE_PV_XEN_SLOTS) )
> {
> -l4_pgentry_t *next = &l4tab[ROOT_PAGETABLE_FIRST_XEN_SLOT +
> -root_pgt_pv_xen_slots];
> +/*
> +
Having all of this logic together makes it easier to follow Xen's virtual
setup across the whole system.
No practical changes to the resulting L4, although the logic has been
rearanged to avoid rewriting some slots. This changes the zap_ro_mpt
parameter to simply ro_mpt. Another side effect is t
