[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH for-3.0] target/arm: Correctly handle overlappin
Re: [Qemu-devel] [PATCH for-3.0] target/arm: Correctly handle overlapping small MPU regions
Tue, 17 Jul 2018 20:40:23 +0100
On 17 July 2018 at 18:29, Richard Henderson
> I don't understand why this is necessary in the v8m case.
> AP APL
> Your comment posits two regions [B1,L1] and [B2,L2], that A is not within
> [B1,L1] but is within [B2,L2] (otherwise we would not report a hit at all).
> Further, that [B1,L1] intersects [AP,APL] but does not intersect [B2,L2]
> (otherwise we would report a fault for overlapping regions).
> Surely this combination of ranges implies that [B2,L2] must itself set
> IS_SUBPAGE (otherwise the first region would not overlap the page of A, or
> would not overlap the second region).
(a) the overlap fault is only for addresses which are actually in the
overlap (ie "you asked about address X and it hits in R1 and R2"); it
doesn't imply that other addresses which are only in R1 fault just
because some part of R1 overlaps with R2. So for instance:
we must report a narrowed page for address A1, even though
it hits only within one region (B1-L1) which covers the
full page which A1 is within. (Otherwise if we later access
A2 then we'll get the TLB entry for A1, rather than reporting
the fault for it being in 2 regions.)
(b) Consider the case where one of the regions is the "background
region" that you get if you don't hit on anything.