All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Adrian Catangiu <acatan@amazon.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	qemu-devel@nongnu.org, kvm@vger.kernel.org,
	linux-s390@vger.kernel.org, gregkh@linuxfoundation.org,
	graf@amazon.com, rdunlap@infradead.org, arnd@arndb.de,
	ebiederm@xmission.com, rppt@kernel.org, 0x7f454c46@gmail.com,
	borntraeger@de.ibm.com, Jason@zx2c4.com, jannh@google.com,
	w@1wt.eu, colmmacc@amazon.com, luto@kernel.org, tytso@mit.edu,
	ebiggers@kernel.org, dwmw@amazon.co.uk, bonzini@gnu.org,
	sblbir@amazon.com, raduweis@amazon.com, corbet@lwn.net,
	mhocko@kernel.org, rafael@kernel.org, pavel@ucw.cz,
	mpe@ellerman.id.au, areber@redhat.com, ovzxemul@gmail.com,
	avagin@gmail.com, ptikhomirov@virtuozzo.com, gil@azul.com,
	asmehra@redhat.com, dgunigun@redhat.com, vijaysun@ca.ibm.com,
	oridgar@gmail.com, ghammer@redhat.com
Subject: Re: [PATCH v5 2/2] drivers/virt: vmgenid: add vm generation id driver
Date: Tue, 9 Feb 2021 09:55:32 -0500	[thread overview]
Message-ID: <20210209095350-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1612200294-17561-3-git-send-email-acatan@amazon.com>

> +The ``vmgenid`` driver uses ACPI events to be notified by hardware
> +changes to the 128-bit Vm Gen Id UUID.

That's ok, problem is ACPI event processing is asynchronous.
What we need is thus to flush out ACPI events whenever userspace
does a read, otherwise the value it gets will be stale.

-- 
MST


WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Adrian Catangiu <acatan@amazon.com>
Cc: Jason@zx2c4.com, areber@redhat.com, kvm@vger.kernel.org,
	linux-doc@vger.kernel.org, ghammer@redhat.com,
	vijaysun@ca.ibm.com, 0x7f454c46@gmail.com, qemu-devel@nongnu.org,
	mhocko@kernel.org, dgunigun@redhat.com, avagin@gmail.com,
	pavel@ucw.cz, ptikhomirov@virtuozzo.com,
	linux-s390@vger.kernel.org, corbet@lwn.net, mpe@ellerman.id.au,
	rafael@kernel.org, ebiggers@kernel.org, borntraeger@de.ibm.com,
	sblbir@amazon.com, bonzini@gnu.org, arnd@arndb.de,
	jannh@google.com, raduweis@amazon.com, asmehra@redhat.com,
	graf@amazon.com, rppt@kernel.org, luto@kernel.org, gil@azul.com,
	oridgar@gmail.com, colmmacc@amazon.com, tytso@mit.edu,
	gregkh@linuxfoundation.org, rdunlap@infradead.org,
	linux-kernel@vger.kernel.org, ebiederm@xmission.com,
	ovzxemul@gmail.com, w@1wt.eu, dwmw@amazon.co.uk
Subject: Re: [PATCH v5 2/2] drivers/virt: vmgenid: add vm generation id driver
Date: Tue, 9 Feb 2021 09:55:32 -0500	[thread overview]
Message-ID: <20210209095350-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1612200294-17561-3-git-send-email-acatan@amazon.com>

> +The ``vmgenid`` driver uses ACPI events to be notified by hardware
> +changes to the 128-bit Vm Gen Id UUID.

That's ok, problem is ACPI event processing is asynchronous.
What we need is thus to flush out ACPI events whenever userspace
does a read, otherwise the value it gets will be stale.

-- 
MST



  reply	other threads:[~2021-02-09 14:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 17:24 [PATCH v5 0/2] System Generation ID driver and VMGENID backend Adrian Catangiu
2021-02-01 17:24 ` acatan--- via
2021-02-01 17:24 ` Adrian Catangiu
2021-02-01 17:24 ` [PATCH v5 1/2] drivers/misc: sysgenid: add system generation id driver Adrian Catangiu
2021-02-01 17:24   ` acatan--- via
2021-02-01 17:24   ` Adrian Catangiu
2021-02-02 12:04   ` Greg KH
2021-02-02 12:04     ` Greg KH
2021-02-02 12:05   ` Greg KH
2021-02-02 12:05     ` Greg KH
2021-02-09 14:44     ` Catangiu, Adrian Costin
2021-02-02 12:08   ` Greg KH
2021-02-02 12:08     ` Greg KH
2021-02-09 14:46     ` Catangiu, Adrian Costin
2021-02-02 22:58   ` Randy Dunlap
2021-02-02 22:58     ` Randy Dunlap
2021-02-09 14:52   ` Michael S. Tsirkin
2021-02-09 14:52     ` Michael S. Tsirkin
2021-02-09 16:44     ` Catangiu, Adrian Costin
2021-02-01 17:24 ` [PATCH v5 2/2] drivers/virt: vmgenid: add vm " Adrian Catangiu
2021-02-01 17:24   ` acatan--- via
2021-02-01 17:24   ` Adrian Catangiu
2021-02-09 14:55   ` Michael S. Tsirkin [this message]
2021-02-09 14:55     ` Michael S. Tsirkin

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=20210209095350-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=0x7f454c46@gmail.com \
    --cc=Jason@zx2c4.com \
    --cc=acatan@amazon.com \
    --cc=areber@redhat.com \
    --cc=arnd@arndb.de \
    --cc=asmehra@redhat.com \
    --cc=avagin@gmail.com \
    --cc=bonzini@gnu.org \
    --cc=borntraeger@de.ibm.com \
    --cc=colmmacc@amazon.com \
    --cc=corbet@lwn.net \
    --cc=dgunigun@redhat.com \
    --cc=dwmw@amazon.co.uk \
    --cc=ebiederm@xmission.com \
    --cc=ebiggers@kernel.org \
    --cc=ghammer@redhat.com \
    --cc=gil@azul.com \
    --cc=graf@amazon.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jannh@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mhocko@kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=oridgar@gmail.com \
    --cc=ovzxemul@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=ptikhomirov@virtuozzo.com \
    --cc=qemu-devel@nongnu.org \
    --cc=raduweis@amazon.com \
    --cc=rafael@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=rppt@kernel.org \
    --cc=sblbir@amazon.com \
    --cc=tytso@mit.edu \
    --cc=vijaysun@ca.ibm.com \
    --cc=w@1wt.eu \
    /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.