All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: Itaru Kitayama <itaru.kitayama@linux.dev>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>, qemu-devel@nongnu.org
Subject: Re: New "rme-guest" QEMU object addition
Date: Thu, 21 Nov 2024 10:00:00 +0000	[thread overview]
Message-ID: <20241121100000.GA2024976@myrica> (raw)
In-Reply-To: <9FF5EDFD-6026-4C3A-A6A1-A66521D837A5@linux.dev>

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
?

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/20241004152804.72508-1-steven.price@arm.com/
And without the KVM API we can't allow users to create a rme-guest object,
since it wouldn't be functional.

Thanks,
Jean


  parent reply	other threads:[~2024-11-21  9:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21  5:34 New "rme-guest" QEMU object addition Itaru Kitayama
2024-11-21  9:53 ` Daniel P. Berrangé
2024-11-21  9:55   ` Itaru Kitayama
2024-11-21  9:58     ` Daniel P. Berrangé
2024-11-21 10:15       ` Itaru Kitayama
2024-11-21 10:00 ` Jean-Philippe Brucker [this message]
2024-11-21 10:22   ` Itaru Kitayama

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=20241121100000.GA2024976@myrica \
    --to=jean-philippe@linaro.org \
    --cc=itaru.kitayama@linux.dev \
    --cc=mathieu.poirier@linaro.org \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.