From: Brian King <brking@linux.vnet.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, David Darrington <ddarring@linux.vnet.ibm.com>
Subject: Re: [PATCH 08/18 v2] powerpc: Do not probe PCI buses or eBus devices if CMO is enabled
Date: Mon, 30 Jun 2008 16:56:54 -0500 [thread overview]
Message-ID: <486956A6.2070806@linux.vnet.ibm.com> (raw)
In-Reply-To: <18536.25052.228270.743669@cargo.ozlabs.ibm.com>
Paul Mackerras wrote:
> Robert Jennings writes:
>
>> From: Brian King <brking@linux.vnet.ibm.com>
>>
>> The Cooperative Memory Overcommit (CMO) on System p does not currently
>> support native PCI devices or eBus devices when enabled.
>
> Then why would we get any native PCI or eBus devices in the device
> tree?
We shouldn't. The reason the patch exists is so that *if* firmware were to
add support for physical PCI/eBus devices in CMO mode in the future, then
we could get into a scenario where there are such devices in the device
tree and we would want to prevent them from getting initialized
on a kernel without the code needed to support such a feature.
-Brian
--
Brian King
Linux on Power Virtualization
IBM Linux Technology Center
next prev parent reply other threads:[~2008-06-30 22:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 20:12 [PATCH 00/18 v2] powerpc: pSeries Cooperative Memory Overcommitment support Robert Jennings
2008-06-25 20:14 ` [PATCH 01/18 v2] powerpc: Remove extraneous error reporting for hcall failures in lparcfg Robert Jennings
2008-06-25 20:14 ` [PATCH 02/18 v2] powerpc: Split processor entitlement retrieval and gathering to helper routines Robert Jennings
2008-06-25 20:14 ` [PATCH 03/18 v2] powerpc: Add memory entitlement capabilities to /proc/ppc64/lparcfg Robert Jennings
2008-06-25 20:15 ` [PATCH 04/18 v2] powerpc: Split retrieval of processor entitlement data into a helper routine Robert Jennings
2008-06-25 20:15 ` [PATCH 05/18 v2] powerpc: Enable CMO feature during platform setup Robert Jennings
2008-06-25 20:15 ` [PATCH 06/18 v2] powerpc: Utilities to set firmware page state Robert Jennings
2008-06-25 20:16 ` [PATCH 07/18 v2] powerpc: Add collaborative memory manager Robert Jennings
2008-06-25 20:17 ` [PATCH 08/18 v2] powerpc: Do not probe PCI buses or eBus devices if CMO is enabled Robert Jennings
2008-06-30 4:32 ` Paul Mackerras
2008-06-30 21:56 ` Brian King [this message]
2008-06-25 20:17 ` [PATCH 09/18 v2] powerpc: Add CMO paging statistics Robert Jennings
2008-06-25 20:17 ` [PATCH 10/18 v2] powerpc: iommu enablement for CMO Robert Jennings
2008-06-25 20:18 ` [PATCH 11/18 v2] powerpc: vio bus support " Robert Jennings
2008-06-25 20:18 ` [PATCH 12/18 v2] powerpc: Verify CMO memory entitlement updates with virtual I/O Robert Jennings
2008-06-25 20:18 ` [PATCH 13/18 v2] powerpc: hvc enablement for CMO Robert Jennings
2008-06-25 20:18 ` [PATCH 14/18 v2] powerpc: hvcs " Robert Jennings
2008-06-25 20:19 ` [PATCH 15/18 v2] ibmveth: Automatically enable larger rx buffer pools for larger mtu Robert Jennings
2008-06-25 20:19 ` [PATCH 16/18 v2] ibmveth: enable driver for CMO Robert Jennings
2008-06-25 20:19 ` [PATCH 17/18 v2] ibmvscsi: driver enablement " Robert Jennings
2008-06-25 20:19 ` [PATCH 18/18 v2] powerpc: Update arch vector to indicate support " Robert Jennings
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=486956A6.2070806@linux.vnet.ibm.com \
--to=brking@linux.vnet.ibm.com \
--cc=ddarring@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).