From: Jan Beulich <jbeulich@suse.com>
To: Jason Andryuk <jason.andryuk@amd.com>,
Daniel Smith <dpsmith@apertussolutions.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 17/24] XSM: make Argo hooks well-formed ones
Date: Wed, 5 Aug 2026 11:11:04 +0200 [thread overview]
Message-ID: <b34dff82-8ead-467d-93b6-4dd655234400@suse.com> (raw)
In-Reply-To: <57bb7281-5898-4243-837a-1236b25e761e@amd.com>
On 04.08.2026 16:27, Jason Andryuk wrote:
> On 2026-08-04 03:53, Jan Beulich wrote:
>> On 03.08.2026 23:01, Jason Andryuk wrote:
>>> On 2026-07-28 09:22, Jan Beulich wrote:
>>>> --- a/xen/include/xsm/dummy.h
>>>> +++ b/xen/include/xsm/dummy.h
>>>
>>>> @@ -751,27 +751,32 @@ static XSM_INLINE int xsm_dm_op(XSM_DEFA
>>>> #endif
>>>>
>>>> #ifdef CONFIG_ARGO
>>>> -static XSM_INLINE int xsm_argo_enable(const struct domain *d)
>>>> +
>>>> +static XSM_INLINE int xsm_argo_enable(XSM_DEFAULT_ARG const struct domain *d)
>>>> {
>>>> - return 0;
>>>> + XSM_ASSERT_ACTION(XSM_HOOK);
>>>> + return xsm_default_action(action, current->domain, d);
>>>
>>> This one I think should be
>>> return xsm_default_action(action, d, NULL);
>>>
>>> Usually current is passed in for the check, but for domain_create() ->
>>> argo_init() it is the under-construction domain.
>>
>> And in that case we want to make sure that current->domain may enable Argo
>> for d.
>
> It's not a hook for current to enable for d, but more of a hook "is d
> allowed to use argo."
>
> In the hypercall entry path, it use is clear - "is this domain allowed
> to make argo hypercalls."
>
> In argo_init(), it is more of an optimization. Only initialize if d is
> allowed to use argo. I think this use is questionable, but it is the
> current code.
>
> In flask, the source is d, the target is xen_t:
> allow domain_type xen_t:argo enable
>
> So it is not an operation between domains.
>
>>>> }
>>>>
>>>> static XSM_INLINE int xsm_argo_register_single_source(
>>>> - const struct domain *d, const struct domain *t)
>>>> + XSM_DEFAULT_ARG const struct domain *d, const struct domain *t)
>>>> {
>>>> - return 0;
>>>> + XSM_ASSERT_ACTION(XSM_HOOK);
>>>> + return xsm_default_action(action, d, t);
>>>> }
>>>>
>>>> static XSM_INLINE int xsm_argo_register_any_source(
>>>> - const struct domain *d)
>>>> + XSM_DEFAULT_ARG const struct domain *d)
>>>> {
>>>> - return 0;
>>>> + XSM_ASSERT_ACTION(XSM_HOOK);
>>>> + return xsm_default_action(action, current->domain, d);
>>>
>>> Similarly:
>>> return xsm_default_action(action, d, NULL);
>>>
>>> The single call is:
>>> xsm_argo_register_any_source(currd);
>>
>> There being just a single call puts this on the edge. If there was another
>> one not passing current->domain, I think the same argument as above would
>> hold here. And the general concept is what I think should matter when
>> writing the dummy implementations.
>
> For flask, we have xen as the target again:
> allow domain_type xen_t:argo register_any_source;
>
> ... since a wildcard ring doesn't have a known target domain.
>
>>> These argo hooks all pass in their arguments explicitly, so I think we
>>> should do that and not use current. (The send and register hooks could
>>> use current, and that could make sense as those map to hypercalls. But
>>> it is correct today with the explicit arguments.)
>>>
>>> With the changes:
>>> Reviewed-by: Jason Andryuk <jason.andryuk@amd.com>
>>
>> Thanks, but no - unless I misunderstand how permissions are intended to
>> work here, I don't think I can make the changes requested, and hence I
>> can't apply the R-b.
> Understandable.
>
> It seems to me that the XSM hooks have two styles. Either implicit args
> (using current) or explicit args. Today, the argo hooks take explicit
> like the grant hooks for instance.
Yes, which doesn't make things any easier. I follow your argumentation as
one of the possible interpretations, but I think I really need Daniel's
verdict (as XSM maintainer) here in order to know whether to adjust the
proposed code. (It is true that what you suggest comes closer to the
blanket "return 0" that were previously there in all the Argo hooks,
leaving aside that due to it being XSM_HOOK all of this is cosmetic / doc
only anyway. There is certainly also the option to retain those, but it
feels that doing it like this was wrong from the start.)
Jan
next prev parent reply other threads:[~2026-08-05 9:11 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 13:10 [PATCH 00/24] XSM: follow-on to XSAs 492 and 499 Jan Beulich
2026-07-28 13:13 ` [PATCH 01/24] XSM: reduce redundancy in hook machinery Jan Beulich
2026-07-30 15:05 ` Daniel P. Smith
2026-07-30 15:18 ` Jan Beulich
2026-07-30 18:21 ` Daniel P. Smith
2026-07-31 8:03 ` Jan Beulich
2026-08-02 14:46 ` Daniel P. Smith
2026-07-28 13:14 ` [PATCH 02/24] XSM: make .grant_*() hooks dependent upon GRANT_TABLE=y Jan Beulich
2026-07-30 18:23 ` Daniel P. Smith
2026-07-28 13:14 ` [PATCH 03/24] XSM: make .{,un}map_domain_pirq() hooks dependent upon HAS_PIRQ=y Jan Beulich
2026-08-02 14:50 ` Daniel P. Smith
2026-07-28 13:14 ` [PATCH 04/24] XSM: make PCI hooks dependent upon HAS_PCI=y Jan Beulich
2026-08-02 14:53 ` Daniel P. Smith
2026-07-28 13:15 ` [PATCH 05/24] XSM: make .iomem_mapping_vcpi() hook dependent upon HAS_VPCI=y Jan Beulich
2026-08-02 14:56 ` Daniel P. Smith
2026-07-28 13:15 ` [PATCH 06/24] XSM: make .kexec() hook dependent upon KEXEC=y Jan Beulich
2026-08-02 14:57 ` Daniel P. Smith
2026-07-28 13:15 ` [PATCH 07/24] XSM: make .hypfs() hook dependent upon HYPFS=y Jan Beulich
2026-08-02 14:58 ` Daniel P. Smith
2026-07-28 13:16 ` [PATCH 08/24] XSM: make .hvm_altp2mhvm_op() hook dependent upon ALTP2M=y Jan Beulich
2026-08-02 14:58 ` Daniel P. Smith
2026-07-28 13:17 ` [PATCH 09/24] XSM: make .hvm_param*() hooks dependent upon HVM=y Jan Beulich
2026-08-02 15:05 ` Daniel P. Smith
2026-08-03 9:55 ` Jan Beulich
2026-08-02 15:05 ` Daniel P. Smith
2026-07-28 13:17 ` [PATCH 10/24] XSM: make .dm_op() hook dependent upon IOREQ_SERVER=y Jan Beulich
2026-08-02 15:07 ` Daniel P. Smith
2026-07-28 13:18 ` [PATCH 11/24] XSM: make certain x86-specific hooks dependent upon PV=y Jan Beulich
2026-08-02 15:08 ` Daniel P. Smith
2026-07-28 13:18 ` [PATCH 12/24] x86/mm: get_page_from_l1e() is PV-or-shadow-only Jan Beulich
2026-08-02 15:55 ` Daniel P. Smith
2026-08-03 10:11 ` Jan Beulich
2026-08-13 11:51 ` Daniel P. Smith
2026-08-13 12:14 ` Jan Beulich
2026-08-13 13:02 ` Daniel P. Smith
2026-07-28 13:19 ` [PATCH 13/24] x86: restrict PHYSDEVOP_* when PV=n Jan Beulich
2026-08-05 22:38 ` Daniel P. Smith
2026-07-28 13:19 ` [PATCH 14/24] XSM/dummy: fold cf_check into XSM_INLINE Jan Beulich
2026-08-05 22:39 ` Daniel P. Smith
2026-07-28 13:20 ` [PATCH 15/24] XSM/dummy: drop redundant return statements Jan Beulich
2026-08-05 22:40 ` Daniel P. Smith
2026-07-28 13:20 ` [PATCH 16/24] XSM: suppress hypercall when XSM=n Jan Beulich
2026-08-05 22:42 ` Daniel P. Smith
2026-07-28 13:22 ` [PATCH 17/24] XSM: make Argo hooks well-formed ones Jan Beulich
2026-08-03 21:01 ` Jason Andryuk
2026-08-04 7:53 ` Jan Beulich
2026-08-04 14:27 ` Jason Andryuk
2026-08-05 9:11 ` Jan Beulich [this message]
2026-08-06 0:37 ` Daniel P. Smith
2026-08-05 23:02 ` Daniel P. Smith
2026-08-06 7:16 ` Jan Beulich
2026-08-06 14:09 ` Jason Andryuk
2026-08-13 12:09 ` Daniel P. Smith
2026-08-15 1:12 ` Jason Andryuk
2026-07-28 13:22 ` [PATCH 18/24] XSM: make XSM " Jan Beulich
2026-08-06 0:53 ` Daniel P. Smith
2026-08-06 7:22 ` Jan Beulich
2026-07-28 13:23 ` [PATCH 19/24] XSM: convert "allow" (Flask: "access") parameters to bool Jan Beulich
2026-08-06 0:56 ` Daniel P. Smith
2026-07-28 13:23 ` [PATCH 20/24] XSM: fold xsm_{,un}map_domain_pirq() hooks Jan Beulich
2026-08-06 1:10 ` Daniel P. Smith
2026-08-06 7:36 ` Jan Beulich
2026-08-06 8:02 ` Jan Beulich
2026-08-13 12:42 ` Daniel P. Smith
2026-08-13 13:02 ` Jan Beulich
2026-08-13 13:05 ` Daniel P. Smith
2026-07-28 13:24 ` [PATCH 21/24] x86: type-correct last parameter of map_domain_pirq() Jan Beulich
2026-07-28 13:25 ` [PATCH 22/24] XSM: pass just SBDF to xsm_{,un}map_domain_irq() Jan Beulich
2026-08-06 1:16 ` Daniel P. Smith
2026-07-28 13:26 ` [PATCH 23/24] XSM: fold xsm_{,un}map_domain_irq() hooks Jan Beulich
2026-08-13 11:27 ` Daniel P. Smith
2026-07-28 13:26 ` [PATCH 24/24] XSM: fold xsm_{,un}bind_pt_irq() hooks Jan Beulich
2026-08-13 11:32 ` Daniel P. Smith
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=b34dff82-8ead-467d-93b6-4dd655234400@suse.com \
--to=jbeulich@suse.com \
--cc=dpsmith@apertussolutions.com \
--cc=jason.andryuk@amd.com \
--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.