Re: Red zones

From: Bernd Eckenfels
Date: Thu Jan 26 2006 - 05:05:46 EST


Eric Dumazet <dada1@xxxxxxxxxxxxx> wrote:
> On x86_64, available virtual space is huge, so having different red zones can
> spot the fault more easily : If the target of the fault is in the PER_CPU
> redzone given range, we can instantly knows there is still a per_cpu() user
> accessing a non possible cpu area. As the red zone is not mapped at all, no
> page table is setup.

Ok, however you can also tell from the stack trace who accessed the red zone, right?

Gruss
Bernd
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/