cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: "Yu, Luming" <luming.yu@intel.com>,
	cpufreq <cpufreq@www.linux.org.uk>,
	"Yu, Fenghua" <fenghua.yu@intel.com>
Subject: Re: [PATCH] Eliminate cpufreq_userspace scaling_setspeed deadlock
Date: Tue, 20 Nov 2007 18:41:33 -0500	[thread overview]
Message-ID: <20071120234132.GA9882@redhat.com> (raw)
In-Reply-To: <924EFEDD5F540B4284297C4DC59F3DEE15F13A@orsmsx423.amr.corp.intel.com>

On Wed, Nov 07, 2007 at 10:45:35PM -0800, Venki Pallipadi wrote:
 >  
 > 
 > >-----Original Message-----
 > >From: Mattia Dongili [mailto:malattia@linux.it] 
 > >Sent: Wednesday, November 07, 2007 4:57 AM
 > >To: Yu, Luming
 > >Cc: Pallipadi, Venkatesh; Dave Jones; Yu, Fenghua; cpufreq
 > >Subject: Re: [PATCH] Eliminate cpufreq_userspace 
 > >scaling_setspeed deadlock
 > >
 > >On Mon, Nov 05, 2007 at 04:58:18PM +0800, Yu, Luming wrote:
 > >> Based on my current testing results, this patch fixes my problem.
 > >> Please help push it upstream.
 > >
 > >BTW, this will break some userspace apps. I can think of cpufrequtils
 > >and some deamons that use the userspace governor to set frequencies.
 > >
 > 
 > Yes. But, this is the only solution we have for the deadlock right now
 > and I think it should goto upstream as soon as possible, unless we have
 > some better alternative. Userspace breakage is better bargain than a
 > kernel deadlock. Isn't it :-).

I'm torn over this patch.  I don't see a better way to fix this either,
but the potential for breaking userspace is there. I think I'm going to
merge this, and see how things go in -mm for a while.

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-11-20 23:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26 17:18 [PATCH] Eliminate cpufreq_userspace scaling_setspeed deadlock Venki Pallipadi
2007-11-05  8:58 ` Yu, Luming
2007-11-07 12:56   ` Mattia Dongili
2007-11-08  6:45     ` Pallipadi, Venkatesh
2007-11-20 23:41       ` Dave Jones [this message]
2007-11-21  3:04         ` claudio
2007-11-26 17:40           ` Pallipadi, Venkatesh
2007-11-27 21:11             ` Mauro 'Kenny' Freitas
2007-11-21 12:02         ` Mattia Dongili
2007-11-26 13:05           ` Claudio Eduardo

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=20071120234132.GA9882@redhat.com \
    --to=davej@redhat.com \
    --cc=cpufreq@www.linux.org.uk \
    --cc=fenghua.yu@intel.com \
    --cc=luming.yu@intel.com \
    --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