svn commit: r52874 - head/en_US.ISO8859-1/htdocs/news/status
Edward Tomasz Napierala
trasz at FreeBSD.org
Mon Mar 18 22:43:53 UTC 2019
Author: trasz
Date: Mon Mar 18 22:43:51 2019
New Revision: 52874
URL: https://svnweb.freebsd.org/changeset/doc/52874
Log:
Add Quarterly Status Report for 2018Q4.
Reviewed by: bcr
Approved by: bcr (mentor)
Differential Revision: https://reviews.freebsd.org/D19618
Added:
head/en_US.ISO8859-1/htdocs/news/status/report-2018-09-2018-12.xml (contents, props changed)
Modified:
head/en_US.ISO8859-1/htdocs/news/status/Makefile
Modified: head/en_US.ISO8859-1/htdocs/news/status/Makefile
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/Makefile Sun Mar 17 10:22:32 2019 (r52873)
+++ head/en_US.ISO8859-1/htdocs/news/status/Makefile Mon Mar 18 22:43:51 2019 (r52874)
@@ -81,6 +81,7 @@ XMLDOCS+= report-2017-04-2017-06
XMLDOCS+= report-2017-07-2017-09
XMLDOCS+= report-2017-10-2017-12
XMLDOCS+= report-2018-01-2018-09
+XMLDOCS+= report-2018-09-2018-12
XSLT.DEFAULT= report.xsl
Added: head/en_US.ISO8859-1/htdocs/news/status/report-2018-09-2018-12.xml
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2018-09-2018-12.xml Mon Mar 18 22:43:51 2019 (r52874)
@@ -0,0 +1,2268 @@
+<?xml version="1.0" encoding="utf-8" ?>
+<!DOCTYPE report PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for
+ Status Report//EN"
+ "http://www.FreeBSD.org/XML/share/xml/statusreport.dtd" >
+
+<!-- $FreeBSD$ -->
+<!-- This file was generated with https://github.com/trasz/md2docbook -->
+<!--
+ Variables to replace:
+ %%START%% - report month start
+ %%STOP%% - report month end
+ %%YEAR%% - report year
+ %%NUM%% - report issue (first, second, third, fourth)
+ %%STARTNEXT%% - report month start
+ %%STOPNEXT%% - report month end
+ %%YEARNEXT%% - next report due year (if different than %%YEAR%%)
+ %%DUENEXT%% - next report due date (i.e., June 6)
+-->
+
+<report>
+ <date>
+ <month>October-December</month>
+
+ <year>2018</year>
+ </date>
+
+ <section>
+ <title>Introduction</title>
+
+ <p>Since we are still on this island among many in this vast ocean of the Internet, we write this message in a bottle to inform you of the work we have finished and what lies ahead of us. These deeds that we have wrought with our minds and hands, they are for all to partake of - in the hopes that anyone of their free will, will join us in making improvements. In todays message the following by no means complete or ordered set of improvements and additions will be covered:</p>
+
+ <p>i386 PAE Pagetables for up to 24GB memory support, Continuous Integration efforts, driver updates to ENA and graphics, ARM enhancements such as RochChip, Marvell 8K, and Broadcom support as well as more DTS files, more Capsicum possibilities, as well as pfsync improvements, and many more things that you can read about for yourselves.</p>
+
+ <p>Additionally, we bring news from some islands further down stream, namely the nosh project, HardenedBSD, ClonOS, and the Polish BSD User-Group.</p>
+
+ <p>We would, selfishly, encourage those of you who give us the good word to please send in your submissions sooner than just before the deadline, and also encourage anyone willing to share the good word to please read the section on which submissions we're also interested in having.</p>
+
+ <p>Yours hopefully,<br/>
+ Daniel Ebdrup, on behalf of the status report team.</p>
+ </section>
+
+ <category>
+ <name>team</name>
+
+ <description>&os; Team Reports</description>
+
+ <p>Entries from the various official and semi-official teams,
+ as found in the <a href="&enbase;/administration.html">Administration
+ Page</a>.</p>
+ </category>
+
+ <category>
+ <name>proj</name>
+
+ <description>Projects</description>
+
+ <p>Projects that span multiple categories, from the kernel and userspace
+ to the Ports Collection or external projects.</p>
+ </category>
+
+ <category>
+ <name>arch</name>
+
+ <description>Architectures</description>
+
+ <p>Updating platform-specific features and bringing in support
+ for new hardware platforms.</p>.
+ </category>
+
+ <category>
+ <name>ports</name>
+
+ <description>Ports</description>
+
+ <p>Changes affecting the Ports Collection, whether sweeping
+ changes that touch most of the tree, or individual ports
+ themselves.</p>
+ </category>
+
+ <category>
+ <name>misc</name>
+
+ <description>Miscellaneous</description>
+
+ <p>Objects that defy categorization.</p>
+ </category>
+
+ <category>
+ <name>third</name>
+
+ <description>Third-Party Projects</description>
+
+ <p>Many projects build upon &os; or incorporate components of
+ &os; into their project. As these projects may be of interest
+ to the broader &os; community, we sometimes include brief
+ updates submitted by these projects in our quarterly report.
+ The &os; project makes no representation as to the accuracy or
+ veracity of any claims in these submissions.</p>
+ </category>
+
+ <project cat='team'>
+ <title>FreeBSD Release Engineering Team</title>
+
+ <body>
+ <p>Category: team</p>
+
+ <p></p>
+
+ <p>The FreeBSD Release Engineering Team is responsible for
+ setting
+ and publishing release schedules for official project
+ releases
+ of FreeBSD, announcing code freezes and maintaining the
+ respective branches, among other things.</p>
+
+ <p>During the fourth quarter of 2018, the FreeBSD Release
+ Engineering team
+ continued working on the 12.0-RELEASE. The
+ <tt>stable/12</tt> branch was created
+ on October 19, with the first BETA build being started
+ shortly after. The
+ release cycle slipped slightly with the addition of
+ 12.0-BETA4, after which
+ the <tt>releng/12.0</tt> branch was created on November
+ 16.</p>
+
+ <p>The remainder of the release cycle continued relatively
+ smoothly for the
+ duration of the release candidate (RC) phase, with the
+ final release builds
+ starting December 7, and the official announcement sent
+ December 11.</p>
+
+ <p>Throughout the quarter, several development snapshots
+ builds were released
+ for the <tt>head</tt> and <tt>stable/11</tt> branches.</p>
+
+ <p>Much of this work was sponsored by the FreeBSD Foundation.</p>
+
+ </body>
+
+ </project>
+
+ <project cat='team'>
+ <title>Ports Collection</title>
+
+ <contact>
+ <person>
+ <name>René Ladan</name>
+ <email>portmgr-secretary at FreeBSD.org</email>
+ </person>
+ <person>
+ <name>FreeBSD Ports Management Team</name>
+ <email>portmgr at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="https://www.FreeBSD.org/ports/">About FreeBSD Ports</url>
+ <url href="https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/ports-contributing.html">Contributing to Ports</url>
+ <url href="http://portsmon.freebsd.org/index.html">FreeBSD Ports Monitoring</url>
+ <url href="https://www.freebsd.org/portmgr/index.html">Ports Management Team">Ports Management Team</url>
+ </links>
+
+ <body>
+ <p>The number of ports in the last quarter shrunk a bit to
+ 32,900. At the end of
+ the quarter there were 2365 open port PRs of which a small
+ 500 were unassigned.
+ The last quarter saw 7333 commits from 174 committers.
+ This means that more
+ port PRs were resolved than last quarter and the number of
+ commits remained
+ approximately the same.</p>
+
+ <p>During the last quarter, we welcomed Alexandre C.
+ Guimarães (rigoletto@) and
+ Vinícius Zavam (egypcio@). The port commit bits of Alberto
+ Villa (avilla@),
+ Lars Thegler (lth@), Dryice Dong Liu (dryice@), Ion-Mihai
+ Tetcu (itetcu@),
+ Gabor Pali (pgj@), Tom Judge (tj@), Ollivier Robert
+ (roberto@), and Maxim
+ Sobolev (sobomax@) were taken in for safekeeping.</p>
+
+ <p>The number of commit bits safekept is higher than usual
+ because for port commit
+ bits the idle timeout changed from 18 months to 12 months.</p>
+
+ <p>Some default versions were changed:</p>
+
+ <ul>
+ <li>PHP from 7.1 to 7.2</li>
+
+ <li>Perl5 from 5.26 to 5.28</li>
+
+ <li>Ruby from 2.4 to 2.5</li>
+
+ <li>For LLVM, version 7.0 is now supported as a default
+ version.</li>
+ </ul>
+
+ <p>
+ Other big changes are:</p>
+
+ <ul>
+ <li>info files are stored in the share/info directory just as
+ other
+ operating systems do.</li>
+
+ <li>PyQt ports can now be installed concurrently.</li>
+
+ <li>As FreeBSD 10 reached its end of life, support for this
+ branch has been
+ removed from the Ports Collection. People still requiring
+ FreeBSD 10
+ support can use the RELEASE\_10\_EOL tag.</li>
+
+ <li>USES=cmake now defaults to outsource</li>
+
+ <li>KDE 4 has reached its end-of-life and has been removed
+ from the Ports
+ Collection.</li>
+ </ul>
+
+ <p>
+ Eager as ever, antoine@ ran 36 exp-runs this quarter to
+ ensure major port
+ upgrades were correct.</p>
+
+ </body>
+
+ </project>
+
+ <project cat='team'>
+ <title>FreeBSD Core Team</title>
+
+ <contact>
+ <person>
+ <name>FreeBSD Core Team</name>
+ <email>core at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <body>
+ <p>Noteworthy events since the last quarterly report:</p>
+
+ <ul>
+ <li>Yuri Pankov (yuripv@) was awarded a source commit bit
+ under the mentorship of Konstantin Belousov
+ (kib@).</li>
+
+ <li>Core agrees that portmgr@ may enforce a 12-month commit
+ bit expiration for ports committers.</li>
+
+ <li>Thomas Munro (tmunro@) was awarded a source commit bit
+ under the mentorship of Mateusz Guzik (mgj@) and
+ co-mentorship of Allan Jude (allanjude@).</li>
+
+ <li>With the approval of FCP-0101, 10/100 Ethernet drivers
+ will be deprecated.</li>
+
+ <li>Core approved the promotion of Remko Lodder (remko@) to
+ Deputy Security Officer.</li>
+ </ul>
+
+ <p></p>
+
+ </body>
+
+ </project>
+
+ <project cat='team'>
+ <title>FreeBSD Foundation</title>
+
+ <contact>
+ <person>
+ <name>Deb Goodkin</name>
+ <email>deb at FreeBSDFoundation.org</email>
+ </person>
+ </contact>
+
+ <body>
+ <p>The FreeBSD Foundation is a 501(c)(3) non-profit
+ organization dedicated to supporting and promoting
+ the FreeBSD Project and community worldwide.
+ Funding comes from individual and corporate
+ donations and is used to fund and manage software
+ development projects, conferences and developer
+ summits, and provide travel grants to FreeBSD
+ contributors. The Foundation purchases and
+ supports hardware to improve and maintain FreeBSD
+ infrastructure and provides resources to improve
+ security, quality assurance, and release
+ engineering efforts; publishes marketing material
+ to promote, educate, and advocate for the FreeBSD
+ Project; facilitates collaboration between
+ commercial vendors and FreeBSD developers; and
+ finally, represents the FreeBSD Project in
+ executing contracts, license agreements, and other
+ legal arrangements that require a recognized legal
+ entity.</p>
+
+ <p>Here are some highlights of what we did to help FreeBSD
+ last quarter:</p>
+
+ <p>Partnerships and Commercial User Support</p>
+
+ <p>As a 501(c)(3) non-profit, we don’t directly support
+ commercial users, but we do work with them to
+ understand their needs and help facilitate
+ collaboration with the community. Last quarter, we
+ were able to meet with a number of FreeBSD users
+ and supporters at the October FreeBSD Developer
+ Summit and MeetBSD conference in addition to our
+ regular company meetings. These in-person meetings
+ provide the opportunity to discuss pain points,
+ identify how they can contribute back to FreeBSD,
+ talk about what technologies they would like to
+ see supported, and what can be done to support
+ FreeBSD over more of their technologies and
+ products.</p>
+
+ <p>Fundraising Efforts</p>
+
+ <p>By end of last year, we raised over $1.3M and were able to
+ add Juniper, Netflix and Facebook and
+ Handshake.org to our list of Foundation Partners.
+ You can view the entire list here <a
+ href="https://www.freebsdfoundation.org/donors/">https://www.freebsdfoundation.org/donors/</a>.
+ We are still finalizing total donations, and will
+ report the final numbers in early February. Thank
+ you to everyone who supported our efforts in 2018.</p>
+
+ <p>OS Improvements</p>
+
+ <p>In the fourth quarter of 2018 six authors made a total of
+ 315 commits to the FreeBSD development tree that were
+ identified as being sponsored by the FreeBSD
+ Foundation. These included staff members
+ Konstantin Belousov, Glen Barber, Li-Wen Hsu and
+ Ed Maste, and grant recipients Mateusz Guzik and
+ Mark Johnston.</p>
+
+ <p>Mateusz' work over the quarter consisted of identifying
+ and fixing bottlenecks in the FreeBSD kernel and
+ system libraries. The FreeBSD base system build,
+ and ports built via Poudriere, were used as
+ motivating cases.</p>
+
+ <p>Mark added an in-kernel Intel CPU microcode loader. This
+ simplifies and increases the robustness of
+ microcode updates, which is increasingly important
+ as mitigations for speculative execution
+ vulnerabilities are delivered in microcode.</p>
+
+ <p>Mark also fixed a number of issues relating to capsicum
+ support in base system utilities, implemented a
+ number of NUMA enhancements and bug fixes, and
+ fixed a number of high profile kernel bugs.</p>
+
+ <p>Ed committed a large number of tool chain fixes to LLVM's
+ lld linker and ELF Tool Chain components.</p>
+
+ <p>Along with several FreeBSD developers Ed worked on the
+ OpenSSL 1.1.1 import in preparation for FreeBSD
+ 12.0, including incorporating OpenSSH and ntp
+ changes for compatibility. Ed also added
+ build-time knobs for to enable userland retpoline
+ and to enable BIND_NOW which
+ can be used as part of a vulnerability mitigation
+ strategy.</p>
+
+ <p>Continuous Integration and Quality Assurance</p>
+
+ <p>The Foundation provides a full-time staff member who is
+ working on improving our automated testing,
+ continuous integration, and overall quality
+ assurance efforts.</p>
+
+ <p>During the fourth quarter of 2018, Foundation employee
+ Li-Wen Hsu continuously worked on improving the
+ project's CI infrastructure, examining the failing
+ build and test cases, and work with other teams in
+ the project for their testing needs. In this
+ period, we also worked on collaboration with
+ external projects to improve their CI on FreeBSD.</p>
+
+ <p>See the FreeBSD CI section of this report for more
+ information.</p>
+
+ <p>Release Engineering</p>
+
+ <p>The Foundation provides a full-time staff member to lead
+ the release engineering efforts. This has provided
+ timely and reliable releases over the last five
+ years. During the fourth quarter of 2018, Glen
+ Barber led the the FreeBSD Release Engineering
+ team in continuing working on the 12.0-RELEASE
+ with the official announcement sent December 11.</p>
+
+ <p>See the FreeBSD Release Engineering Team section of this
+ report for more
+ information.</p>
+
+ <p>Supporting FreeBSD Infrastructure</p>
+
+ <p>The Foundation provides hardware and support to improve
+ the FreeBSD infrastructure. Last quarter, we
+ continued supporting FreeBSD hardware located
+ around the world.</p>
+
+ <p>FreeBSD Advocacy and Education</p>
+
+ <p>A large part of our efforts are dedicated to advocating
+ for the Project. This includes promoting work
+ being done by others with FreeBSD; producing
+ advocacy literature to teach people about FreeBSD
+ and help make the path to starting using FreeBSD
+ or contributing to the Project easier; and
+ attending and getting other FreeBSD contributors
+ to volunteer to run FreeBSD events, staff FreeBSD
+ tables, and give FreeBSD presentations.</p>
+
+ <p>The FreeBSD Foundation sponsors many conferences, events,
+ and summits around the globe. These events can be
+ BSD-related, open source, or technology events
+ geared towards underrepresented groups. We support
+ the FreeBSD-focused events to help provide a venue
+ for sharing knowledge, to work together on
+ projects, and to facilitate collaboration between
+ developers and commercial users. This all helps
+ provide a healthy ecosystem. We support the
+ non-FreeBSD events to promote and raise awareness
+ of FreeBSD, to increase the use of FreeBSD in
+ different applications, and to recruit more
+ contributors to the Project.</p>
+
+ <p>Some of the advocacy and education work we did last
+ quarter includes:</p>
+
+ <ul>
+ <li>Organized, sponsored, and presented at the October 2018
+ FreeBSD Developers Summit in Santa Clara, CA</li>
+
+ <li>Sponsored and exhibited at MeetBSD 2018 in Santa Clara, CA</li>
+
+ <li>Exhibited for the first time at All Things Open in
+ Raleigh, NC</li>
+
+ <li>Exhibited and sponsored as an Industry Partner at LISA’ 18
+ in Nashville, TN</li>
+
+ <li>Sponsored USENIX OSDI ‘18 in Carlsbad, CA as an Industry
+ Partner</li>
+
+ <li>Held an Intro to FreeBSD workshop and a “Why You Should
+ Contribute to FreeBSD” talk at the Rocky Mountain
+ Celebration of Women in Computing in Lakewood,
+ Colorado</li>
+ </ul>
+
+ <p>
+ We continued producing FreeBSD advocacy material to help
+ people promote FreeBSD around the world.</p>
+
+ <p>Read more about our conference adventures in the
+ conference recaps and trip reports in our monthly
+ newsletters: <a
+ href="https://www.freebsdfoundation.org/news-and-events/newsletter/">https://www.freebsdfoundation.org/news-and-events/newsletter/</a></p>
+
+ <p>We help educate the world about FreeBSD by publishing the
+ professionally produced FreeBSD Journal. We
+ recently announced that the FreeBSD Journal will
+ become a Free publication with the
+ January/February 2019 issue. <a
+ href="https://www.FreeBSDfoundation.org/journal/">https://www.FreeBSDfoundation.org/journal/</a>.</p>
+
+ <p>You can find out more about events we attended and
+ upcoming events at <a
+ href="https://www.FreeBSDfoundation.org/news-and-events/">https://www.FreeBSDfoundation.org/news-and-events/</a>.</p>
+
+ <p>For a look back at all of efforts in 2018, please see the
+ year-end video at <a
+ href="https://www.freebsdfoundation.org/blog/thank-you-for-supporting-freebsd/">https://www.freebsdfoundation.org/blog/thank-you-for-supporting-freebsd/</a>.</p>
+
+ <p>Legal/FreeBSD IP</p>
+
+ <p>The Foundation owns the FreeBSD trademarks, and it is our
+ responsibility to protect them. We also provide
+ legal support for the core team to investigate
+ questions that arise. Last quarter, we approved 6
+ requests to use the Trademark.
+ Go to <a
+ href="http://www.FreeBSDfoundation.org">http://www.FreeBSDfoundation.org</a>
+ to find out how we support FreeBSD and how we can
+ help you!</p>
+
+ </body>
+
+ </project>
+
+ <project cat='team'>
+ <title>Continuous Integration</title>
+
+ <contact>
+ <person>
+ <name>Jenkins Admin</name>
+ <email>jenkins-admin at FreeBSD.org</email>
+ </person>
+ <person>
+ <name>Li-Wen Hsu</name>
+ <email>lwhsu at FreeBSD.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="https://ci.FreeBSD.org">FreeBSD Jenkins Instance</url>
+ <url href="https://artifact.ci.FreeBSD.org/">FreeBSD CI artifact archive</url>
+ <url href="https://wiki.freebsd.org/Jenkins">FreeBSD Jenkins wiki</url>
+ <url href="https://lists.FreeBSD.org/mailman/listinfo/freebsd-testing">freebsd-testing Mailing List</url>
+ <url href="https://github.com/freebsd/freebsd-ci">freebsd-ci Repository</url>
+ <url href="https://preview.tinyurl.com/y9maauwg">Tickets related to freebsd-testing@</url>
+ <url href="https://wiki.freebsd.org/HostedCI">Hosted CI wiki</url>
+ </links>
+
+ <body>
+ <p>The FreeBSD CI team maintains continuous integration
+ system and related tasks
+ for the FreeBSD project. The CI system regularly checks
+ the changes committed
+ to the project's Subversion repository can be successfully
+ built, and performs
+ various tests and analysis over the results. The results
+ from build jobs are
+ archived in artifact server, for the further testing and
+ debugging needs.</p>
+
+ <p>The members on the CI team examine the failing builds and
+ unstable tests, and
+ work with the experts in that area to fix the code or
+ build and test
+ infrastructure, to improve the software quality of the
+ FreeBSD base system.
+ The CI team member and the FreeBSD foundation staff Li-Wen
+ is the maintainer of
+ Jenkins and Jenkins related ports.</p>
+
+ <p>In this quarter, we worked on extending test executing
+ environment to improve
+ the coverage, temporarily disabling flakey test cases (and
+ opening tickets to
+ work with domain experts). Please see freebsd-testing@
+ related tickets for
+ more information.</p>
+
+ <p>In addition to that, starting from this quarter, we also
+ work on collaboration
+ with external projects to extend their CI to cover
+ FreeBSD. See "HostedCI"
+ wiki page for more information.</p>
+
+ <p>Work in progress:</p>
+
+ <ul>
+ <li>Fixing the failing test cases and builds</li>
+
+ <li>Adding drm ports building test against -CURRENT</li>
+
+ <li>Adding tests for selected project branches, e.g.:
+ clang800-import</li>
+
+ <li>Implementing automatic tests on bare metal hardware</li>
+
+ <li>Planning the embedded testbed</li>
+
+ <li>Planning running ztest and network stack tests</li>
+ </ul>
+
+ <p></p>
+
+ </body>
+
+ </project>
+
+ <project cat='team'>
+ <title>FreeBSD Graphics Team status report</title>
+
+ <contact>
+ <person>
+ <name>FreeBSD Graphics Team</name>
+ <email>x11 at freebsd.org</email>
+ </person>
+ <person>
+ <name>Niclas Zeising</name>
+ <email>zeising at freebsd.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="https://github.com/FreeBSDDesktop">Project GitHub page</url>
+ </links>
+
+ <body>
+ <p>The FreeBSD X11/Graphics team maintains the lower levels
+ of the FreeBSD graphics
+ stack.
+ This includes graphics drivers, graphics libraries such as
+ the
+ MESA OpenGL implementation, the X.org xserver with related
+ libraries and
+ applications, and Wayland with related libraries and
+ applications.</p>
+
+ <p>In the forth quarter, the team focused on stablizing the
+ graphics drivers and
+ ports for the FreeBSD 12.0 release.
+ The graphics drivers have been updated with new versions
+ for both FreeBSD 11.2
+ and FreeBSD 12.0.
+ The ports have been renamed in order to make it clearer
+ which version of a port
+ runs on which version on FreeBSD.
+ We also created a new meta port,
+ <tt>graphics/drm-kmod</tt>, which will install the
+ correct driver based on FreeBSD version and architecture.
+ Moving forward this is the recommended way to install the
+ FreeBSD graphics
+ drivers.</p>
+
+ <p>The DRM drivers themselves are named
+ <tt>graphics/drm-current-kmod</tt> and
+ <tt>graphics/drm-fbsd12.0-kmod</tt> for CURRENT and 12.0
+ respectively, both of which
+ have been updated to use the 4.16 Linux Kernel source.
+ For FreeBSD 11.2 we have
+ <tt>graphics/drm-fbsd11.2-kmod</tt> which uses the
+ 4.11 Linux
+ Kernel source.
+ Finally, we created <tt>graphics/drm-legacy-kmod</tt>,
+ which works on FreeBSD 12.0 and
+ CURRENT.
+ This is a copy of the legacy drivers from the FreeBSD base
+ system.
+ This work will make it possible for us to remove the drm2
+ code from CURRENT,
+ something we are planning to do in early February.
+ A remnant of the drm2 code will remain in the base after
+ this due to an
+ unresolved dependency for the NVIDIA Tegra ARM chip.
+ Plans for its migration are expected to be finalized in
+ first quarter in 2019.</p>
+
+ <p>Support for i386 and PowerPC 64 has been added to the drm
+ kernel drivers.
+ This is currently in an alpha state.</p>
+
+ <p>Wayland has been enabled by default in the ports tree,
+ meaning that all packages
+ are build with Wayland support enabled.
+ This makes it much easier to use and test Wayland.</p>
+
+ <p>Support for VMware graphics pass through has been added to
+ the kernel driver.
+ Support for this is still missing in
+ <tt>graphcs/mesa-dri</tt> though, so it currently
+ does not work out of the box.</p>
+
+ <p>The input stack has been updated and is now for the most
+ part current with
+ upstream.
+ Evdev headers were split off from
+ <tt>multimedia/v4l_compat</tt> into their own
+ port,
+ <tt>devel/evdev-proto</tt>.
+ This makes it easier to update those headers and keep them
+ current with
+ upstream, as needed.
+ The input stack is still an area where more work needs to
+ be done to make it
+ easier to use various input devices with X and Wayland on
+ FreeBSD.</p>
+
+ <p>Several meetings has been held over the course of the
+ period.
+ Meeting notes have been sent out to the public
+ <tt>x11 at FreeBSD.org</tt> mailing list.</p>
+
+ <p>People who are interested in helping out can find us on
+ the x11 at FreeBSD.org
+ mailing list, or on our gitter chat: <a
+ href="https://gitter.im/FreeBSDDesktop/Lobby">https://gitter.im/FreeBSDDesktop/Lobby</a>.
+ We
+ are also available in #freebsd-xorg on EFNet.</p>
+
+ <p>We also have a team area on GitHub where our work
+ repositories can be found:
+ <a
+ href="https://github.com/FreeBSDDesktop">https://github.com/FreeBSDDesktop</a></p>
+
+ <p></p>
+
+ </body>
+
+ </project>
+
+ <project cat='proj'>
+ <title>amd64 Usermode Protection Keys</title>
+
+ <contact>
+ <person>
+ <name>Konstantin Belousov</name>
+ <email>kib at freebsd.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="https://reviews.freebsd.org/D18893">The patch</url>
+ </links>
+
+ <body>
+ <p>Skylake Xeons have a new feature in 4-level paging
+ implementation
+ called Usermode Protection Keys. It is a complementary
+ page access
+ permission management mechanism, which provides very
+ low-overhead
+ disabling of all accesses or only modifications, on
+ per-page basis.</p>
+
+ <p>Each thread of execution gets 16 slots, called protection
+ keys, while
+ each userspace page mapping is tagged with one key.
+ Processor
+ provides a new 32bit register PKRU, which holds access and
+ modification disable bits per key, the PKRU register is
+ automatically
+ context-switched, and managed by userspace using RDPKRU
+ and WRPKRU
+ instructions. See Intel SDM rev. 68 Vol 3 4.6.2 Protection
+ Keys for
+ further details.</p>
+
+ <p>Since a key index must be always specified, this makes the
+ key zero a
+ default key, which permissions are tricky to modify
+ without breaking
+ the process envirnment. The rest 15 keys are usable, for
+ instance
+ process might put some sensitive data like decoded private
+ key into
+ the key protected area, and only enable access on as
+ needed basis,
+ without issuing costly mprotect(2) syscall. Note that
+ permissions are
+ enforced even for kernel access, so sneaky read(2) from
+ other thread
+ is subject to the same permission checks.</p>
+
+ <p>I implemented the support for the amd64 pmap and provided
+ convenient
+ wrappers in libc both for 64bit and 32bit processes.
+ Prototypes for
+ the API are presented below and their use should be
+ obvious from the
+ explanation.</p>
+
+ <p>int x86_pkru_get_perm(unsigned int keyidx, int <tt>access,
+ int </tt>modify);
+ int x86_pkru_set_perm(unsigned int keyidx, int access, int
+ modify);
+ int x86_pkru_protect_range(void *addr, unsigned long len,
+ unsigned int keyidx, int flag);
+ int x86_pkru_unprotect_range(void *addr, unsigned long
+ len);</p>
+
+ <p></p>
+
+ </body>
+
+ <sponsor>
+ The FreeBSD Foundation
+ </sponsor>
+
+ </project>
+
+ <project cat='proj'>
+ <title>bhyve - Live Migration</title>
+
+ <contact>
+ <person>
+ <name>Elena Mihailescu</name>
+ <email>elenamihailescu22 at gmail.com</email>
+ </person>
+ <person>
+ <name>Darius Mihai</name>
+ <email>dariusmihaim at gmail.com</email>
+ </person>
+ <person>
+ <name>Sergiu Weisz</name>
+ <email>sergiu121 at gmail.com</email>
+ </person>
+ <person>
+ <name>Mihai Carabas</name>
+ <email>mihai at freebsd.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="https://github.com/FreeBSD-UPB/freebsd/wiki/Virtual-Machine-Migration-using-bhyve">Github wiki - How to Warm Migrate a bhyve guest</url>
+ <url href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration">Github - Warm Migration branch</url>
+ <url href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration_dev">Github - Live Migration branch</url>
+ </links>
+
+ <body>
+ <p>The Migration feature uses the Save/Restore feature to
+ migrate a bhyve guest
+ from a FreeBSD host to another FreeBSD host. To migrate a
+ bhyve guest,
+ one needs to start an empty guest on the destination host
+ from a shared guest
+ image using the bhyve tool with the <tt>-R</tt> option
+ followed by the source host
+ IP and the port to listen to migration request. On the
+ source host, the
+ migration is started by executing the bhyvectl command
+ with the <tt>--migrate</tt>
+ or <tt>--migrate-live</tt> option, followed by the
+ destination host IP and the
+ port to send to the messages.</p>
+
+ <p>New features added:</p>
+
+ <ul>
+ <li>Prove that live migration cannot be implemented using the
+ FreeBSD's Copy-on-Write mechanism;</li>
+
+ <li>Add <tt>--migrate-live</tt> option to bhyvectl;</li>
+
+ <li>Add additional message exchange between source and
+ destination host to establish the migration type
+ and the number of rounds;</li>
+
+ <li>Implement a dirty-bit approach for live migrating the
+ guest's wired memory;</li>
+ </ul>
+
+ <p>
+ Future tasks:</p>
+
+ <ul>
+ <li>Clear the dirty bit after each migration round;</li>
+
+ <li>Extend live migration to highmem segment;</li>
+
+ <li>Extend live migration to unwired memory;</li>
+ </ul>
+
+ <p></p>
+
+ </body>
+
+ <sponsor>
+ Matthew Grooms
+ </sponsor>
+
+ </project>
+
+ <project cat='proj'>
+ <title>bhyve - Save/Restore</title>
+
+ <contact>
+ <person>
+ <name>Elena Mihailescu</name>
+ <email>elenamihailescu22 at gmail.com</email>
+ </person>
+ <person>
+ <name>Darius Mihai</name>
+ <email>dariusmihaim at gmail.com</email>
+ </person>
+ <person>
+ <name>Sergiu Weisz</name>
+ <email>sergiu121 at gmail.com</email>
+ </person>
+ <person>
+ <name>Mihai Carabas</name>
+ <email>mihai at freebsd.org</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="https://github.com/FreeBSD-UPB/freebsd/tree/projects/bhyve_migration">Github repository for the save/restore and migration features</url>
+ <url href="https://github.com/FreeBSD-UPB/freebsd/wiki/Save-and-Restore-a-virtual-machine-using-bhyve">Github wiki - How to Save and Restore a bhyve guest</url>
+ <url href="https://github.com/FreeBSD-UPB/freebsd/wiki/Suspend-Resume-test-matrix">Github wiki - Suspend/resume test matrix</url>
+ </links>
+
+ <body>
+ <p>The Save/Restore for bhyve feature is a suspend and resume
+ facility added to the
+ FreeBSD/amd64's hypervisor, bhyve. The bhyvectl tool is
+ used to save the guest
+ state in three files (a file for the guest memory, a file
+ for devices' and CPU's
+ state and another one for some metadata that are used in
+ the restore process).
+ To suspend a bhyve guest, the bhyvectl tool must be run
+ with the <tt>--suspend
+ <state_file_name></tt>
+ option followed by the guest name.</p>
+
+ <p>To restore a bhyve guest from a checkpoint, one simply has
+ to add the <tt>-r</tt> option
+ followed by the main state file (the same file that was
+ given to the <tt>--suspend</tt>
+ option for bhyvectl) when starting the VM.</p>
+
+ <p>New features added:</p>
+
+ <ul>
+ <li>Improve timers' save and restore state feature;</li>
+
+ <li>Fix synchronization issues related to the ahci device save
+ and restore state feature;</li>
+
+ <li>Add suspend/resume support for Windows guests;</li>
+
+ <li>Refactor save and restore code - save component's state
+ field by field</li>
+ </ul>
+
+ <p>
+ Future tasks:</p>
+
+ <ul>
+ <li>Open ticket on Phabricator;</li>
+
+ <li>Add suspend/resume support for nvme;</li>
+
+ <li>Add suspend/resume support for virtio-console;</li>
+
+ <li>Add suspend/resume support for virtio-scsi;</li>
+
+ <li>Add TSC offseting for restore for AMD CPUs;</li>
+ </ul>
+
+ <p></p>
+
+ </body>
+
+ <sponsor>
+ Matthew Grooms; iXsystems;
+ </sponsor>
+
+ </project>
+
+ <project cat='proj'>
+ <title>Improving FreeBSD boot security</title>
+
+ <contact>
+ <person>
+ <name>Michal Stanek</name>
+ <email>mst at semihalf.com</email>
+ </person>
+ <person>
+ <name>Marcin Wojtas</name>
+ <email>mw at semihalf.com</email>
+ </person>
+ <person>
+ <name>Kornel Duleba</name>
+ <email>mindal at semihalf.com</email>
+ </person>
+ </contact>
+
+ <links>
+ <url href="https://svnweb.freebsd.org/base/head/sys/dev/tpm/tpm20.c?revision=342084&nview=markup">TPM 2.0 driver</url>
+ <url href="https://reviews.freebsd.org/D18798">Loader Secure Boot support</url>
+ <url href="https://reviews.freebsd.org/D18797">Secure Boot library</url>
+ <url href="https://reviews.freebsd.org/D18799">binsign utility</url>
+ </links>
+
+ <body>
+ <p>FreeBSD now supports TPM 2.0 devices. TPM (Trusted
+ Platform Module) is a discrete chip which provides
+ secure computation and secure NVRAM storage. It is
+ most
+ commonly associated with Measured Boot i.e. providing hash
+ measurements of boot elements such as firmware
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
More information about the svn-doc-all
mailing list