On Thu, Nov 18, 2021 at 09:04:30PM +0200, Oleksandr wrote: > > On 18.11.21 19:33, Roger Pau Monné wrote: > > Hi Roger > > > > On Thu, Nov 18, 2021 at 06:11:07PM +0200, Oleksandr Tyshchenko wrote: > > > On Wed, Nov 17, 2021 at 11:54 AM Roger Pau Monne <roger....@citrix.com> > > > wrote: > > > > > > Hi Roger, all > > > > > > [Sorry for the possible format issues] > > > > > > Document some of the relevant changes during the 4.16 release cycle, > > > > likely more entries are missing. > > > > > > > > Signed-off-by: Roger Pau Monné <roger....@citrix.com> > > > > --- > > > > CHANGELOG.md | 11 +++++++++++ > > > > 1 file changed, 11 insertions(+) > > > > > > > > diff --git a/CHANGELOG.md b/CHANGELOG.md > > > > index ad1a8c2bc2..8b0bdd9cf0 100644 > > > > --- a/CHANGELOG.md > > > > +++ b/CHANGELOG.md > > > > @@ -21,6 +21,17 @@ The format is based on [Keep a Changelog]( > > > > https://keepachangelog.com/en/1.0.0/) > > > > - qemu-traditional based device models (both, qemu-traditional and > > > > ioemu-stubdom) will > > > > no longer be built per default. In order to be able to use those, > > > > configure needs to > > > > be called with "--enable-qemu-traditional" as parameter. > > > > + - Fixes for credit2 scheduler stability in corner case conditions. > > > > + - Ongoing improvements in the hypervisor build system. > > > > + - vtpmmgr miscellaneous fixes in preparation for TPM 2.0 support. > > > > + - 32bit PV guests only supported in shim mode. > > > > + - Improved PVH dom0 debug key handling. > > > > + - Fix booting on some Intel systems without a PIT (i8254). > > > > > > > I would add "Various fixes for OP-TEE mediator (Arm)" here and ... > > > > > > > > > > > > > + > > > > +### Added > > > > + - 32bit Arm builds to the automated tests. > > > > + - New x86 pagetable APIs. > > > > + - Arm vPMU support. > > > > > > > "Extended regions support, device tree only (Arm)" here. > > > > > > ... > > > The extended regions are ranges of unused address space exposed to domains > > > as > > > "safe to use" for special memory mappings. > > I've worded this as: > > > > "Report unpopulated memory regions safe to use for foreign mappings, > > Arm and device tree only." > > > > As "extended regions" was IMO too vague. Let me know if that's OK. > > I think, it is OK. Nit: maybe replace "foreign" with "foreign/grant"? I > would be OK either way.
Maybe, I would consider grants as foreign mappings also, ie: the memory is foreign to the domain, but I can see this being confusing as we have a specific kind of mappings that are named foreign. Does replacing foreign with external seem better? Thanks, Roger.
