> On Jul 29, 2019, at 10:45, Jan Beulich <jbeul...@suse.com> wrote: > >> On 29.07.2019 16:39, Lukasz Hawrylko wrote: >> Support for Intel TXT has orphaned status right now because >> no active maintainter is listed. Adding myself as active maintainter, >> so it could be reverted to supported state. > > Which you should then do ... > >> --- a/MAINTAINERS >> +++ b/MAINTAINERS >> @@ -240,6 +240,7 @@ S: Maintained >> F: tools/golang >> >> INTEL(R) TRUSTED EXECUTION TECHNOLOGY (TXT) >> +M: Lukasz Hawrylko <lukasz.hawry...@intel.com> >> S: Orphaned > > ... right here. The question is what new state you want to put > it into. But it was suggested anyway that you add yourself as > reviewer first, at which point the new state would probably be > "Odd Fixes".
There is no status for Intel TXT documented in SUPPORT.md [1]. What's the established mapping between "Odd Fixes" in Maintainers and support status in SUPPORT.md? At present, MAINTAINERS generalizes "tboot support" to "Intel TXT". This will change with TrenchBoot (discussed at Xen Summit) [2] and "secure launch" [3] for the Linux kernel, which will support Intel TXT and AMD SKINIT variants of DRTM. At that point, there will be tboot and TrenchBoot for Intel TXT, with different Xen maintainers and potentially different levels of support. We will eventually need to document Xen's DRTM status on Intel, AMD and Arm/Qualcomm, in both SUPPORT.md and MAINTAINERS. Rich [1] SUPPORT.md, https://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=SUPPORT.md;hb=refs/heads/stable-4.12 [2] TrenchBoot, https://youtube.com/watch?v=f0LZFSq4Ack [3] kernel_info, https://lkml.org/lkml/2019/5/24/330
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
