On Monday 31 July 2006 14:15, Attilio Rao wrote:
> 2006/7/30, Divacky Roman <[EMAIL PROTECTED]>:
> > On Sun, Jul 30, 2006 at 12:57:32PM +0200, Divacky Roman wrote:
> > > hi,
> > >
> > > while working on SoC linuxolator project I am in a need of this:
> > >
> > > I need to do some operation on memor
2006/7/30, Divacky Roman <[EMAIL PROTECTED]>:
On Sun, Jul 30, 2006 at 12:57:32PM +0200, Divacky Roman wrote:
> hi,
>
> while working on SoC linuxolator project I am in a need of this:
>
> I need to do some operation on memory like mem1 = mem1 + mem2 etc.
> where the mem1/mem2 access can trigger f
[EMAIL PROTECTED] wrote:
On 31.07.2006 14:12:20, Intron wrote:
Mutex(9) is sometimes too heavy, and has many limitations, while sx(9)
is somewhat enough.
First paragraph from sx(9) manual says:
Shared/exclusive locks are used to protect data that are read
far more often than
On 31.07.2006 14:12:20, Intron wrote:
> Mutex(9) is sometimes too heavy, and has many limitations, while sx(9)
> is somewhat enough.
First paragraph from sx(9) manual says:
Shared/exclusive locks are used to protect data that are read
far more often than they are written. Mutexe
Divacky Roman wrote:
On Sun, Jul 30, 2006 at 12:57:32PM +0200, Divacky Roman wrote:
hi,
while working on SoC linuxolator project I am in a need of this:
I need to do some operation on memory like mem1 = mem1 + mem2 etc.
where the mem1/mem2 access can trigger fault. (memory not mapped or somet
From kern_umtx.c:
static int
_do_lock(struct thread *td, struct umtx *umtx, long id, int timo)
{
struct umtx_q *uq;
intptr_t owner;
intptr_t old;
int error = 0;
uq = td->td_umtxq;
/*
* Care must be exercised when dealing with umtx structure. It
On Sun, Jul 30, 2006 at 12:57:32PM +0200, Divacky Roman wrote:
> hi,
>
> while working on SoC linuxolator project I am in a need of this:
>
> I need to do some operation on memory like mem1 = mem1 + mem2 etc.
> where the mem1/mem2 access can trigger fault. (memory not mapped or something)
to mak
Divacky Roman wrote:
hi,
while working on SoC linuxolator project I am in a need of this:
I need to do some operation on memory like mem1 = mem1 + mem2 etc.
where the mem1/mem2 access can trigger fault. (memory not mapped or something)
currently I solve this by using pcb_onfault. this must be
On Sun, 2006-Jul-30 12:57:32 +0200, Divacky Roman wrote:
>while working on SoC linuxolator project I am in a need of this:
>
>I need to do some operation on memory like mem1 = mem1 + mem2 etc.
>where the mem1/mem2 access can trigger fault. (memory not mapped or something)
This is normally only an
hi,
while working on SoC linuxolator project I am in a need of this:
I need to do some operation on memory like mem1 = mem1 + mem2 etc.
where the mem1/mem2 access can trigger fault. (memory not mapped or something)
currently I solve this by using pcb_onfault. this must be done in asm (kib@
told
10 matches
Mail list logo
