Difference between revisions of "Design Sessions"
Lars.kurth (talk | contribs) |
Lars.kurth (talk | contribs) (→2018: Developer and Design Summit: Added placeholders) |
||
Line 1: | Line 1: | ||
== 2018: Developer and Design Summit == |
== 2018: Developer and Design Summit == |
||
+ | ==== Architecture ==== |
||
− | {{InfoLeft|Please send design session notes to community.manager@xenproject.org. We will post notes before the end of July.}} |
||
+ | [TODO Reworking x86 Xen, current status and future plan] |
||
+ | [TODO PCI pass-through with de-privileged QEMU] |
||
+ | [TODO Resource mapping, PV-IOMMU and page ownership in Xen] |
||
+ | |||
+ | ==== Intel Specific === |
||
+ | [TODO Intel Processor Trace for Xen hypervisor design discussion] |
||
+ | [TODO how to support more vCPUs in a HVM guest] |
||
+ | [TODO NVDIMM Discussion] |
||
+ | [TODO SGX deep dive and SGX virtualization design discussion] |
||
+ | |||
+ | ==== Embedded and Safety ==== |
||
+ | [TODO Dom0less and static partitioning] |
||
+ | [TODO A Strawman Plan to Make Safety Certification for Xen Easier] |
||
+ | [TODO Graphic virtualization on Xen] |
||
+ | |||
+ | ==== Working Practice, Process, ... ==== |
||
+ | [TODO Testing/Building with Docker/GitLab] |
||
+ | [TODO (Automated?) Performance Testing in Virtualization] |
||
+ | [TODO Process changes: is the 6 monthly release Cadence too short, Security Process, ...] |
||
+ | |||
+ | ==== Performance ==== |
||
+ | [TODO XenWatch Multithreading Design Session] |
||
+ | |||
+ | ==== Security ==== |
||
+ | [TODO Silo mode for extra defence in depth] |
||
+ | [TODO Panopticon: See no secrets, leak no secrets] |
||
+ | [TODO What is OpenXT and the Xen Security Community Doing - this was primarily about measured boot and Win10 support] |
||
+ | |||
+ | ==== Other ==== |
||
+ | [TODO USB pass-through on Xenserver] |
||
+ | [TODO From Hobbyist to Maintainer, Why and How] |
||
+ | [TODO Unikraft: Design and Use Cases] |
||
+ | |||
== 2017: Developer and Design Summit == |
== 2017: Developer and Design Summit == |
||
=== Notes === |
=== Notes === |
Revision as of 13:44, 2 July 2018
Contents
- 1 2018: Developer and Design Summit
- 2 2017: Developer and Design Summit
- 3 Archive
2018: Developer and Design Summit
Architecture
[TODO Reworking x86 Xen, current status and future plan] [TODO PCI pass-through with de-privileged QEMU] [TODO Resource mapping, PV-IOMMU and page ownership in Xen]
= Intel Specific
[TODO Intel Processor Trace for Xen hypervisor design discussion] [TODO how to support more vCPUs in a HVM guest] [TODO NVDIMM Discussion] [TODO SGX deep dive and SGX virtualization design discussion]
Embedded and Safety
[TODO Dom0less and static partitioning] [TODO A Strawman Plan to Make Safety Certification for Xen Easier] [TODO Graphic virtualization on Xen]
Working Practice, Process, ...
[TODO Testing/Building with Docker/GitLab] [TODO (Automated?) Performance Testing in Virtualization] [TODO Process changes: is the 6 monthly release Cadence too short, Security Process, ...]
Performance
[TODO XenWatch Multithreading Design Session]
Security
[TODO Silo mode for extra defence in depth] [TODO Panopticon: See no secrets, leak no secrets] [TODO What is OpenXT and the Xen Security Community Doing - this was primarily about measured boot and Win10 support]
Other
[TODO USB pass-through on Xenserver] [TODO From Hobbyist to Maintainer, Why and How] [TODO Unikraft: Design and Use Cases]
2017: Developer and Design Summit
Notes
Intel sessions
ARM Sessions
Coprocessor Sharing and Stubdoms
- Notes on stubdoms and latency on ARM
- Shared coprocessor framework followup
- SCF configuration followup
PVH (v2)
Release and Build tools
- Notes Design Session: Making Releases Lessons Learned: Improving Our Release Process and Tooling
- Notes Design Session: Testing & CI Process and Workflow Improvements, x86/ARM/Embedded Testing, etc. - Does what we do today work?
Outcomes
- Build tools follow up
- A document for Xen release management
- A document for Xen release management, v2
Security, Safety
- Notes of Design Session: Xen Certification in Automotive Industrial
- Notes for Design Session: Loose ends for becoming a CNA (CVE Numbering Authorities) and other Security Team Operational Questions
- Notes from Design Summit Hypervisor Fuzzing Session
Outcomes
Community
Sessions Highlighted on the Wiki
Graphics Virtualization
Peer Review CommentsFeel free to make suggestions hereAnd whether you intend to attend: |
Xen Toolstacks for Server and Edge Use Cases
Peer Review CommentsFeel free to make suggestions hereAnd whether you intend to attend: |
Testing Server and Edge Hypervisors
Peer Review CommentsFeel free to make suggestions hereAnd whether you intend to attend: |
Design Session: Loose ends for becoming a CNA (CVE Numbering Authorities) and other Security Team Operational Questions -
Peer Review CommentsFeel free to make suggestions hereAnd whether you intend to attend: |