[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH V13 4/7] xen/arm: Data abort exception (R/W) mem_events.
On Thu, Mar 12, 2015 at 2:35 PM, Ian Campbell <ian.campbell@xxxxxxxxxx> wrote: On Fri, 2015-03-06 at 22:24 +0100, Tamas K Lengyel wrote: Ack, this is a bit awkward here. If mem_access is not enabled, the access type passed here is always p2m_access_rwx, thus the tree wasn't updated/maintained. I'll make it more explicit by moving the check for p2m->mem_access_enabled up front to return 0 if not enabled.. Â
I don't think it would make it any easier to read if abstracted. I rather keep it this way. Â
Hm, yea it's not actually required. Â
Right, it's not a bugfix and not required to be outside the loop, I think I just moved it because it made sense to me to flush it only once instead at every iteration. I'll place it back. Â
It's different because of how the x86 code is structured. In ARM it is a bit more straight forward thus the prototype is simpler. The function doesn't get called from common, so arch specific discrepancies are OK. Â
Not without introducing another wrapper around them. The mem_event_emulate_check in x86 takes mem_event_response_t as input, here we take npfec. While the logic applied afterwards is similar, I would rather do consolidation like that once this series and the other cleanup series are both applied. Â
Could be but for now I rather keep them separate. Â
This is actually a bit different. On x86 the request is just being setup here and sent only later, while on ARM we can actually send it right away. I had made an attempt before to consolidate these two, but the x86 side required some heavy cleanup before that was possible so it got postponed to happen after the mem_event API itself is cleaned up. Â
Nearly, but not completely. IMHO consolidation may be possible on some of these bits, but I'm not sure if it would make it any easier to follow when the code jumps back and forth between common and arch specific parts. Â
What do you mean twice? One is converting from p2m_access to XENMEM_access, the other is XENMEM_access to p2m_access. Â
~0ull is specifically used by the mem_access API for this purpose. If anywhere, in the cleanup series it might make sense to have a #define added for it. Â
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 |