From: Andre Przywara <andre.przywara@amd.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel <xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH] RFC: Linux: disable APERF/MPERF feature in PV kernels
Date: Wed, 23 May 2012 11:52:57 +0200 [thread overview]
Message-ID: <4FBCB379.90908@amd.com> (raw)
In-Reply-To: <4FBCCD76020000780008569E@nat28.tlf.novell.com>
On 05/23/2012 11:43 AM, Jan Beulich wrote:
>>>> On 23.05.12 at 11:14, Andre Przywara<andre.przywara@amd.com> wrote:
>> On 05/23/2012 09:34 AM, Jan Beulich wrote:
>>> Next I'd like to note that in our kernels we simply don't build
>>> arch/x86/kernel/cpu/sched.o. Together with CPU_FREQ being
>>> suppressed, there's no consumer of the feature flag in our
>>> kernels.
>>
>> With "our kernels" you mean OpenSuSE/SLES kernels? I quickly checked
>> upstream as well as the repos on kernel.opensuse.org. In all of them
>> sched.o is unconditionally included in the Makefile.
>> So is there a build patch to exclude this file for builds of distro Xen
>> kernels?
>
> Did you perhaps overlook
>
> disabled-obj-$(CONFIG_XEN) := hypervisor.o mshyperv.o perfctr-watchdog.o \
> perf_event.o sched.o vmware.o
>
> in that very Makefile?
No, I just utterly ignored it ;-)
Thanks for the hint.
But this works only for SuSE since you build different kernels for Xen
and without Xen, right?
Starting with 3.x I now have only a single kernel image which I use for
both native and as Dom0.
So the patch to disable APERFMPERF is still useful, at least for
upstream, right?
Regards,
Andre.
--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
next prev parent reply other threads:[~2012-05-23 9:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 16:07 [PATCH] RFC: Linux: disable APERF/MPERF feature in PV kernels Andre Przywara
2012-05-22 16:52 ` Jeremy Fitzhardinge
2012-05-22 17:08 ` Malcolm Crossley
2012-05-23 8:10 ` Jan Beulich
2012-05-22 20:46 ` Andre Przywara
2012-05-22 17:18 ` Konrad Rzeszutek Wilk
2012-05-22 21:02 ` Andre Przywara
2012-05-22 21:00 ` Konrad Rzeszutek Wilk
2012-05-22 22:44 ` Andre Przywara
2012-05-23 13:26 ` Konrad Rzeszutek Wilk
2012-05-24 13:24 ` Andre Przywara
2012-05-29 10:54 ` Andre Przywara
2012-05-23 7:34 ` Jan Beulich
2012-05-23 9:14 ` Andre Przywara
2012-05-23 9:43 ` Jan Beulich
2012-05-23 9:52 ` Andre Przywara [this message]
2012-05-23 10:01 ` Jan Beulich
2012-05-23 11:11 ` Andrew Cooper
2012-05-23 12:18 ` Jan Beulich
2012-05-23 13:21 ` Andrew Cooper
2012-05-23 13:31 ` Andre Przywara
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=4FBCB379.90908@amd.com \
--to=andre.przywara@amd.com \
--cc=JBeulich@suse.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).