From: Ingo Molnar <mingo@elte.hu>
To: Greg KH <greg@kroah.com>
Cc: Yinghai Lu <Yinghai.Lu@Sun.COM>,
Andrew Morton <akpm@linux-foundation.org>,
Jeff Garzik <jeff@garzik.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/8] AMD opteron mm config numa etc
Date: Wed, 20 Feb 2008 07:37:52 +0100 [thread overview]
Message-ID: <20080220063752.GD7493@elte.hu> (raw)
In-Reply-To: <20080219175339.GB8344@kroah.com>
* Greg KH <greg@kroah.com> wrote:
> > > could make up for system that system have acpi problem or still
> > > can mmconf and numa when acpi=off
> >
> > Greg, any deep objections against these patches? (other than that
> > they need a good amount of testing) I personally think that the more
> > independent the kernel is of the whims of the BIOS, the better ...
>
> No objection from me, other than they need a LOT of testing. [...]
ok - have queued it up for v2.6.26. Note: Andrew might get grumpy when
your PCI tree starts changing nearby places in arch/x86/pci again and it
clashes with these changes in x86.git - in that case please pick up the
full lot from x86.git#testing and carry it in the PCI tree. (or,
alternatively, send me any trivial, arch/x86-only PCI bits to
x86.git#testing so that we can keep it and test it all in a single place
- whichever approach is more convenient to you)
> [...] Oh, and the networking patch is still wrong, and the poster has
> been told this numerous times, which makes me wonder how well the pci
> bridge patch was tested...
i think the optimization should be more correct now than in the past,
its purpose and dependencies just have not been communicated fully.
We'll get there eventually :-)
Ingo
next prev parent reply other threads:[~2008-02-20 6:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 11:19 Yinghai Lu
2008-02-19 11:23 ` Ingo Molnar
2008-02-19 17:53 ` Greg KH
2008-02-20 6:37 ` Ingo Molnar [this message]
2008-02-20 9:51 ` Andrew Morton
2008-02-20 10:38 ` Ingo Molnar
2008-02-19 16:50 ` Jeff Garzik
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=20080220063752.GD7493@elte.hu \
--to=mingo@elte.hu \
--cc=Yinghai.Lu@Sun.COM \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome