From: Borislav Petkov <bp@amd64.org>
To: Marvin <marvin24@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] cpufreq: Add APERF/MPERF support for AMD processors
Date: Thu, 1 Apr 2010 12:36:59 +0200 [thread overview]
Message-ID: <20100401103659.GB5893@aftab> (raw)
In-Reply-To: <201004011101.04420.marvin24@gmx.de>
From: Marvin <marvin24@gmx.de>
Date: Thu, Apr 01, 2010 at 11:01:04AM +0200
> > From: Mark Langsdorf <mark.langsdorf@amd.com>
> >
> > Starting with model 10 of Family 0x10, AMD processors may have
> > support for APERF/MPERF. Add support for identifying it and using
> > it within cpufreq. Move the APERF/MPERF functions out of the
> > acpi-cpufreq code and into their own file so they can easily be
> > shared.
>
> just out of interest: what are the realnames of these processors (>= Mangy-Core) ?
Well, you're going to have to wait and see. Or search the net :)
> > Signed-off-by: Mark Langsdorf <mark.langsdorf@amd.com>
> > Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
> > Reviewed-by: Thomas Renninger <trenn@suse.de>
> > ---
> > arch/x86/kernel/cpu/cpufreq/Makefile | 4 +-
> > arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c | 44 +-----------------------
> > arch/x86/kernel/cpu/cpufreq/mperf.c | 50
> > ++++++++++++++++++++++++++++ arch/x86/kernel/cpu/cpufreq/mperf.h |
> > 9 +++++
> > arch/x86/kernel/cpu/cpufreq/powernow-k8.c | 8 ++++
> > 5 files changed, 71 insertions(+), 44 deletions(-)
> > create mode 100644 arch/x86/kernel/cpu/cpufreq/mperf.c
>
> this file has no copyright or module license, thus tainting my kernel...
This is not a standalone module but only an auxiliary. How does that
taint your kernel? dmesg, .config please.
--
Regards/Gruss,
Boris.
--
Advanced Micro Devices, Inc.
Operating Systems Research Center
next prev parent reply other threads:[~2010-04-01 10:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 19:56 [-v3 PATCH 0/6] powernow-k8: Core Performance Boost and effective frequency support Borislav Petkov
2010-03-31 19:56 ` [PATCH 1/6] x86, cpu: Add AMD core boosting feature flag to /proc/cpuinfo Borislav Petkov
2010-04-09 22:18 ` [tip:x86/cpu] " tip-bot for Borislav Petkov
2010-03-31 19:56 ` [PATCH 2/6] powernow-k8: Add core performance boost support Borislav Petkov
2010-04-09 22:19 ` [tip:x86/cpu] " tip-bot for Borislav Petkov
2010-03-31 19:56 ` [PATCH 3/6] x86: Unify APERF/MPERF support Borislav Petkov
2010-04-09 22:19 ` [tip:x86/cpu] " tip-bot for Borislav Petkov
2010-05-03 23:21 ` [tip:x86/cpu] x86, cpu: Make APERF/MPERF a normal table-driven flag tip-bot for H. Peter Anvin
2010-03-31 19:56 ` [PATCH 4/6] cpufreq: Add APERF/MPERF support for AMD processors Borislav Petkov
2010-04-01 9:01 ` Marvin
2010-04-01 10:36 ` Borislav Petkov [this message]
2010-04-01 11:46 ` Marvin
2010-04-01 14:00 ` Borislav Petkov
2010-04-01 14:19 ` [-v3.1 PATCH " Borislav Petkov
2010-04-09 22:19 ` [tip:x86/cpu] x86, " tip-bot for Mark Langsdorf
2010-03-31 19:56 ` [PATCH 5/6] powernow-k8: Fix frequency reporting Borislav Petkov
2010-04-09 22:19 ` [tip:x86/cpu] " tip-bot for Mark Langsdorf
2010-05-03 13:09 ` [tip:x86/urgent] " tip-bot for Mark Langsdorf
2010-03-31 19:56 ` [PATCH 6/6] cpufreq: Unify sysfs attribute definition macros Borislav Petkov
2010-04-09 22:20 ` [tip:x86/cpu] " tip-bot for Borislav Petkov
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=20100401103659.GB5893@aftab \
--to=bp@amd64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marvin24@gmx.de \
/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.