public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Alok Kataria <akataria@vmware.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: "ak@linux.intel.com" <ak@linux.intel.com>,
	Ingo Molnar <mingo@elte.hu>, "Brown, Len" <len.brown@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-acpi <linux-acpi@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	TJ <linux@tjworld.net>
Subject: Re: acpi based pci gap calculation  - v3
Date: Tue, 15 Jul 2008 13:54:16 -0700	[thread overview]
Message-ID: <1216155256.6135.25.camel@alok-dev1> (raw)
In-Reply-To: <200807151328.00739.jbarnes@virtuousgeek.org>

On Tue, 2008-07-15 at 13:28 -0700, Jesse Barnes wrote:
> On Tuesday, July 15, 2008 11:59 am Alok Kataria wrote:
> > Hi Andi,
> >
> > I don't see this patch being applied in any of the tree yet.
> > Resending this incase you guys might have missed it.
> > I assume this will go through the ACPI tree.
> >
> > The need for this patch was explained in
> > http://marc.info/?l=linux-kernel&m=121441818818598&w=2
> >
> > The v2 patch was discussed in
> > http://marc.info/?l=linux-acpi&m=121433339619175&w=2
> >
> > I then sent a incremental patch on top of v2 to fix some conditions and
> > handle the change in the e820_search_gap interface.
> >
> > In this v3 patch, i have folded the incremental fix into the v2 patch.
> > Please apply this.
> 
> This should probably go to linux-pci too.
> 
> I wonder if this is stable enough to go into 2.6.27?  

I have tested it with couple of different BIOS settings and it seems to
work as it should.

> Most of the PCI bugs we
> have at the moment are related to PCI resource allocation failures.  My hope
> is that finding more space will fix most of them.  Assuming this patch
> doesn't have any dependencies, I can put it in my linux-next branch.

No dependencies, I had added a function e820_search_gap which is used by
this patch. This function is already in the mainline tree. 
Thanks for applying.

--
Alok


  reply	other threads:[~2008-07-15 20:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 18:59 acpi based pci gap calculation - v3 Alok Kataria
2008-07-15 20:28 ` Jesse Barnes
2008-07-15 20:54   ` Alok Kataria [this message]
2008-07-15 22:53     ` Jesse Barnes
2008-07-15 23:07       ` Ingo Molnar
2008-07-16  5:40       ` Andi Kleen
2008-07-16 16:06         ` Jesse Barnes
2008-07-16 16:33           ` Andi Kleen
2008-07-17  0:03             ` Jesse Barnes
2008-07-17 21:31               ` Alok Kataria
     [not found]                 ` <1216663147.26169.5.camel@alok-dev1>
     [not found]                   ` <200807221450.52114.jbarnes@virtuousgeek.org>
2008-07-22 22:52                     ` Alok Kataria
2008-07-23  7:13                       ` TJ
2008-07-23 16:58                       ` Jesse Barnes
2008-07-23 17:10                         ` Alok Kataria
2008-07-23 17:52                           ` Jesse Barnes
2008-07-23 18:02                             ` Alok Kataria
2008-07-16  5:42 ` Andi Kleen

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=1216155256.6135.25.camel@alok-dev1 \
    --to=akataria@vmware.com \
    --cc=ak@linux.intel.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@tjworld.net \
    --cc=mingo@elte.hu \
    /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