All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Xiaoyao Li <xiaoyao.li@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org, Chenyi Qiang <chenyi.qiang@intel.com>,
	Binbin Wu <binbin.wu@linux.intel.com>,
	Isaku Yamahata <isaku.yamahata@intel.com>
Subject: Re: [PATCH 3/3] i386/tdx: handle TDG.VP.VMCALL<GetQuote>
Date: Fri, 20 Jun 2025 09:09:07 +0100	[thread overview]
Message-ID: <aFUXI5noscw_DfP5@redhat.com> (raw)
In-Reply-To: <c60001b3-12d2-4261-8b6b-a7bfaf4e71ff@intel.com>

On Fri, Jun 20, 2025 at 02:47:46PM +0800, Xiaoyao Li wrote:
> On 6/20/2025 4:33 AM, Paolo Bonzini wrote:

> > +static gboolean tdx_get_quote_read(QIOChannel *ioc, GIOCondition condition,
> > +                                   gpointer opaque)
> > +{
> ...> +    if (task->receive_buf_received >= (sizeof(qgs_msg_header_t) +
> HEADER_SIZE)) {
> > +        qgs_msg_header_t *hdr = (qgs_msg_header_t *)(task->receive_buf + HEADER_SIZE);
> > +        if (hdr->major_version != QGS_MSG_LIB_MAJOR_VER ||
> > +            hdr->minor_version != QGS_MSG_LIB_MINOR_VER) {
> 
> This check makes it fail with old QGS, which defines
> 
> QGS_MSG_LIB_MINOR_VER as 0,
> 
> so what QEMU gets is 1.0 instead of 1.1.
> 
> It is really a QGS bug that when it changes QGS_MSG_LIB_MINOR_VER from 0 to
> 1, it didn't consider the compatible issue.
> 
> However, the old QGS is there. Should we relax the check here for it? or
> just let it fail with old QGS?

AFAICT, MINOR_VER==1 was introduced in DCAP 1.21 from Apr 2024

Given that this is new functionality in QEMU, I don't think we
have to worry about versions of DCAP so far behind the latest
version.


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 :|



  parent reply	other threads:[~2025-06-20  8:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19 20:33 [RFC PATCH 0/3] TDX attestation support Paolo Bonzini
2025-06-19 20:33 ` [PATCH 1/3] update Linux headers to v6.16-rc3 Paolo Bonzini
2025-06-19 20:33 ` [PATCH 2/3] i386/tdx: handle TDG.VP.VMCALL<GetTdVmCallInfo> Paolo Bonzini
2025-06-19 20:33 ` [PATCH 3/3] i386/tdx: handle TDG.VP.VMCALL<GetQuote> Paolo Bonzini
2025-06-20  6:47   ` Xiaoyao Li
2025-06-20  7:47     ` Paolo Bonzini
2025-06-20  8:02       ` Xiaoyao Li
2025-06-20  8:09     ` Daniel P. Berrangé [this message]
2025-06-20  6:53 ` [RFC PATCH 0/3] TDX attestation support Xiaoyao Li

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=aFUXI5noscw_DfP5@redhat.com \
    --to=berrange@redhat.com \
    --cc=binbin.wu@linux.intel.com \
    --cc=chenyi.qiang@intel.com \
    --cc=isaku.yamahata@intel.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=xiaoyao.li@intel.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 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.