linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Jan Beulich <jbeulich@novell.com>
Cc: gary.hade@us.ibm.com, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Avoid creating P2P prefetch window for expansion ROMs
Date: Tue, 20 Nov 2007 15:14:53 -0800	[thread overview]
Message-ID: <20071120231453.GA20462@suse.de> (raw)
In-Reply-To: <4742C9D7.76E4.0078.0@novell.com>

On Tue, Nov 20, 2007 at 03:49:43AM -0700, Jan Beulich wrote:
> This patch (in its incarnation in our SLE10SP2 tree) is causing resource
> allocation failures on one of my machines.

Does the latest 2.6.23 kernel also cause these same problems?

> The condition for this is that besides ROMs behind a bridge not having
> their base addresses assigned there's no extra space available in the
> non-prefetch window to accommodate the ROMs' space. I therefore think
> the change, while having a good reason, isn't complete so far, as it
> would imply the need for checking whether space in the non-prefetch
> window is sufficient and continuing to force the creation of a
> prefetch window otherwise.

Hm, I'll defer to Gary on this one :)

thanks,

greg k-h

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20 10:49 Avoid creating P2P prefetch window for expansion ROMs Jan Beulich
2007-11-20 23:14 ` Greg KH [this message]
2007-11-21  8:53   ` Jan Beulich
     [not found] <4742CB2C.76E4.0078.0@novell.com>
     [not found] ` <20071120174945.GA6024@us.ibm.com>
     [not found]   ` <47440D1F.76E4.0078.0@novell.com>
2007-11-26 21:59     ` Gary Hade
2007-11-26 22:15       ` Greg KH
2007-11-26 22:46         ` Gary Hade
2007-12-12  1:08         ` Gary Hade
2007-11-27  9:28       ` Jan Beulich
2007-11-27 19:17         ` Gary Hade

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=20071120231453.GA20462@suse.de \
    --to=gregkh@suse.de \
    --cc=gary.hade@us.ibm.com \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).