Bug 323431
Summary: | [RHEL5.2]: Xen 3.1.1 ia64 PCI front/back fixes | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Chris Lalancette <clalance> |
Component: | kernel-xen | Assignee: | Chris Lalancette <clalance> |
Status: | CLOSED WONTFIX | QA Contact: | Martin Jenner <mjenner> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.1 | CC: | xen-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | ia64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-02-16 15:12:15 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: |
Description
Chris Lalancette
2007-10-08 17:38:23 UTC
Cset15083 is just to initializing the variable, so it does not break kABI. As for cset15392, we are now trying to check on PRIMEQUEST/Tiger4 that it does not break kABI. Fujitsu Xen team in Japan has tested cset 15392 with a driver domain, and confiremd that it has no problem and works fine. This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?". Where are we with these? Did they make RHEL 5.2? Or are they desired for 5.3? These are not in 5.2, so desired for 5.3. Clearing out old flags for reporting purposes. Chris Lalancette |