From: Jerome Forissier <jerome@forissier.org>
To: Volodymyr Babchuk <vlad.babchuk@gmail.com>
Cc: Jens Wiklander <jens.wiklander@linaro.org>,
Sumit Garg <sumit.garg@linaro.org>,
"op-tee@lists.trustedfirmware.org"
<op-tee@lists.trustedfirmware.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Tyler Hicks <tyhicks@linux.microsoft.com>
Subject: Re: optee: regression with kernel v5.14 (virtualization)
Date: Tue, 28 Sep 2021 15:35:31 +0200 [thread overview]
Message-ID: <cbcae077-3ebe-42b0-cbfe-cf5491f9ee0e@forissier.org> (raw)
In-Reply-To: <CAOcqxo339CS63i5sMdweqx3MO7ME9TxFPJe-p-ESWME=vSzLwg@mail.gmail.com>
On 9/28/21 3:15 PM, Volodymyr Babchuk wrote:
> Hi Jerome,
>
> On Tue, 28 Sept 2021 at 16:08, Jerome Forissier <jerome@forissier.org> wrote:
>>
>> Hi,
>>
>> I met an issue when testing OP-TEE with the latest released kernel
>> (v5.14). The kernel won't boot when virtualization is enabled. More
>> precisely, the boot hangs as the optee driver is probed. The last line
>> on the console is:
>>
>> [xxx] optee: probing for conduit method.
>>
>> The issue can easily be reproduced in the QEMU OP-TEE environment as
>> documented in [1]:
>>
>> $ repo init -u https://github.com/OP-TEE/manifest.git -m qemu_v8.xml
>> $ repo sync -j10
>> $ cd linux
>> $ git fetch github --unshallow
>> $ git checkout v5.14
>> $ cd ../build
>> $ make -j2 toolchains
>> $ make -j10 XEN_BOOT=y run
>>
>> [Note, if you switch between XEN_BOOT=y and the default build, you need
>> to "make arm-tf-clean"]
>>
>> git bisect points at commit b5c10dd04b74 ("optee: Clear stale cache
>> entries during initialization") and reverting this commit on top of
>> v5.14 does resolve the issue.
>>
>> Any idea what's wrong?
>
> Yes, there was a small mistake in the mediator. My colleague already
> pushed the patch. It is at staging now:
>
> http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=1c3ed9c908732d19660fbe83580674d585464d4c
>
> And will be backported to Xen 4.13+
Awesome :) Thanks Vlad!
--
Jerome
prev parent reply other threads:[~2021-09-28 13:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 13:08 Jerome Forissier
2021-09-28 13:15 ` Volodymyr Babchuk
2021-09-28 13:35 ` Jerome Forissier [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=cbcae077-3ebe-42b0-cbfe-cf5491f9ee0e@forissier.org \
--to=jerome@forissier.org \
--cc=jens.wiklander@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=sumit.garg@linaro.org \
--cc=tyhicks@linux.microsoft.com \
--cc=vlad.babchuk@gmail.com \
/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
all inboxes | Powered by JetHome®