From: Richard Hirst <rhirst@linuxcare.com>
To: John Marvin <jsm@udlkern.fc.hp.com>
Cc: parisc-linux@puffin.external.hp.com
Subject: Re: Single-stepping
Date: Thu, 16 Nov 2000 13:20:17 +0000 [thread overview]
Message-ID: <20001116132017.W32715@linuxcare.com> (raw)
In-Reply-To: <200011161244.FAA03502@udlkern.fc.hp.com>; from jsm@udlkern.fc.hp.com on Thu, Nov 16, 2000 at 05:44:55AM -0700
On Thu, Nov 16, 2000 at 05:44:55AM -0700, John Marvin wrote:
> > Current code does
> >
> > /* Nullified, just crank over the queue. */
> > task_regs(child)->iaoq[0] = task_regs(child)->iaoq[1];
> > task_regs(child)->iasq[0] = task_regs(child)->iasq[1];
> > task_regs(child)->iaoq[1] = task_regs(child)->iaoq[0] + 4;
> >
> > Does that look right to you?
>
> Yes, that is the correct way to do it (I'll assume the duplicated line
> is just a cut/paste error).
It's not duplicated (iaoq v. iasq).
> > At the moment my test harness notes IAOQ=0x100 and stops single stepping,
> > but obviously the kernel needs to enforce that.
> >
> You should also be checking the space. But yes, the kernel needs to enforce
> this for security reasons. You should be able to do it in the recovery
> counter trap handler (rather than having to test for it in the syscall
> path, which affects all processes).
I might come back to you on that when I've thought some more.
Thanks,
Richard
next prev parent reply other threads:[~2000-11-16 13:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-16 12:44 Single-stepping John Marvin
2000-11-16 13:20 ` Richard Hirst [this message]
2000-11-16 19:00 ` Single-stepping Frank Rowand
2000-11-16 20:28 ` Single-stepping Richard Hirst
-- strict thread matches above, loose matches on Subject: below --
2000-11-20 5:43 Single-stepping John Marvin
2000-11-20 6:53 ` Single-stepping Alan Modra
2000-11-20 7:24 ` Single-stepping Stan Sieler
2000-11-20 9:05 ` Single-stepping Alan Modra
2000-11-20 18:47 ` Single-stepping Stan Sieler
2000-11-16 9:01 Single-stepping John Marvin
2000-11-16 12:00 ` Single-stepping Richard Hirst
2000-11-20 3:03 ` Single-stepping Alan Modra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001116132017.W32715@linuxcare.com \
--to=rhirst@linuxcare.com \
--cc=jsm@udlkern.fc.hp.com \
--cc=parisc-linux@puffin.external.hp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.