From: Ingo Molnar <mingo@elte.hu>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
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>, Adam Belay <abelay@mit.edu>,
Matthew Garrett <mjg@redhat.com>, Dan Williams <dcbw@redhat.com>
Subject: Re: [PATCH 1/5] resources: add arch hook for preventing allocation in reserved areas
Date: Mon, 13 Dec 2010 14:47:39 +0100 [thread overview]
Message-ID: <20101213134739.GA27941@elte.hu> (raw)
In-Reply-To: <20101213054334.GA15856@helgaas.com>
* Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> > OK, so I guess the best thing we can do for 2.6.37 is to revert 1af3c2e (x86:
> > allocate space within a region top-down), right?
>
> That's a possibility, but I'm not sure it's the best. It would avoid the nx6325
> landmine, but we could easily step on a different one on other machines.
>
> If Windows uses the end of available space first, that's the best-tested
> territory, and I think it's better to try to stay in it rather revert 1af3c2e and
> start mapping different territory that really isn't tested by Windows at all.
>
> On the nx6325, we stray out of that tested territory because Linux opens windows
> on subtractive-decode bridges and allocates more space to CardBus bridges.
>
> I think it'd be fairly simple to leave subtractive-decode bridges alone, and that
> might make the nx6325 work well enough for .37, even without the quirk. This
> feels like a change that might be the right thing to do in general. Using
> subtractive rather than positive decode would give up a little performance, but I
> doubt it's important
Is there a patch for that that people could try?
The regression needs to be addressed one way or another: either by improving the
"compatible with Windows" approach to actually work (without quirks), or by
reverting to the tested-for-years Linux solution.
( What we always try to avoid is trading in a set of regressions for another set of
regressions. That way lies madness, it can not result in reliable, provable
progress. )
Thanks,
Ingo
next prev parent reply other threads:[~2010-12-13 13:48 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
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 [this message]
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=20101213134739.GA27941@elte.hu \
--to=mingo@elte.hu \
--cc=abelay@mit.edu \
--cc=bjorn.helgaas@hp.com \
--cc=dcbw@redhat.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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