Bug 1390316
Summary: | PCIe: Add Generic PCIe Root Ports | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Marcel Apfelbaum <marcel> | |
Component: | qemu-kvm-rhev | Assignee: | Marcel Apfelbaum <marcel> | |
Status: | CLOSED ERRATA | QA Contact: | jingzhao <jinzhao> | |
Severity: | low | Docs Contact: | ||
Priority: | medium | |||
Version: | 7.4 | CC: | ailan, chayang, drjones, hhan, juzhang, lersek, marcel, michen, mrezanin, mtessun, virt-maint | |
Target Milestone: | rc | Keywords: | FutureFeature | |
Target Release: | 7.4 | |||
Hardware: | All | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | qemu-kvm-rhev-2.9.0-1.el7 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1408808 (view as bug list) | Environment: | ||
Last Closed: | 2017-08-01 23:37:14 UTC | Type: | Bug | |
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: | 1173755, 1395265, 1408808, 1410437, 1410441, 1422967 |
Description
Marcel Apfelbaum
2016-10-31 16:51:12 UTC
Posted upstream: https://lists.gnu.org/archive/html/qemu-devel/2016-11/msg04310.html Hi Marcel According to comment1, "Generic PCIe root ports" is the same with "ioh3420", what is the different between bz1390316 and bz1390329 ? I am not very clear about it. Thanks Jing Zhao (In reply to jingzhao from comment #2) > Hi Marcel > > According to comment1, "Generic PCIe root ports" is the same with > "ioh3420", what is the different between bz1390316 and bz1390329 ? I am not > very clear about it. > > Thanks > Jing Zhao Hi, Generic PCIe Root ports exports the same functionality as IOH3420 indeed, however bz1390329 refers to PCIe-PCI bridge that has other functionality, to allow legacy PCI devices (instead of the DMI-PCI bridge i82801b11) Thanks, Marcel > Hi, > > Generic PCIe Root ports exports the same functionality as IOH3420 indeed, > however bz1390329 refers to PCIe-PCI bridge that has other functionality, to > allow legacy PCI devices (instead of the DMI-PCI bridge i82801b11) Marcel, thanks very much firstly, and also following questions confused me 1. "bz1390329 allow legacy PCI devices", you mean instead of i82801b11 bridge, how about the connection PRL for the legacy PCI device? connect to the Generic PCIe-PCI bridge(bz1390329) or connect to the pcie.0, in other words, what's the common connection? 2. As QE known, i82801b11 bridge will be not used on rhel7.4, that means we will use the PCIe-PCI bridge that bz1390329 provided in qemu? qemu will provide Generic PCIe-PCI bridge all the time, never use the i82801b11 bridge? 3. the usage of the two bridge, are the following right? 1) pcie.0 --- Generic PCIe Root Ports (/multifunction) -- pcie devices 2) pcie.0 --- Generic PCIe-PCI bridge --- PCI devices Thanks Jing Zhao (In reply to jingzhao from comment #4) > > Hi, > > > > Generic PCIe Root ports exports the same functionality as IOH3420 indeed, > > however bz1390329 refers to PCIe-PCI bridge that has other functionality, to > > allow legacy PCI devices (instead of the DMI-PCI bridge i82801b11) > > Marcel, thanks very much firstly, and also following questions confused me > > 1. "bz1390329 allow legacy PCI devices", you mean instead of i82801b11 > bridge, how about the connection PRL for the legacy PCI device? connect to > the Generic PCIe-PCI bridge(bz1390329) or connect to the pcie.0, in other > words, what's the common connection? > Yes, PCI devices should be Integrated Endpoints (plugged into pcie.0) or connected to the new device - the PCIe-PCI bridge. We want to deprecate the i82801b11 bridge. > 2. As QE known, i82801b11 bridge will be not used on rhel7.4, that means we > will use the PCIe-PCI bridge that bz1390329 provided in qemu? yes, but the new bridge will not be ready for 7.4 . on 7.4 PCI devices will be plugged only into pcie.0 bus. qemu will > provide Generic PCIe-PCI bridge all the time, never use the i82801b11 bridge? > once the device will be ready, it will completely replace the i82801b11 > 3. the usage of the two bridge, are the following right? > > 1) pcie.0 --- Generic PCIe Root Ports (/multifunction) -- pcie devices > 2) pcie.0 --- Generic PCIe-PCI bridge --- PCI devices > Correct and also: 3) pcie.0 --- PCI devices Thanks, Marcel > > Thanks > Jing Zhao Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 |