qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Cornelia Huck <cohuck@redhat.com>,
	"Chalios, Babis" <bchalios@amazon.es>,
	 "mst@redhat.com" <mst@redhat.com>,
	"imammedo@redhat.com" <imammedo@redhat.com>,
	 "pbonzini@redhat.com" <pbonzini@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, "Graf (AWS),
	Alexander" <graf@amazon.de>,
	"mzxreary@0pointer.de" <mzxreary@0pointer.de>
Subject: Re: [RFC PATCH 2/4] hw/acpi: add new fields in VMClock ABI
Date: Mon, 01 Dec 2025 14:27:00 +0000	[thread overview]
Message-ID: <8e8ab56ce4f8f2a0f0c084bd4e48958a441b40f1.camel@infradead.org> (raw)
In-Reply-To: <87ldjmnwyt.fsf@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2184 bytes --]

On Mon, 2025-12-01 at 14:38 +0100, Cornelia Huck wrote:
> On Mon, Dec 01 2025, David Woodhouse <dwmw2@infradead.org> wrote:
> 
> > On Mon, 2025-12-01 at 14:04 +0100, Cornelia Huck wrote:
> > > On Mon, Dec 01 2025, "Chalios, Babis" <bchalios@amazon.es> wrote:
> > > 
> > > > VMClock now supports a vm_generation_counter field in the struct it
> > > > exposes to userspace. The field signals a disruption that happened due
> > > > to a guest loaded from a snapshot.
> > > > 
> > > > Moreover, VMClock now optionally supports device notifications when the
> > > > seq_count changes to a new even value.
> > > > 
> > > > Signed-off-by: Babis Chalios <bchalios@amazon.es>
> > > > ---
> > > >  include/standard-headers/linux/vmclock-abi.h | 20 ++++++++++++++++++++
> > > >  1 file changed, 20 insertions(+)
> > > 
> > > Please either do a full linux-headers update against a specific Linux
> > > kernel version, or mark this as a placeholder patch if the code is not
> > > yet merged.
> > 
> > The Linux patches are being posted simultaneously, so they'll be in
> > Linux 6.20 (7.0?) at the earliest. We'll want to ingest the update
> > before then.
> > 
> > The intent is not for the Linux source to be the canonical definition
> > of the data structure; we *are* working on publishing the spec, and
> > Babis referenced the current draft. It isn't in the form of C source
> > code though, so I suspect it makes sense to keep including the Linux
> > header?
> 
> Oh, including the Linux header sounds fine; but as long as the code has
> not yet been merged there, this needs to be marked as not yet ready to
> merge on the QEMU side. (And it needs to be updated by a full headers
> update when merged.)

That's exactly what we *don't* want, and why we say that the canonical
definition of this structure is the actual specification. There's no
need for QEMU to only ever follow Linux.

In that case, probably best *not* to use the Linux header and instead
to build our own specifically for QEMU based on the specification. It
can be almost byte-for-byte identical, but just needs to live elsewhere
rather than in <standard-headers/linux>



[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5069 bytes --]

  reply	other threads:[~2025-12-01 14:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-01 12:50 [RFC PATCH 0/4] vmclock: add support for VM generation counter and notifications Chalios, Babis
2025-12-01 12:50 ` Chalios, Babis
2025-12-01 12:52   ` Babis Chalios
2025-12-01 12:50 ` [RFC PATCH 1/4] acpi: fix acpi_send_gpe_event() to handle more events Chalios, Babis
2025-12-01 12:50 ` [RFC PATCH 2/4] hw/acpi: add new fields in VMClock ABI Chalios, Babis
2025-12-01 13:04   ` Cornelia Huck
2025-12-01 13:11     ` Babis Chalios
2025-12-01 13:36       ` Cornelia Huck
2025-12-01 13:24     ` David Woodhouse
2025-12-01 13:38       ` Cornelia Huck
2025-12-01 14:27         ` David Woodhouse [this message]
2025-12-01 15:05           ` Babis Chalios
2025-12-01 15:21             ` David Woodhouse
2025-12-01 15:10           ` Cornelia Huck
2025-12-01 12:51 ` [RFC PATCH 3/4] hw/acpi: add VM generation counter field to VMClock Chalios, Babis
2025-12-01 14:12   ` Daniel P. Berrangé
2025-12-01 14:29     ` David Woodhouse
2025-12-01 14:41       ` Daniel P. Berrangé
2025-12-01 15:01         ` Babis Chalios
2025-12-01 15:28           ` David Woodhouse
2025-12-01 12:51 ` [RFC PATCH 4/4] hw/acpi: add ACPI notification to VMClock device Chalios, Babis
2025-12-01 15:10 ` [RFC PATCH 0/4] vmclock: add support for VM generation counter and notifications Daniel P. Berrangé
2025-12-01 15:23   ` David Woodhouse
2025-12-01 15:46   ` Babis Chalios

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=8e8ab56ce4f8f2a0f0c084bd4e48958a441b40f1.camel@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=bchalios@amazon.es \
    --cc=cohuck@redhat.com \
    --cc=graf@amazon.de \
    --cc=imammedo@redhat.com \
    --cc=mst@redhat.com \
    --cc=mzxreary@0pointer.de \
    --cc=pbonzini@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).