All of lore.kernel.org
 help / color / mirror / Atom feed
From: torsten.oehlenschlager@tutanota.de
To: Xen Devel <xen-devel@lists.xenproject.org>
Cc: Andrew Cooper3 <andrew.cooper3@citrix.com>,
	Sstabellini <sstabellini@kernel.org>,
	Jbeulich <jbeulich@suse.com>, Julien <julien@xen.org>
Subject: [PATCH] xen/domain: enable VCPUOP_register_runstate_phys_area hypercall
Date: Fri, 12 Dec 2025 22:01:58 +0100 (CET)	[thread overview]
Message-ID: <OgJMhRT--F-9@tutanota.de> (raw)

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

ice@blossom ..............................................................................................................................................................................…/xen 🌸 enable-runstate-phys-area ?
❯ cat 0001-xen-domain-enable-VCPUOP_register_runstate_phys_area.patch
From 416992b30258d34b7cc7bc4f7875719f47618147 Mon Sep 17 00:00:00 2001
From: melanie <torsten.oehlenschlager@tutanota.de>
Date: Fri, 12 Dec 2025 20:55:50 +0000
Subject: [PATCH] xen/domain: enable VCPUOP_register_runstate_phys_area
hypercall

The XENFEAT_runstate_phys_area feature is unconditionally advertised to
guests via XENVER_get_features ( see xen/common/kernel.c ),  but the
corresponding VCPUOP_register_runstate_phys_area hypercall was disabled
with a placeholder check that always returned -ENOSYS!

Remove the dead code to enable the hypercall,  making the implementation
consistent with the advertised feature.

Signed-off-by: melanie <torsten.oehlenschlager@tutanota.de>
---
xen/common/domain.c | 4 ----
1 file changed, 4 deletions(-)

diff --git a/xen/common/domain.c b/xen/common/domain.c
index 93c71bc766..3ae8d41cf2 100644
--- a/xen/common/domain.c
+++ b/xen/common/domain.c
@@ -2284,10 +2284,6 @@ long common_vcpu_op(int cmd, struct vcpu *v, XEN_GUEST_HANDLE_PARAM(void) arg)
     {
         struct vcpu_register_runstate_memory_area area;

-        rc = -ENOSYS;
-        if ( 0 /* TODO: Dom's XENFEAT_runstate_phys_area setting */ )
-            break;
-
         rc = -EFAULT;
         if ( copy_from_guest(&area.addr.p, arg, 1) )
             break;
--

-- 

[-- Attachment #2: Type: text/html, Size: 3234 bytes --]

             reply	other threads:[~2025-12-12 21:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-12 21:01 torsten.oehlenschlager [this message]
2025-12-15 16:55 ` [PATCH] xen/domain: enable VCPUOP_register_runstate_phys_area hypercall Jan Beulich

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=OgJMhRT--F-9@tutanota.de \
    --to=torsten.oehlenschlager@tutanota.de \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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 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.