From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Itaru Kitayama <itaru.kitayama@linux.dev>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: New "rme-guest" QEMU object addition
Date: Thu, 21 Nov 2024 09:58:55 +0000 [thread overview]
Message-ID: <Zz8EX70z9qyLcEQg@redhat.com> (raw)
In-Reply-To: <8A08FAE0-3712-4EFD-A39F-3D39D92B8B07@linux.dev>
On Thu, Nov 21, 2024 at 06:55:18PM +0900, Itaru Kitayama wrote:
>
>
> > On Nov 21, 2024, at 18:53, Daniel P. Berrangé <berrange@redhat.com> wrote:
> >
> > 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?
> >
> > Is the CCA host kernel support merged yet ? As a general rule we would
> > not expect to merge QEMU support for a feature, until after the corresponding
> > kernel support is merged.
> >
>
> Ah, only the guest part. So now I understand.
You can still post PoC patches for libvirt based on the latest out of
tree QEMU code. We'll review them in the normal way, and then when the
kernel & QEMU stuff does merge, there'll be minimal further delay on
merging the libvirt side.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev 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é [this message]
2024-11-21 10:15 ` Itaru Kitayama
2024-11-21 10:00 ` Jean-Philippe Brucker
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=Zz8EX70z9qyLcEQg@redhat.com \
--to=berrange@redhat.com \
--cc=itaru.kitayama@linux.dev \
--cc=jean-philippe@linaro.org \
--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.