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

RE: [Xen-ia64-devel] RE: [PATCH]: disable handling of legacyprivified insns


  • To: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>, "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Tue, 21 Mar 2006 09:46:07 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 21 Mar 2006 01:47:54 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcZL8DOiK5sZg1yXTou7bdgJLeiUkwAR3MwgABQwq+A=
  • Thread-topic: [Xen-ia64-devel] RE: [PATCH]: disable handling of legacyprivified insns

>From: Magenheimer, Dan (HP Labs Fort Collins)
>Sent: 2006年3月21日 0:09
>
>> The Linux kernel doesn't use the break instructions for
>> itself, does it ?
>
>I don't know about current kernels, but certainly in past
>Linux/ia64 kernels, Linux uses break instructions.  If I
>recall correctly, launching a kernel thread required a
>pl0 system call via a break instruction.

Latest code has no that 'break' for kernel thread creation.

>
>> So, if I am correct the linux kernel could use break insns
>> without ic=0/ic=1
>> for hyperprivops.
>>
>> I really think this could work for linux.
>> What about other OS ?  I don't see why they would use break
>> in kernel mode.
>> The only exception may be debugger/single stepping.
>
>I agree a kernel debugger might use break instructions
>with pl=0.

Yes current linux kernel definitely uses 'break', like kdb, kprobe, jprobe, 
etc. See include/asm-ia64/break.h.

Thanks,
Kevin

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


 


Rackspace

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