[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v3 07/13] xen/arm: Simplify alternative patching of non-writable region
Hi Konrad, On 22/06/18 14:33, Konrad Rzeszutek Wilk wrote: On Tue, Jun 12, 2018 at 11:06:16PM +0100, Julien Grall wrote:On 12/06/2018 22:17, Konrad Rzeszutek Wilk wrote:On Tue, Jun 12, 2018 at 12:36:37PM +0100, Julien Grall wrote: Won't this mean the traps (if there are any) won't be recognized at all during this patching?What do you mean by recognized? This new region will only be accessed to write instruction. The only potential fault on that region is a data abort.Exactly the data abort. My recollection is that the data abort would print a stack trace. And the stack trace needs symbol information - which it gets from virtual_region. But if virtual_region is not registered then the stack won't contain the name of the function that had an data abort as the patching is done. I am not sure to understand what you mean by "the name of the function that had a data abort". Could you give a bit more detail? Cheers, -- Julien Grall _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |