Re: [discuss] [patch] x86_64: align and pad x86_64 GDT on page boundary

On Thu, Dec 08, 2005 at 09:15:18PM +0100, Andi Kleen wrote:
> On Thu, Dec 08, 2005 at 11:42:32AM -0800, Ravikiran G Thirumalai wrote:
> >  
> > -	.align  L1_CACHE_BYTES
> > +	/* zero the remaining page */
> > +	.fill PAGE_SIZE / 8 - GDT_ENTRIES,8,0
> > +	
> >  ENTRY(idt_table)	
> 
> Why can't the IDT not be shared with the GDT page? It should be mostly
> read only right and putting r-o data on that page should be ok, right?

Yes, you are right.  This should not have been a problem.  
Some people reported this symbol (cpu_gdt) though.  Will have to go back and
check.

Thanks,
Kiran
-
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/

---

• Follow-Ups:
  • Re: [discuss] [patch] x86_64: align and pad x86_64 GDT on page boundary
    • From: Rohit Seth <[email protected]>

• References:
  • [patch] x86_64: align and pad x86_64 GDT on page boundary
    • From: Ravikiran G Thirumalai <[email protected]>
  • Re: [discuss] [patch] x86_64: align and pad x86_64 GDT on page boundary
    • From: Andi Kleen <[email protected]>

• Prev by Date: Re: set_page_dirty vs set_page_dirty_lock
• Next by Date: Re: Driver bind/unbind and __devinit
• Previous by thread: Re: [discuss] [patch] x86_64: align and pad x86_64 GDT on page boundary
• Next by thread: Re: [discuss] [patch] x86_64: align and pad x86_64 GDT on page boundary
• Index(es):
  • Date
  • Thread

[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]