[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DE8DF0795D48FD4CA783C40EC829233509F044@SHSMSX101.ccr.corp.intel.com>
Date: Fri, 17 Feb 2012 17:59:56 +0000
From: "Liu, Jinsong" <jinsong.liu@...el.com>
To: Jan Beulich <JBeulich@...e.com>
CC: "keir.xen@...il.com" <keir.xen@...il.com>,
"Li, Shaohua" <shaohua.li@...el.com>,
xen-devel <xen-devel@...ts.xen.org>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Kerneldevelopment list <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/3] PAD helper for native and paravirt platform
>>
>> +static inline int __acpi_pad_init(void)
>> +{
>> + return PVOP_CALL0(int, pv_pad_ops.acpi_pad_init); +}
>> +
>> +static inline void __acpi_pad_exit(void)
>> +{
>> + PVOP_VCALL0(pv_pad_ops.acpi_pad_exit);
>> +}
>
> With this you, aiui, you aim at getting the calls patched. Are the
> callers of this really on performance critical paths? If not, the
> simpler approach of having an ops structure the fields of which get
> overwritten by
> Xen initialization would seem a more appropriate approach.
>
Yes, I agree. I code in this way just want to keep same coding style as other pv functions of paravirt.h.
I update the patch w/ a simpler approach, and will post later.
Of course, we need Konrad's comments.
Thanks,
Jinsong--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists