From: Julien Grall <julien.grall@citrix.com>
To: "Wang, Wei W" <wei.w.wang@intel.com>,
Julien Grall <julien.grall@citrix.com>,
"jbeulich@suse.com" <jbeulich@suse.com>,
"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
"Dong, Eddie" <eddie.dong@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Subject: Re: [PATCH 6/9] x86/intel_pstate: the main boby of the intel_pstate driver
Date: Sun, 26 Apr 2015 15:02:35 +0200 [thread overview]
Message-ID: <553CE1EB.1080302@citrix.com> (raw)
In-Reply-To: <286AC319A985734F985F78AFA26841F78D2FC4@shsmsx102.ccr.corp.intel.com>
On 26/04/2015 05:32, Wang, Wei W wrote:
> Hi Julien,
Hi Wei,
> On 24/04/2015 20:57, Julien Grall wrote
>> On 23/04/2016 18:58, Wei Wang wrote:
>>> diff --git a/xen/include/acpi/cpufreq/processor_perf.h
>>> b/xen/include/acpi/cpufreq/processor_perf.h
>>> index d8a1ba6..ebff11d 100644
>>> --- a/xen/include/acpi/cpufreq/processor_perf.h
>>> +++ b/xen/include/acpi/cpufreq/processor_perf.h
>>> @@ -7,6 +7,7 @@
>>>
>>> #define XEN_PX_INIT 0x80000000
>>>
>>> +int intel_pstate_init(void);
>>
>> The intel pstate driver is x86 specific. Although xen/include/acpi contains
>> common headers for common code.
>
> Thanks for your comments. But I saw "int powernow_cpufreq_init(void);" is put there.
FWIW, this prototype doesn't have any implementation even on x86.
While currently some drivers (such as the x86 powernow) may define
prototype in the common header. This is wrong, the common code should
not be able to call those functions.
There is an ongoing support on ACPI for ARM (an RFC has been sent a
couple of months ago). Adding new x86 prototype in this directory
complicate the splitting. Please help us to at least avoid adding new
x86 specific prototype/code in the common code when it's possible.
We will take care of moving the current x86 prototype/code in the
arch-specific directories.
Although, I'm not a maintainer. They may have a different opinion on
this point.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-04-26 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 14:00 [PATCH 6/9] x86/intel_pstate: the main boby of the intel_pstate driver Wei Wang
2015-04-25 18:05 ` Julien Grall
2015-04-26 3:32 ` Wang, Wei W
2015-04-26 13:02 ` Julien Grall [this message]
2015-04-27 1:23 ` Wang, Wei W
2015-04-28 13:17 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=553CE1EB.1080302@citrix.com \
--to=julien.grall@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=eddie.dong@intel.com \
--cc=ian.campbell@citrix.com \
--cc=jbeulich@suse.com \
--cc=kevin.tian@intel.com \
--cc=wei.w.wang@intel.com \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.