Re: [Xen-devel] [PATCH 5/5] xen/arm: optee: remove experimental status
Hi Volodymyr, On 9/11/19 7:41 PM, Volodymyr Babchuk wrote: Julien Grall writes: On 8/23/19 8:20 PM, Volodymyr Babchuk wrote: Hi Julien, Hi, Apologies for the delay. It is okay. I myself was busy a bit. Julien Grall writes: Hi, On 8/23/19 7:48 PM, Volodymyr Babchuk wrote: As all TODOs and potential security issues are resolved now, remove experimental status from OP-TEE mediator. Looking at SUPPORT.MD, I think OP-TEE without this series would be considered as "Experimental". Right. With this series applied, I still think we should keep the Kconfig behind EXPERT but mark it as "Technical Preview" for at least a release. This would encourage people to test and report any potential issues with OP-TEE. We can re-discuss about the state in a few months for future release. BTW, SUPPORT.MD should be updated to reflect the state of OP-TEE in Xen. Fair enough. In the next version I'll replace this patch with patch to SUPPORT.md. Or it is better to push separate patch for the documentation? I think the patch in SUPPORT.MD should go regardless of the state of the rest. It is fine to keep it in this series. Okay. By the way, I skimmed thru SUPPORT.MD and I'm not sure what is the best place to describe mediator. So I could use some advice there. Good question. I would put it under "## Virtual Hardware, Hypervisor". Maybe after the subsection "### ARM: Guest ACPI support"? Cheers, -- Julien Grall ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [PATCH 5/5] xen/arm: optee: remove experimental status
Julien Grall writes: > On 8/23/19 8:20 PM, Volodymyr Babchuk wrote: >> >> Hi Julien, > > Hi, > > Apologies for the delay. It is okay. I myself was busy a bit. > >> >> Julien Grall writes: >> >>> Hi, >>> >>> On 8/23/19 7:48 PM, Volodymyr Babchuk wrote: As all TODOs and potential security issues are resolved now, remove experimental status from OP-TEE mediator. >>> >>> Looking at SUPPORT.MD, I think OP-TEE without this series would be >>> considered as "Experimental". >> Right. >> >>> >>> With this series applied, I still think we should keep the Kconfig >>> behind EXPERT but mark it as "Technical Preview" for at least a >>> release. This would encourage people to test and report any potential >>> issues with OP-TEE. >>> >>> We can re-discuss about the state in a few months for future release. >>> >>> BTW, SUPPORT.MD should be updated to reflect the state of OP-TEE in Xen. >> Fair enough. In the next version I'll replace this patch with patch to >> SUPPORT.md. Or it is better to push separate patch for the documentation? > > I think the patch in SUPPORT.MD should go regardless of the state of > the rest. It is fine to keep it in this series. Okay. By the way, I skimmed thru SUPPORT.MD and I'm not sure what is the best place to describe mediator. So I could use some advice there. -- Volodymyr Babchuk at EPAM ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [PATCH 5/5] xen/arm: optee: remove experimental status
On 8/23/19 8:20 PM, Volodymyr Babchuk wrote: Hi Julien, Hi, Apologies for the delay. Julien Grall writes: Hi, On 8/23/19 7:48 PM, Volodymyr Babchuk wrote: As all TODOs and potential security issues are resolved now, remove experimental status from OP-TEE mediator. Looking at SUPPORT.MD, I think OP-TEE without this series would be considered as "Experimental". Right. With this series applied, I still think we should keep the Kconfig behind EXPERT but mark it as "Technical Preview" for at least a release. This would encourage people to test and report any potential issues with OP-TEE. We can re-discuss about the state in a few months for future release. BTW, SUPPORT.MD should be updated to reflect the state of OP-TEE in Xen. Fair enough. In the next version I'll replace this patch with patch to SUPPORT.md. Or it is better to push separate patch for the documentation? I think the patch in SUPPORT.MD should go regardless of the state of the rest. It is fine to keep it in this series. Cheers, -- Julien Grall ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [PATCH 5/5] xen/arm: optee: remove experimental status
Hi Julien, Julien Grall writes: > Hi, > > On 8/23/19 7:48 PM, Volodymyr Babchuk wrote: >> As all TODOs and potential security issues are resolved now, >> remove experimental status from OP-TEE mediator. > > Looking at SUPPORT.MD, I think OP-TEE without this series would be > considered as "Experimental". Right. > > With this series applied, I still think we should keep the Kconfig > behind EXPERT but mark it as "Technical Preview" for at least a > release. This would encourage people to test and report any potential > issues with OP-TEE. > > We can re-discuss about the state in a few months for future release. > > BTW, SUPPORT.MD should be updated to reflect the state of OP-TEE in Xen. Fair enough. In the next version I'll replace this patch with patch to SUPPORT.md. Or it is better to push separate patch for the documentation? -- Volodymyr Babchuk at EPAM ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] [PATCH 5/5] xen/arm: optee: remove experimental status
Hi, On 8/23/19 7:48 PM, Volodymyr Babchuk wrote: As all TODOs and potential security issues are resolved now, remove experimental status from OP-TEE mediator. Looking at SUPPORT.MD, I think OP-TEE without this series would be considered as "Experimental". With this series applied, I still think we should keep the Kconfig behind EXPERT but mark it as "Technical Preview" for at least a release. This would encourage people to test and report any potential issues with OP-TEE. We can re-discuss about the state in a few months for future release. BTW, SUPPORT.MD should be updated to reflect the state of OP-TEE in Xen. Cheers, -- Julien Grall ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
