[Xen-ia64-devel] pv_ops: intrinsic ops2

["Dong, Eddie" <eddie.dong@xxxxxxxxx>]

In current patch series, we have many definition:

+#define ia64_itci                      ia64_native_itci
+#define ia64_itcd                      ia64_native_itcd
+#define ia64_itri                      ia64_native_itri
+#define ia64_itrd                      ia64_native_itrd
+#define ia64_tpa                       ia64_native_tpa
+#define ia64_set_ibr                   ia64_native_set_ibr
+#define ia64_set_pkr                   ia64_native_set_pkr
+#define ia64_set_pmc                   ia64_native_set_pmc
+#define ia64_set_pmd                   ia64_native_set_pmd
+#define ia64_set_rr                    ia64_native_set_rr
+#define ia64_get_cpuid                 ia64_native_get_cpuid
+#define ia64_get_ibr                   ia64_native_get_ibr
+#define ia64_get_pkr                   ia64_native_get_pkr
+#define ia64_get_pmc                   ia64_native_get_pmc
+#define ia64_get_pmd                   ia64_native_get_pmd



    Which comes from gcc_intrin.h such as:

-#define ia64_itci(addr)        asm volatile ("itc.i %0;;" :: "r"(addr)
: "memory")
+#define ia64_native_itci(addr) asm volatile ("itc.i %0;;" :: "r"(addr)
: "memory")



        The question is we actually don't have xen_itci in the whole
patch, should
we remove the indirect reference of "new
ia64_itci-->ia64_native_itci->old_ia64_itci".
        It is just identical and the change is redunadnt at least for
this moment.

Thanks, eddie

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