From: "Marco C. Mason" <mason@ntr.net>
To: umiguel@alunos.deis.isec.pt, linux-kernel@vger.kernel.org
Subject: Re: copy to user
Date: Sun, 25 Nov 2001 16:58:42 -0500 [thread overview]
Message-ID: <3C016992.8C564A96@ntr.net> (raw)
Luis Henriques--
Before making my suggestion: Apologies to the list if this has already
been settled. I'm trying to catch up on my LKML reading, and I'm only
up to Nov 20 so far...
Anyway: Here's what I'd do, if I had to do such a apalling thing 8^)
Drop a function in your code something like:
_xyzzy:
db 0x18, 0xfe ; jr $
Then, when you detect the condition where you want to waste time, then
put the address of this function on top of the user stack (along with
whatever else in the stack frame is required) so that the code just sits
there burning CPU. To clean it up, you'd simply restore the original
stack frame to the process.
It's hideous & gross, but if you need it.....
--marco
next reply other threads:[~2001-11-25 21:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-25 21:58 Marco C. Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-20 20:54 copy to user Luis Miguel Correia Henriques
2001-11-20 21:28 ` John Alvord
2001-11-20 21:44 ` Andreas Dilger
2001-11-21 11:02 ` Luís Henriques
2001-11-20 22:02 ` n0ano
2001-11-20 22:05 ` Chris Wright
2001-11-21 8:43 ` Mathijs Mohlmann
2001-11-21 10:12 ` Jan Hudec
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=3C016992.8C564A96@ntr.net \
--to=mason@ntr.net \
--cc=linux-kernel@vger.kernel.org \
--cc=umiguel@alunos.deis.isec.pt \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox