Re: copy to suer space

["Hua Zhong" <hzhong@cisco.com>]

Why not SIGSTOP/SIGCONT instead?

I don't see any reason why you should change the code segment (reminded me
some ugly Windows hacks of changing DLL entries).

----- Original Message -----
From: "Luís Henriques" <lhenriques@criticalsoftware.com>
To: "Andreas Dilger" <adilger@turbolabs.com>
Cc: "Anton Altaparmakov" <aia21@cam.ac.uk>; <linux-kernel@vger.kernel.org>
Sent: Tuesday, November 20, 2001 10:44 AM
Subject: Re: copy to suer space


>
> > Maybe if you describe the actual problem that you are trying to solve,
and
> > not the actual way you are trying to solve it, there may be a better
> > method. Usually, if something you are trying to do is very hard to do,
> > there is a different (much better) way of doing it.
> >
> > Cheers, Andreas
>
> OK, here it goes:
>
> I'm developping a kernel module that needs to delay a process, that is, he
> receives a PID and, when a specific event occurs, that process shall be
> delayed. This delay shall be done in a way that the process keeps burning
CPU
> time (it can not be, e.g., put in a waiting-list...).
> The solution I found was to change its code segment, putting a loop in it.
> After a specified period of time, the original code must be restored and
the
> process must keep going as nothing happened.
> The main problem I found was already explained: can't write to the CS!
>
> --
> Luís Henriques
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/