Bug 463368
Summary: | [LTC 6.0 FEAT] 201023:Fix eHCA to tolerate memory DLPAR operations when module not loaded | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | IBM Bug Proxy <bugproxy> |
Component: | kernel | Assignee: | Doug Ledford <dledford> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.0 | CC: | ejratl, notting, peterm, snagar |
Target Milestone: | alpha | Keywords: | FutureFeature, OtherQA |
Target Release: | 6.0 | ||
Hardware: | ppc64 | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | kernel-2.6.31-1 | Doc Type: | Enhancement |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-11-15 14:05:19 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 356741, 465489, 554559 |
Description
IBM Bug Proxy
2008-09-23 03:10:38 UTC
Has this feature actually made 2.6.27? Hello RH, the ehca driver will not support memory DLPAR as described in the titel of this Bug. The plan for RH 6 is to enable the ehca driver to tolerate memory DLPAR operations. That means memory DLPAR operations are possible if the ehca driver is not loaded. Could you please rename this feature Bug to "Fix eHCA to tolerate memory DLPAR"? The fix will be available in OFED-1.5 release (planned GA Aug 1) and in linux kernel version 2.6.31. If RH 6 is not going to pick OFED-1.5 for infinibad inclusion we would also provide a patch here in this Bugzilla. regards Stefan ------- Comment From alexs.ibm.com 2010-05-31 12:09 EDT------- I've verified that the code for tolerating DLPAR mem is included in snapshot 5, setting feature to verified. Red Hat Enterprise Linux 6.0 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you. |