From Fedora Project Wiki
No edit summary
m (Add virt category)
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<!-- All fields on this form are required to be accepted by FESCo.
= Virt PCI Express Q35 =
We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
 
= PCI Express BUS Support (Q35) =


== Summary ==
== Summary ==
Emulate PCI Express, preferably by default. PCI Express is required for Advanced Error Reporting support.  
Emulate PCI Express, preferably by default. PCI Express is required for Advanced Error Reporting support.  


Line 13: Line 9:
* Name: [[User:crobinso| Cole Robinson]]
* Name: [[User:crobinso| Cole Robinson]]
* Email: crobinso@redhat.com
* Email: crobinso@redhat.com
* Name: Michael Tsirkin/Amit Shah
* Name: Michael Tsirkin
* Email: mst@redhat.com/amit.shah@redhat.com
* Email: mst@redhat.com


== Current status ==
== Current status ==
* Targeted release: [[Releases/19 | Fedora 19]]
* Targeted release: [[Releases/19 | Fedora 19]]
* Last updated:  
* Last updated: Jan 26 2013
* Percentage of completion: TBS
* Percentage of completion: 30%


== Detailed Description ==
== Detailed Description ==
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
This is an infrastructure change. When working properly we get the same functionality as now by default.  
This is an infrastructure change. When working properly we get the same functionality as now by default.  


When configured, Express Root port devices will be visible to guest.
When configured, Express Root port devices will be visible to guest.


XXX: More info here about why this is really interesting


== Benefit to Fedora ==
== Benefit to Fedora ==
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
* Express Root port devices will be visible to guest.
* Express Root port devices will be visible to guest.
* Enhanced error reporting of assigned devices.
* Enhanced error reporting of assigned devices.
* Enables Native hotplug support.
* Enables Native hotplug support.
XXX: explain these


== Scope ==
== Scope ==
* TBS
* QEMU Q35 (available as of 1.3)
* Apps (all optional but would be nice if they are done)
** AHCI Migration issues? https://lists.gnu.org/archive/html/qemu-devel/2013-01/msg03103.html
** TBS
** No need to specify custom acpi tables (queued for 1.4)
 
** Seabios support (DONE, in 1.7.2)
** Will not be the default for 1.4 though...
*** Though sounds like there are still issues: http://www.seabios.org/pipermail/seabios/2013-January/005330.html
* Libvirt support (patches posted)


== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
XXX: fixme
 
Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
 
A good "how to test" should answer these four questions:
 
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this feature? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the feature is
working like it's supposed to?
3. What are the expected results of those actions?
-->
 
WHQL + existing PCI tests should cover a lot of functionality.
 
pcisig.org has pci express specific tests that we can run in a windows guest.
 


== User Experience ==
== User Experience ==
Express Root port devices will be visible to guest.
Express Root port devices will be visible to guest.


XXX: expand this


== Dependencies ==
== Dependencies ==
 
None.
None
 


== Contingency Plan ==
== Contingency Plan ==
 
Since this is brand new functionality, if it isn't ready in time, nothing has changed. We just drop this feature page.
TBS
 


== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
* http://www.linux-kvm.org/wiki/images/2/2e/2010-forum-Pci-express-in-qemu.pdf
* http://www.linux-kvm.org/wiki/images/2/2e/2010-forum-Pci-express-in-qemu.pdf
 
* http://wiki.qemu.org/Features/Q35
* [https://www.redhat.com/archives/libvir-list/2013-January/msg00494.html Libvirt patch posting]


== Release Notes ==
== Release Notes ==
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
XXX: fixme
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
 
* TBS


== Comments and Discussion ==
== Comments and Discussion ==
 
* None yet
* TBS




[[Category:FeaturePageIncomplete]]
[[Category:FeaturePageIncomplete]]
[[Category:Virtualization]]
<!-- When your feature page is completed and ready for review -->
<!-- When your feature page is completed and ready for review -->
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

Latest revision as of 00:03, 29 January 2013

Virt PCI Express Q35

Summary

Emulate PCI Express, preferably by default. PCI Express is required for Advanced Error Reporting support.

Down the road it will enable features such as alternative requester id, multiple pci domains.

Owner

  • Name: Cole Robinson
  • Email: crobinso@redhat.com
  • Name: Michael Tsirkin
  • Email: mst@redhat.com

Current status

  • Targeted release: Fedora 19
  • Last updated: Jan 26 2013
  • Percentage of completion: 30%

Detailed Description

This is an infrastructure change. When working properly we get the same functionality as now by default.

When configured, Express Root port devices will be visible to guest.

XXX: More info here about why this is really interesting

Benefit to Fedora

  • Express Root port devices will be visible to guest.
  • Enhanced error reporting of assigned devices.
  • Enables Native hotplug support.

XXX: explain these

Scope

How To Test

XXX: fixme

User Experience

Express Root port devices will be visible to guest.

XXX: expand this

Dependencies

None.

Contingency Plan

Since this is brand new functionality, if it isn't ready in time, nothing has changed. We just drop this feature page.

Documentation

Release Notes

XXX: fixme

Comments and Discussion

  • None yet
Retrieved from "https://fedoraproject.org/w/index.php?title=Features/Virt_PCI_Express_Q35&oldid=321223"