From: <dan.j.williams@intel.com>
To: Dave Hansen <dave.hansen@intel.com>, <dan.j.williams@intel.com>,
"Lange, Jon" <jlange@microsoft.com>
Cc: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>, <john.starks@microsoft.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
"Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: "Paravisor" Feature Enumeration
Date: Mon, 5 Jan 2026 19:24:27 -0800 [thread overview]
Message-ID: <695c806beb4d7_4b7a10080@dwillia2-mobl4.notmuch> (raw)
In-Reply-To: <71f42b9e-793b-4f8d-8159-a6ca7800f292@intel.com>
Dave Hansen wrote:
> On 1/5/26 16:01, dan.j.williams@intel.com wrote:
> > Dave Hansen wrote:
> ...
> >> X86_FEATURE_KVM_CLOCKSOURCE in arm,pvclock
> >> or
> >> X86_FEATURE_KVM_STEAL_TIME in arm,kvm-steal-time
> >>
> >> As far as I can tell, these aliases are all done ad-hoc. This approach
> >> could obviously be extended to paravisor features, but it would probably
> >> be on the slow side to do it for each new feature.
> >
> > "Slow" as in standardization time?
>
> Yes.
That speed problem is mitigated by the EFI/ACPI Code First process.
Linux and any other impacted implementation that want to be party to a
new mechanism just come to a public agreement on the mailing lists per
usual and ACPI Working Group acks/naks that public proposal. That
effectively gets you in the same ballpark of time as landing a new
invented Linux enumeration upstream.
There is a lag between the ack and the spec release, but the intention
is the ack means it is safe to assume a future version of the
specification will adopt the change.
next prev parent reply other threads:[~2026-01-06 3:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 21:42 Dave Hansen
2026-01-06 0:01 ` dan.j.williams
2026-01-06 0:10 ` [EXTERNAL] " Jon Lange
2026-01-06 0:46 ` Dave Hansen
2026-01-06 0:36 ` Dave Hansen
2026-01-06 1:08 ` Sean Christopherson
2026-01-06 3:24 ` dan.j.williams [this message]
2026-01-06 1:44 ` Andrew Cooper
2026-01-06 2:12 ` [EXTERNAL] " Jon Lange
2026-01-06 22:39 ` Andrew Cooper
2026-01-06 23:01 ` Jon Lange
2026-01-07 1:58 ` dan.j.williams
2026-01-07 2:48 ` Jon Lange
2026-01-07 18:42 ` dan.j.williams
2026-01-08 6:53 ` Jon Lange
2026-01-07 12:06 ` Kiryl Shutsemau
2026-01-06 19:17 ` Edgecombe, Rick P
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=695c806beb4d7_4b7a10080@dwillia2-mobl4.notmuch \
--to=dan.j.williams@intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=dave.hansen@intel.com \
--cc=jlange@microsoft.com \
--cc=john.starks@microsoft.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=will@kernel.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
all inboxes | Powered by JetHome®