"...The NT flag indicates that the previous task link field of the TSS
has been loaded with a saved TSS segment selector. If software
uses an IRET instruction to suspend the new task, the processor uses the
value in the previous task link field and the NT flag to return to the
previous task; that is, if the NT flag is set, the processor performs a
task switch to the task specified in the previous task link field."
"If the task switch was initiated with an exception, or an interrupt,
the processor sets the NT flag in the EFLAGS image stored in the new
task’s TSS;"
Intel Architecture Software Developer’s Manual Volume 3: System
Programming
Not sure I need to clear the NT flag.
my page fault handler:
static void pagefault_fn(void)
{
unsigned int address, aligned_page_fault_address;
struct vm_struct *area;
/* retrieve the page fault address */
__asm__("movl %%cr2,%0":"=r" (address));
aligned_page_fault_address = ((address+PAGE_SIZE)&(~(4096-1)));
area = find_vm_area((void*)(aligned_page_fault_address));
/* allocate a new physical page, expand the stack size */
expend_stack_size(area);
// asm ("pushf; orl $0x00004000, (%esp); popf; iret"); /* sets NT */
// asm ("pushf; andl $0xffffbfff, (%esp); popf; iret"); /* clears NT */
asm ("iret");
}
On Wed, 2005-06-29 at 16:09, Ingo Molnar wrote:
> * eliad lubovsky <[email protected]> wrote:
>
> > I am trying to handle page faults exceptions in the kernel using the
> > task gate mechanism. I succeeded to transfer the execution to my page
> > fault handler using a new TSS and updates to the GDT and IDT tables
> > (similar to the double fault mechanism in 2.6). After handling the
> > fault and allocating the physical page I use the iret instruction to
> > switch back to the previous task. The problem is that I got a double
> > fault with the same address that cause the fault (although the
> > physical page is allocated and mapped). Any clues?
>
> are you clearing the 'nested task' (NT) flag of the new TSS once you
> have switched to it?
>
> Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
