Re: [PATCH v6 05/24] arm/x86: Use struct virtual_region to do bug, symbol, and (x86) exception tables lookup.

[Julien Grall <julien.grall@arm.com>]

Hi Konrad,

On 07/04/16 04:49, Konrad Rzeszutek Wilk wrote:
> During execution of the hypervisor we have two regions of
> executable code - stext -> _etext, and _sinittext -> _einitext.
>
> The later is not needed after bootup.
>
> We also have various built-in macros and functions to search
> in between those two swaths depending on the state of the system.
>
> That is either for bug_frames, exceptions (x86) or symbol
> names for the instruction.
>
> With xSplice in the picture - we need a mechansim for new payloads

NIT: s/mechansim/mechanism/

> to searched as well for all of this.
>
> Originally we had extra 'if (xsplice)...' but that gets
> a bit tiring and does not hook up nicely.
>
> This 'struct virtual_region' and virtual_region_list provide a
> mechanism to search for the bug_frames, exception table,
> and symbol names entries without having various calls in
> other sub-components in the system.
>
> Code which wishes to participate in bug_frames and exception table
> entries search has to only use two public APIs:
>   - register_virtual_region
>   - unregister_virtual_region
>
> to let the core code know.
>
> If the ->lookup_symbol is not then the default internal symbol lookup
> mechanism is used.
>
> Suggested-by: Andrew Cooper <andrew.cooper3@citrix.com>
> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

For the ARM parts:

Acked-by: Julien Grall <julien.grall@arm.com>

Regards,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel