All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: Ashok Raj <ashok.raj@intel.com>,
	Petr Vandrovec <vandrove@vc.cvut.cz>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: powernow-k8 schedules in atomic since sunday :-(
Date: Sat, 5 Nov 2005 23:13:19 -0500	[thread overview]
Message-ID: <20051106041319.GD4046@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0511051643520.1526@montezuma.fsmlabs.com>

On Sat, Nov 05, 2005 at 05:13:07PM -0800, Zwane Mwaikambo wrote:
 > On Thu, 3 Nov 2005, Ashok Raj wrote:
 > 
 > > On Thu, Nov 03, 2005 at 05:03:17PM +0100, Petr Vandrovec wrote:
 > > > Hello Ashok,
 > > >    your change '[PATCH] create and destroy cpufreq sysfs entries based on cpu 
 > > > notifiers' causes problems with powernow-k8 driver.  powernow-k8 uses 
 > > > set_cpus_allowed() (it even calls schedule() explicitly for no reason), and when 
 > > > you've changed code from lock_cpu_hotplug() to preempt_disable() 
 > > > set_cpus_allowed() now complains that schedule() is not allowed while preemption 
 > > > is disabled...
 > 
 > Hmm i submitted a patch 
 > (http://groups.google.ca/group/fa.linux.kernel/browse_frm/thread/ec079d77dc1f6e80/edf10a39eede6246?tvc=1&q=Remove+p$ 
 > to remove those superfluous schedules, but perhaps it hasn't hit Linus' 
 > tree yet via Davej.

I sent Linus a pull request last week, but I did it at the same
time osdl's mailserver had issues aparently.

I resent another request earlier this afternoon.

		Dave


      reply	other threads:[~2005-11-06  4:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03 16:03 powernow-k8 schedules in atomic since sunday :-( Petr Vandrovec
2005-11-03 20:49 ` Ashok Raj
2005-11-06  1:13   ` Zwane Mwaikambo
2005-11-06  4:13     ` Dave Jones [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=20051106041319.GD4046@redhat.com \
    --to=davej@redhat.com \
    --cc=ashok.raj@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vandrove@vc.cvut.cz \
    --cc=zwane@arm.linux.org.uk \
    /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.