[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] loading IDT in xen?


  • To: "Jun Koi" <junkoi2004@xxxxxxxxx>
  • From: "余上" <yusunn@xxxxxxxxx>
  • Date: Thu, 31 Jan 2008 14:56:23 +0800
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 30 Jan 2008 22:57:08 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cGjV54W7MqL/uaWYxvEHWpx2l+FoxXu5KLFczWy+1LZ8oeD3wLQiprFOTC4+xIbPHL/CdiBshg7tlo2ka8nd51cZ3t3oh226WUNEVms7O87OFOUDzNTwd/Zl6S+5FlbhhXCun/+H2T0P0LaMmN9f0EbExYy20ISl8+O0kiQWNpM=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

There is another IDTR reload in x86_32.S at line 15 , where the
protected mode IDT vectors are initialized with ignore_int handler
firstly. Then trap_init called from __xen_start will setup the formal
IDT vectors .

2008/1/31, Jun Koi <junkoi2004@xxxxxxxxx>:
> I am looking at the hypervisor code to see how Xen setup the IDT. But
> it seems that the code in protected mode reuses the real mode IDT?
>
> In arch/x86/boot/trampoline.S we have at several places:
>
> lidt bootsym(idt_48)
>
> And idt_48 is defined as:
>
> idt_48: .word 0,0,0 # base = limit = 0
>
> And in nowhere we initialize idt_48, which means idt_48 reuses real
> mode IDT table. However, real mode IDT table has different format than
> protected mode IDT, so this doesnt look to work for me.
>
> Definitely I miss something here. Anybody could enlighten me how IDT
> setting in protected mode work?
>
> Thanks,
> Jun
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.