RE: [Xen-ia64-devel] update linux kernels w/ xen-ia64 cset 9275

["Xu, Anthony" <anthony.xu@xxxxxxxxx>]

Difference is, sometimes it will crash dom0,
Sometimes it will not.
The best way to check it is to see whether xen_fc is called
inside dom0.

Thanks,
-Anthony 

>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Xu, Anthony
>Sent: 2006年3月17日 10:56
>To: Alex Williamson
>Cc: xen-ia64-devel
>Subject: RE: [Xen-ia64-devel] update linux kernels w/ xen-ia64 cset 9275
>
>Alex,
>
>I am using 9268.
>But I think all versions are using privified instructions,
>because this code is in sparse tree.
>
>Pls refer to inux-2.6-xen-sparse/include/asm-ia64/xen/privop.h
>extern unsigned long xen_fc(unsigned long addr);
>#define ia64_fc(addr)           xen_fc((unsigned long)(addr))
>extern unsigned long xen_thash(unsigned long addr);
>#define ia64_thash(addr)        xen_thash((unsigned long)(addr))
>
>Thanks,
>-Anthony
>
>>-----Original Message-----
>>From: Alex Williamson [mailto:alex.williamson@xxxxxx]
>>Sent: 2006年3月17日 10:46
>>To: Xu, Anthony
>>Cc: You, Yongkang; xen-ia64-devel
>>Subject: RE: [Xen-ia64-devel] update linux kernels w/ xen-ia64 cset 9275
>>
>>On Fri, 2006-03-17 at 10:34 +0800, Xu, Anthony wrote:
>>> Alex/ Tristan
>>>
>>> Legacy privifiedinsns is being used; please turn on it by default.
>>> Pls refer to the attachment.
>>
>>Anthony,
>>
>>   The specific example cited is fixed in xen-ia64 9274.  Are there
>>other examples of where privified instructions are still in use?
>>Thanks,
>>
>>      Alex
>>--
>>Alex Williamson                             HP Linux & Open Source Lab
>
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel

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