qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Igor Mammedov <imammedo@redhat.com>,
	Ani Sinha <anisinha@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	Eduardo Habkost <eduardo@habkost.net>,
	 Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
	Peter Hilber <peter.hilber@opensynergy.com>,
	"Mohamed Abuelfotoh, Hazem" <abuehaze@amazon.com>
Subject: Re: [PATCH v2] hw/acpi: Add vmclock device
Date: Thu, 01 Aug 2024 11:00:05 +0100	[thread overview]
Message-ID: <e3432911c2083ffaddf45ad23aece6322a4105f1.camel@infradead.org> (raw)
In-Reply-To: <20240801054718-mutt-send-email-mst@kernel.org>

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

On Thu, 2024-08-01 at 05:48 -0400, Michael S. Tsirkin wrote:
> On Thu, Aug 01, 2024 at 09:49:06AM +0100, David Woodhouse wrote:
> > On Wed, 2024-07-31 at 17:19 -0400, Michael S. Tsirkin wrote:
> > > 
> > > > Perfect. So as and when the header is in its final form in Linux,
> > > > it can be part of the automated import and we'll use that version.
> > > > At that point we can drop the one that's sitting alongside the
> > > > device itself in hw/acpi/.
> > > 
> > > Yes. Maybe add a comment in the temporary header.
> > 
> > I pondered that, but kind of preferred to have it byte-identical.
> > 
> > Admittedly I'm not *planning* to have to change it any more but it's
> > been useful so far that I can just *copy* the file between the Linux
> > and Linux-backport and QEMU repositories.
> 
> ok. note machinery we have is clever, it handles __le and such stuff
> automatically.

Sure. But the *temporary* file in hw/acpi isn't using that machinery;
it's literally just copied.

I can add a comment in the vmclock.c file where we *include* it, noting
that it's sitting here in the same directory for now, but in the
fullness of time it will be imported from Linux.

--- a/hw/acpi/vmclock.c
+++ b/hw/acpi/vmclock.c
@@ -22,6 +22,7 @@
 #include "migration/vmstate.h"
 #include "sysemu/reset.h"
 
+/* This will come from Linux headers in the end, but we carry our own for now. */
 #include "vmclock-abi.h"
 
 void vmclock_build_acpi(VmclockState *vms, GArray *table_data,


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

      reply	other threads:[~2024-08-01 10:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30 16:33 [PATCH v2] hw/acpi: Add vmclock device David Woodhouse
2024-07-30 17:53 ` Michael S. Tsirkin
2024-07-30 19:04   ` David Woodhouse
2024-07-30 20:45     ` Michael S. Tsirkin
2024-07-31  0:23       ` David Woodhouse
2024-07-31 21:19         ` Michael S. Tsirkin
2024-08-01  8:49           ` David Woodhouse
2024-08-01  9:48             ` Michael S. Tsirkin
2024-08-01 10:00               ` David Woodhouse [this message]

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=e3432911c2083ffaddf45ad23aece6322a4105f1.camel@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=abuehaze@amazon.com \
    --cc=anisinha@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=imammedo@redhat.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.hilber@opensynergy.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).