Hi Jean,

> On Nov 21, 2024, at 19:00, Jean-Philippe Brucker <[email protected]> 
> wrote:
> 
> Hi Itaru,
> 
> On Thu, Nov 21, 2024 at 02:34:24PM +0900, Itaru Kitayama wrote:
>> Hi Jean, Mathieu,
>> 
>> I’ve been using you guys’ ccs/v3 QEMU for some time to bring up an Realm 
>> instance without a major issue, and as a one who is making changes libvirt 
>> to support CCA, I wonder if you could merge the v3 local changes under qap 
>> dir first so I can query the feature from libvirt?
> 
> I'm not very familiar with libvirt, which changes are needed for query,
> this one:
> https://git.codelinaro.org/linaro/dcap/qemu/-/commit/250732e03bf0bd2e2a9058358707baf51d0193cb#68c067b8d3c460fb3331256759e405f48df64c73
> ?

Yes, but I wasn’t aware of the Kim-rme,c code under the target/arm. I am trying 
to generate C code using the QAPI so that we can issue QMP command like other 
CoCo, SEV(-SNP) and SGX.
Is this the way forward for Arm CCA support I wonder?

For now the focus is on getting a reasonable output of `virsh domcapabilities 
—emulatorbin qemu-system-aarch64` and getting virsh edit can be finished 
without a complain if I added <launchSecurity/> and <cca/>
elements.
 
Thanks,
Itaru.

> 
> The problem for upstreaming QEMU VMM patches is that the whole series
> depends on the updated KVM API, so until that gets merged in Linux I can't
> get the QEMU patches merged
> https://git.codelinaro.org/linaro/dcap/qemu/-/commit/bb044aeb5bf888f193b1def0a4d03de2ff8389ac
> https://lore.kernel.org/linux-arm-kernel/[email protected]/
> And without the KVM API we can't allow users to create a rme-guest object,
> since it wouldn't be functional.
> 
> Thanks,
> Jean


Reply via email to