From: Julien Grall <julien.grall@arm.com>
To: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Cc: "tee-dev@lists.linaro.org" <tee-dev@lists.linaro.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [Xen-devel] [PATCH 5/5] xen/arm: optee: remove experimental status
Date: Thu, 12 Sep 2019 20:00:08 +0100 [thread overview]
Message-ID: <85d27ba4-ae9b-f704-a074-913d5bc87059@arm.com> (raw)
In-Reply-To: <87lfuufzfk.fsf@epam.com>
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
prev parent reply other threads:[~2019-09-12 19:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 18:48 [Xen-devel] [PATCH 0/5] arch/arm: optee: fix TODOs and remove "experimental" status Volodymyr Babchuk
2019-08-23 18:48 ` [Xen-devel] [PATCH 1/5] xen/arm: optee: impose limit on shared buffer size Volodymyr Babchuk
2019-09-09 22:11 ` Julien Grall
2019-09-11 18:48 ` Volodymyr Babchuk
2019-09-12 19:32 ` Julien Grall
2019-09-12 19:45 ` Volodymyr Babchuk
2019-09-12 19:51 ` Julien Grall
2019-09-16 15:26 ` Volodymyr Babchuk
2019-09-17 10:49 ` Julien Grall
2019-09-17 12:28 ` Volodymyr Babchuk
2019-09-17 18:46 ` Julien Grall
2019-08-23 18:48 ` [Xen-devel] [PATCH 2/5] xen/arm: optee: check for preemption while freeing shared buffers Volodymyr Babchuk
2019-09-09 22:19 ` Julien Grall
2019-09-11 18:53 ` Volodymyr Babchuk
2019-09-12 19:39 ` Julien Grall
2019-09-12 19:47 ` Volodymyr Babchuk
2019-08-23 18:48 ` [Xen-devel] [PATCH 3/5] xen/arm: optee: limit number of " Volodymyr Babchuk
2019-08-23 18:48 ` [Xen-devel] [PATCH 4/5] xen/arm: optee: handle share buffer translation error Volodymyr Babchuk
2019-09-10 11:17 ` Julien Grall
2019-09-11 18:32 ` Volodymyr Babchuk
2019-09-12 18:55 ` Julien Grall
2019-08-23 18:48 ` [Xen-devel] [PATCH 5/5] xen/arm: optee: remove experimental status Volodymyr Babchuk
2019-08-23 19:05 ` Julien Grall
2019-08-23 19:20 ` Volodymyr Babchuk
2019-09-09 21:31 ` Julien Grall
2019-09-11 18:41 ` Volodymyr Babchuk
2019-09-12 19:00 ` Julien Grall [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85d27ba4-ae9b-f704-a074-913d5bc87059@arm.com \
--to=julien.grall@arm.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=sstabellini@kernel.org \
--cc=tee-dev@lists.linaro.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).