Re: [PATCH v2 4/6] arm/mpu: Destroy an existing entry in Xen MPU memory mapping table

2025-07-14 Thread Orzel, Michal
On 11/07/2025 08:04, Hari Limaye wrote: > Hi Michal, > > Thank you for reviewing the patch. > >   > >> > +    /* Zeroing the region will also zero the region enable */ > >> > +    memset(&xen_mpumap[index], 0, sizeof(pr_t)); > >> Is it ok that for a fast case (i.e. 0-31) our representation

Re: [PATCH v2 4/6] arm/mpu: Destroy an existing entry in Xen MPU memory mapping table

2025-07-10 Thread Hari Limaye
Hi Michal, Thank you for reviewing the patch. > > +/* Zeroing the region will also zero the region enable */ > > +memset(&xen_mpumap[index], 0, sizeof(pr_t)); > Is it ok that for a fast case (i.e. 0-31) our representation of prbar/prlar > will > be different from the HW i.e. xen_mpumap[in

Re: [PATCH v2 4/6] arm/mpu: Destroy an existing entry in Xen MPU memory mapping table

2025-07-09 Thread Orzel, Michal
On 02/07/2025 16:13, Hari Limaye wrote: > From: Penny Zheng > > This commit expands xen_mpumap_update/xen_mpumap_update_entry to include > destroying an existing entry. > > We define a new helper "disable_mpu_region_from_index" to disable the MPU > region based on index. If region is within [

[PATCH v2 4/6] arm/mpu: Destroy an existing entry in Xen MPU memory mapping table

2025-07-02 Thread Hari Limaye
From: Penny Zheng This commit expands xen_mpumap_update/xen_mpumap_update_entry to include destroying an existing entry. We define a new helper "disable_mpu_region_from_index" to disable the MPU region based on index. If region is within [0, 31], we could quickly disable the MPU region through P