From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Len Brown <lenb@kernel.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Adam Belay <abelay@mit.edu>,
Matthew Garrett <mjg@redhat.com>, Dan Williams <dcbw@redhat.com>,
rjw@sisk.pl
Subject: Re: [PATCH 1/5] resources: add arch hook for preventing allocation in reserved areas
Date: Fri, 10 Dec 2010 17:37:49 -0800 [thread overview]
Message-ID: <20101210173749.7ec3cc28@jbarnes-desktop> (raw)
In-Reply-To: <201012101407.24419.bjorn.helgaas@hp.com>
On Fri, 10 Dec 2010 14:07:24 -0700
Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> On Friday, December 10, 2010 01:36:09 pm Jesse Barnes wrote:
> > [Actually cc'ing Matthew this time]
> >
> > On Fri, 10 Dec 2010 12:30:08 -0800
> > Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> >
> > > On Wed, 08 Dec 2010 14:36:06 -0700
> > > Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> > >
> > > >
> > > > This adds arch_remove_reservations(), which an arch can implement if it
> > > > needs to protect part of the address space from allocation.
> > > >
> > > > Sometimes that can be done by just requesting a resource. This hook is to
> > > > cover cases where protected area doesn't fit well in the hierarchical
> > > > resource tree. For example, x86 BIOS E820 reservations are not related
> > > > to devices, so they may overlap part of, all of, or more than a device
> > > > resource.
> > > >
> > > > Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
> > > > ---
> > >
> > > Hm, this is bigger than the simple change of just avoiding the high 2M;
> > > Linus have you checked it out yet? It's nicer than simply adjusting
> > > PCIBIOS_MAX_MEM since it will affect all resource callers rather than
> > > just PCI, but it's definitely bigger.
>
> Dan Williams also reproduced the problem on a 2530p and tested this
> series (though I think he actually tested a backport in Fedora):
> https://bugzilla.kernel.org/show_bug.cgi?id=23542#c7
> https://bugzilla.kernel.org/show_bug.cgi?id=23542#c23
>
> The simple PCIBIOS_MAX_MEM_32 change below will fix the 2530p problem,
> but it won't help fix the nx6325 problem Rafael reported; details at:
> https://bugzilla.kernel.org/show_bug.cgi?id=23332#c20
>
> Rafael did confirm on #acpi Wednesday that the full series fixed
> his nx6325.
Thanks, I'll add Dan and Rafael's tested-bys to the patches (they're
already in my for-linus tree). Unless Linus has a problem with them
I'll send them over to him this weekend or Monday.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-12-11 1:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 21:36 [PATCH 1/5] resources: add arch hook for preventing allocation in reserved areas Bjorn Helgaas
2010-12-08 21:36 ` [PATCH 2/5] x86: avoid BIOS area when allocating address space Bjorn Helgaas
2010-12-08 21:36 ` [PATCH 3/5] x86: avoid PNP resources " Bjorn Helgaas
2010-12-08 21:36 ` [PATCH 4/5] PNP: add framework for platform PNP quirks Bjorn Helgaas
2010-12-08 21:36 ` [PATCH 5/5] PNP: HP nx6325 fixup: reserve unreported resources Bjorn Helgaas
2010-12-12 3:30 ` Linus Torvalds
2010-12-12 5:23 ` Dave Airlie
2010-12-12 6:17 ` Bjorn Helgaas
2010-12-14 20:34 ` Linus Torvalds
2010-12-14 20:44 ` Linus Torvalds
2010-12-14 23:57 ` Bjorn Helgaas
2010-12-15 6:02 ` Bjorn Helgaas
2010-12-15 6:26 ` Bjorn Helgaas
2010-12-15 7:03 ` Linus Torvalds
2010-12-15 18:18 ` Bjorn Helgaas
2010-12-15 18:27 ` H. Peter Anvin
2010-12-15 19:21 ` Linus Torvalds
2010-12-08 21:37 ` [PATCH 0/5] resources: add arch hook for preventing allocation in reserved areas Bjorn Helgaas
2010-12-10 20:30 ` [PATCH 1/5] " Jesse Barnes
2010-12-10 20:36 ` Jesse Barnes
2010-12-10 21:07 ` Bjorn Helgaas
2010-12-11 1:37 ` Jesse Barnes [this message]
2010-12-12 3:34 ` Linus Torvalds
2010-12-12 4:16 ` Jesse Barnes
2010-12-12 13:20 ` Rafael J. Wysocki
2010-12-13 5:43 ` Bjorn Helgaas
2010-12-13 13:47 ` Ingo Molnar
2010-12-15 0:09 ` Bjorn Helgaas
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=20101210173749.7ec3cc28@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=abelay@mit.edu \
--cc=bjorn.helgaas@hp.com \
--cc=dcbw@redhat.com \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mjg@redhat.com \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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