[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH RFC v2 09/12] xen/arm: Data abort exception (R/W) mem_events.
On Fri, Aug 29, 2014 at 11:41 PM, Julien Grall <julien.grall@xxxxxxxxxx> wrote: Hello Tamas, The Radix tree is only updated in the caller in if this function returns 1. In the next iteration of the series I already added a separate function for this, p2m_set_entry which doesn't lock so p2m_lookup will be unchanged. [..] It really only happened because of large pages in the table, as I was passing paddr inputs based on 4k page boundaries. I already started working on shattering the large pages as I'm setting the permissions so this will go away in the next iteration.
Ack.
Ack.
I would need to adjust this function in the x86 side as well where I think it may be returning -errno if something is wrong.
I didn't add it in this iteration yet (and n2rwx, rx2rw are also missing). I have them already in the next iteration which I will be sending in Monday after I go back to my office to reset my hung arndale to test it :-)
Ack.
Just in case I guess? I'm not entirely certain, this is pretty much just copy-pasta from the x86 side.
Ack.
They were bool_t inputs into the function passed from the trap handler in traps.c. In the next iteration they are going away and will be using the new combined struct npfec input from my other patch that just landed in staging.
Ack.
I'm not to happy with this either but that's what the x86 side is doing too. I would prefer it retrying to deliver the notification but keeping the offending domain paused in the meanwhile. Not entirely sure how to go about that though as I assume if xzalloc fails we have other things to worry about already.
Ack.
Thanks! Tamas _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |