Long ago, On Mon, 17 Feb 2003, Jake Burkholder wrote:
[I quoted everything since this thread is so old. My main point is at
the end. It restarts and older part of this thread.]
> > Can you explain how fuswintr() and suswintr() work on sparc64's? They
> > seem to cause traps if the user counter
>
> Can you explain how fuswintr() and suswintr() work on sparc64's? They
> seem to cause traps if the user counter is not mapped, and I can't see
> where the traps are handled. ia64/trap.c has a comment about where these
> traps are handled, but has dummies for fuswintr() and suswintr() so the
On Sun, 16 Feb 2003, Julian Elischer wrote:
> On Mon, 17 Feb 2003, Bruce Evans wrote:
>
> > On Sun, 16 Feb 2003, Julian Elischer wrote:
> >
> > > In addupc_intr, if the increment cannot be done immediatly, the addres
> > > to increment the count for is stored and the increment is done later at
> >
On Mon, 17 Feb 2003, Jake Burkholder wrote:
> Apparently, On Mon, Feb 17, 2003 at 05:35:09PM +1100,
> Bruce Evans said words to the effect of;
> > ... Also, ast() doesn't
> > have access to the frame, and there is no macro like CLKF_PC() for
> > general frames. This probably doesn't matter
On Mon, 17 Feb 2003, Bruce Evans wrote:
> On Sun, 16 Feb 2003, Julian Elischer wrote:
>
> > In addupc_intr, if the increment cannot be done immediatly, the addres
> > to increment the count for is stored and the increment is done later at
> > ast or userret() time...
>
> Note that "cannot be d
Apparently, On Mon, Feb 17, 2003 at 05:35:09PM +1100,
Bruce Evans said words to the effect of;
> On Sun, 16 Feb 2003, Julian Elischer wrote:
>
> > In addupc_intr, if the increment cannot be done immediatly, the addres
> > to increment the count for is stored and the increment is done late
On Sun, 16 Feb 2003, Julian Elischer wrote:
> In addupc_intr, if the increment cannot be done immediatly, the addres
> to increment the count for is stored and the increment is done later at
> ast or userret() time...
Note that "cannot be done immediatly" is "always except on sparc64's"
under Fre
In addupc_intr, if the increment cannot be done immediatly, the addres
to increment the count for is stored and the increment is done later at
ast or userret() time...
is there any reason that the address of the PC needs to be stored?
why is the address from the frame at that time not useable?
