LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Olivier Galibert <galibert@pobox.com>
To: Dave Jones <davej@codemonkey.org.uk>,
	Zhao Yakui <yakui.zhao@intel.com>,
	Li Shaohua <shaohua.li@intel.com>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Thomas Renninger <trenn@suse.de>, Len Brown <len.brown@intel.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: PNP: increase the maximum number of resources
Date: Wed, 12 Mar 2008 18:08:02 +0100	[thread overview]
Message-ID: <20080312170802.GA10606@dspnet.fr.eu.org> (raw)
In-Reply-To: <20080312151452.GA4523@codemonkey.org.uk>

On Wed, Mar 12, 2008 at 11:14:52AM -0400, Dave Jones wrote:
> In commit a7839e960675b549f06209d18283d5cee2ce9261 the number of PNP resources
> was increased.  In testing, we've found that the 'exceeded' warnings still get
> hit with quite high frequency. See https://bugzilla.redhat.com/show_bug.cgi?id=436589
> for examples.
> 
> I added the debug patch below, which yielded an interesting output.
> 
> pnpacpi: exceeded the max number of mem resources. Max:12 Found:12
> 
> off by one somewhere ?

No, your patch is just not giving out any additional information.  'i'
is the number of currently allocated resources, not the number asked
for.  That number does not exist anywhere at that point as far as I
can see, you'll have to add a counter for it.

That looks valid for every resource type btw.

  OG.


  reply	other threads:[~2008-03-12 17:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12 15:14 PNP: increase the maximum number of resources Dave Jones
2008-03-12 17:08 ` Olivier Galibert [this message]
2008-03-12 17:45 ` Len Brown
2008-03-13  0:16   ` Rene Herman
2008-03-13 12:04   ` PNP: dynamic pnp resources Thomas Renninger
2008-03-13 15:17     ` Bjorn Helgaas
2008-03-17 22:31     ` Rene Herman

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=20080312170802.GA10606@dspnet.fr.eu.org \
    --to=galibert@pobox.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=davej@codemonkey.org.uk \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    --cc=trenn@suse.de \
    --cc=yakui.zhao@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;
as well as URLs for NNTP newsgroup(s).