All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Arjan van de Ven <arjan@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Venki Pallipadi <venkatesh.pallipadi@intel.com>,
	Len Brown <lenb@kernel.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: kerneloops.org report for the week of June 14 2009
Date: Tue, 23 Jun 2009 18:58:43 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0906231857450.2767@localhost.localdomain> (raw)
In-Reply-To: <200906231856.24959.rjw@sisk.pl>

On Tue, 23 Jun 2009, Rafael J. Wysocki wrote:
> The long term solution for the issue at hand is to clean up the suspend-resume
> support in cpufreq so that it doesn't do stupid things like calling
> smp_call_function_single() with interrupts disabled, but that requires someone
> (I can do it, but I need to dig through the cpufreq code for this purpose) to
> figure out how to fix it.
> 
> I'm not quite sure if there's an acceptable short term solution, though.
> 
> In principle we can do
> 
> local_irq_save()
> ...
> local_irq_restore()
> 
> around each sysdevs ->susend() and ->resume() in addition to checking the
> status of interrupts.  Would that work?

Well not really, if the function enables interrupts you run into the
same issue (interrupt service routine calls ktime_get()) again.

Thanks,

	tglx

  reply	other threads:[~2009-06-23 17:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15  0:33 kerneloops.org report for the week of June 14 2009 Arjan van de Ven
2009-06-15  5:53 ` [alsa-devel] " Takashi Iwai
2009-06-15  5:53   ` Takashi Iwai
2009-06-15  7:06 ` Stefan Schmidt
2009-06-16  7:11   ` WARN_ON's in i915_gem_tiling.c Stefan Schmidt
2009-06-16  7:11     ` Stefan Schmidt
2009-06-18 17:08 ` kerneloops.org report for the week of June 14 2009 Bob Copeland
2009-06-19  5:32   ` Arjan van de Ven
2009-06-28  9:11     ` Bob Copeland
2009-06-23 10:05 ` Thomas Gleixner
2009-06-23 11:55   ` Ingo Molnar
2009-06-23 14:50     ` Arjan van de Ven
2009-06-23 16:56     ` Rafael J. Wysocki
2009-06-23 16:58       ` Thomas Gleixner [this message]
2009-06-25 13:03   ` Pádraig Brady

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=alpine.LFD.2.00.0906231857450.2767@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=benh@kernel.crashing.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.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 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.