All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mgross@linux.intel.com
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: 2.6.23-mm1 breaks C-state support on Intel T7200 x86_64
Date: Thu, 8 Nov 2007 12:15:36 -0800	[thread overview]
Message-ID: <20071108121536.8eeafb62.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071108200352.GA5538@linux.intel.com>

> On Thu, 8 Nov 2007 12:03:52 -0800 Mark Gross <mgross@linux.intel.com> wrote:
> ...
> > >   call.
> > > 
> > > I shouldn't have to have a process open a /dev/file, write a number, and then
> > > stay around forever so the file doesn't close in order to get the same behavior
> > > I was getting by default before.  What needs to happen to get this to not
> > > be a behavior regression/change?
> > > 
> > 
> > That's a great report, thanks.  Over to you, Mark ;)
> > 
> > btw, I also have a note here that these patches caused Rafael to see an
> > smp_call_function() inside local_irq_save().  Did that get fixed?
> 
> Ah, I see the problem.  I think I posted a fix to this.  The problem is
> that what's in the mm1 tree has a parameter PM_QOS_IDLE that needed to
> be PM_QOS_CPU_DMA_LATENCY. 

That doesn't ring a bell.

> I'm not sure what's in the current MM tree at this point so I can't say
> its been fixed.  Is there an easy way from me to see what's currently in
> MM?  

Not terribly. 
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/mm/broken-out-2007-11-06-02-32.tar.gz
is from two days ago.

> FWIW I think I fixed this when I fixed up Rafael's issue.  Would you
> like me to send out a re-fresh patch against 2.6.23-mm1?

sure.

  reply	other threads:[~2007-11-08 20:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08 17:19 2.6.23-mm1 breaks C-state support on Intel T7200 x86_64 Valdis.Kletnieks
2007-11-08 18:02 ` Andrew Morton
2007-11-08 20:03   ` Mark Gross
2007-11-08 20:15     ` Andrew Morton [this message]
2007-11-08 18:07 ` Mark Gross
2007-11-08 22:30 ` Mark Gross
2007-11-09 20:24   ` Valdis.Kletnieks
2007-11-12  4:26     ` mark gross

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=20071108121536.8eeafb62.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgross@linux.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.