Re: BookE "branch taken" behavior vis-a-vis updating the NIP register

2013-11-11 Thread pegasus
I re-read the link you posted earlier and this time it made more sense to me. The kind of questions which are coming into my mind were being discussed. So, off I went and downloaded the latest version of arch/powerpc/kernel/traps.c hoping to see those very changes in them. However it didn't match

Re: BookE "branch taken" behavior vis-a-vis updating the NIP register

2013-11-10 Thread pegasus
Thanks James. So it means that, the NIP that I am seeing in the printks is indeed correct. Right? And this is due to the pipelining feature that is inherent in all processors. So it basically means that after having executed the branch, the NIP has already progressed to the next instruction it is

BookE "branch taken" behavior vis-a-vis updating the NIP register

2013-11-08 Thread pegasus
Hello. I was reading the source code for the debug exception under powerpc. I saw that BookE processors stop before (actually) taking a branch. Hence in order to force it to take that branch and then stop, the source code for it had to be "hacked' to (temporarily) enable single step until the bra

Re: Understanding how kernel updates MMU hash table

2012-12-13 Thread pegasus
Hi Ben There has been quite much confusion with my post disappearing from the new nabble system to it having getting posted twice..Im sorry for all this. Nevertheless, Id like to continue where we left off. Here I again repost my response which initially disappeared and then showed up twice. Ive