Re: Why kernel space begins at 3GB
From: gopan (gop_kumar_at_hotmail.com)
Date: 06/14/04
- Next message: Giorgos Momferratos: "system call returning memory usage?"
- Previous message: nick_faye: "redirecting driver printk messages to specific file"
- In reply to: John Reiser: "Re: Why kernel space begins at 3GB"
- Next in thread: John Reiser: "Re: Why kernel space begins at 3GB"
- Reply: John Reiser: "Re: Why kernel space begins at 3GB"
- Reply: Doug Gale: "Re: Why kernel space begins at 3GB"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 14 Jun 2004 03:24:36 -0700
> If the target addresses are less than 0x10000, then an indirect
> CALL or JMP instruction can use an x86 address size prefix (0x67)
> to make the table entries only 2 bytes wide, even in 32-bit code.
Can u please elaborate this point, or atleast give a hint as to
where I can find more info about the same.
- Next message: Giorgos Momferratos: "system call returning memory usage?"
- Previous message: nick_faye: "redirecting driver printk messages to specific file"
- In reply to: John Reiser: "Re: Why kernel space begins at 3GB"
- Next in thread: John Reiser: "Re: Why kernel space begins at 3GB"
- Reply: John Reiser: "Re: Why kernel space begins at 3GB"
- Reply: Doug Gale: "Re: Why kernel space begins at 3GB"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]