From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Subject: Re: [PATCH] Avoid wiping out pr->performance during preregistering
Date: Mon, 30 Mar 2009 10:04:56 +0200 [thread overview]
Message-ID: <20090330100456.319fa3c8@dhcp-lab-109.englab.brq.redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0903272113550.26419@localhost.localdomain>
On Fri, 27 Mar 2009 21:15:23 -0400 (EDT)
Len Brown <lenb@kernel.org> wrote:
> > When cpufreq driver call acpi_processor_preregister_performance() , function
> > will clean up pr->performance even if there is possibly already registered
> > other cpufreq driver. The patch fix this potential problem. It also remove
> > double checks in P domain basic validity code and move these checks to function
> > where _PSD data is captured.
> >
> > Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
> > ---
> > drivers/acpi/processor_perflib.c | 46 +++++++++++++++++--------------------
> > 1 files changed, 21 insertions(+), 25 deletions(-)
> >
>
> What failure symptom does the user see before this patch is applied?
> Does it merit backporting to .stable?
Nothing destructive, kernel ignore P-states limit requested by BIOS using
ACPI _PPC . I think this patch is not so good candidate for backporting.
Cheers
Stanislaw Gruszka
prev parent reply other threads:[~2009-03-30 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 12:41 [PATCH] Avoid wiping out pr->performance during preregistering Stanislaw Gruszka
2009-03-28 1:15 ` Len Brown
2009-03-30 8:04 ` Stanislaw Gruszka [this message]
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=20090330100456.319fa3c8@dhcp-lab-109.englab.brq.redhat.com \
--to=sgruszka@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=venkatesh.pallipadi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox