All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Andy Isaacson <adi@hexapodia.org>,
	"R. Andrew Bailey" <bailey@akamai.com>,
	Yinghai <yinghai.lu@oracle.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	guenter.roeck@ericsson.com,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Thomas Renninger <trenn@suse.de>,
	yaneti@declera.com
Subject: Re: [PATCH] x86/PCI: never allocate PCI MMIO resources below    BIOS_END
Date: Mon, 26 Apr 2010 18:40:54 -0700	[thread overview]
Message-ID: <20100426184054.6f17a2b2@virtuousgeek.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1004261824570.3739@i5.linux-foundation.org>

On Mon, 26 Apr 2010 18:27:27 -0700 (PDT)
Linus Torvalds <torvalds@linux-foundation.org> wrote:

> 
> 
> On Mon, 26 Apr 2010, Jesse Barnes wrote:
> > 
> > Glad we agree.  As I said (and echoing Bjorn), I think it would be best
> > to reserve this space in a way that doesn't just use IORESOURCE_BUSY.
> > We want and need to do allocations from the special region, so we
> > should mark it as such.
> 
> I think Bjorn's patch to pcibios_align_resource() is really good and 
> clever, and I think it should take care of the need for IORESOURCE_BUSY, 
> no? We do want to let devices that are _already_ allocated there insert 
> their resources, it's just that we never want to allocate new ones in the 
> low 1M region.
> 
> Do we actually have a regression left with Bjorn's patch?

No, I think we're covered.  But it sounded like Peter was also
concerned about making new allocations from the 1M space, which would
mean we'd need something other than the IORESOURCE_BUSY bit.  But maybe
Bjorn's patch plus simply removing the IORESOURCE_BUSY line is
sufficient for that.  The downside there is that it doesn't clearly
communicate the special nature of the 1M region.

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2010-04-27  1:40 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 23:02 [PATCH] x86/PCI: never allocate PCI MMIO resources below BIOS_END H. Peter Anvin
2010-04-26 23:25 ` Jesse Barnes
2010-04-26 23:49   ` H. Peter Anvin
2010-04-26 23:49   ` H. Peter Anvin
2010-04-27  0:05     ` Jesse Barnes
2010-04-27  1:27       ` Linus Torvalds
2010-04-27  1:40         ` Jesse Barnes [this message]
2010-04-27  1:41         ` Yinghai
2010-04-27 15:11           ` Bjorn Helgaas
2010-04-28 16:07             ` Bjorn Helgaas
2010-04-28 17:14               ` Yinghai Lu
2010-04-28 19:06                 ` Bjorn Helgaas
2010-04-28 19:10                   ` Yinghai
2010-04-28 19:23                     ` Bjorn Helgaas
  -- strict thread matches above, loose matches on Subject: below --
2010-04-27  2:02 H. Peter Anvin
2010-04-13 21:42 [PATCH -v2 1/2] x86: Reserve [0xa0000, 0x100000] in e820 map Yinghai
2010-04-21  5:33 ` [PATCH -v4 1/3] " Yinghai
2010-04-21 19:31   ` Andy Isaacson
2010-04-23 23:05     ` [PATCH] x86/PCI: never allocate PCI MMIO resources below BIOS_END Bjorn Helgaas
2010-04-23 23:44       ` H. Peter Anvin
2010-04-24  0:36         ` Yinghai Lu
2010-04-26 12:50       ` R. Andrew Bailey
2010-04-26 15:40         ` Bjorn Helgaas
2010-04-26 18:34       ` Andy Isaacson
2010-04-26 19:31         ` Jesse Barnes
2010-04-26 20:27           ` Bjorn Helgaas
2010-04-26 20:37             ` Jesse Barnes
2010-04-26 21:07               ` Yinghai
2010-04-26 21:19                 ` H. Peter Anvin
2010-04-26 21:12               ` H. Peter Anvin
2010-04-26 21:25                 ` Jesse Barnes
2010-04-26 21:44                   ` H. Peter Anvin
2010-04-26 21:53                     ` Jesse Barnes
2010-04-26 21:59                   ` Yinghai Lu
2010-04-26 21:44                 ` jacob pan

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=20100426184054.6f17a2b2@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=adi@hexapodia.org \
    --cc=bailey@akamai.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=guenter.roeck@ericsson.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=trenn@suse.de \
    --cc=x86@kernel.org \
    --cc=yaneti@declera.com \
    --cc=yinghai.lu@oracle.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.