[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v5] xen: introduce CONFIG_HAS_SHARED_INFO for archs without a shared page
- To: Oleksii Kurochko <oleksii.kurochko@xxxxxxxxx>
- From: Jan Beulich <jbeulich@xxxxxxxx>
- Date: Fri, 10 Jul 2026 15:50:02 +0200
- Authentication-results: eu.smtp.expurgate.cloud; dkim=pass header.s=google header.d=suse.com header.i="@suse.com" header.h="Content-Transfer-Encoding:Content-Type:In-Reply-To:Autocrypt:From:Content-Language:References:Cc:To:Subject:User-Agent:MIME-Version:Date:Message-ID"
- Autocrypt: addr=jbeulich@xxxxxxxx; keydata= xsDiBFk3nEQRBADAEaSw6zC/EJkiwGPXbWtPxl2xCdSoeepS07jW8UgcHNurfHvUzogEq5xk hu507c3BarVjyWCJOylMNR98Yd8VqD9UfmX0Hb8/BrA+Hl6/DB/eqGptrf4BSRwcZQM32aZK 7Pj2XbGWIUrZrd70x1eAP9QE3P79Y2oLrsCgbZJfEwCgvz9JjGmQqQkRiTVzlZVCJYcyGGsD /0tbFCzD2h20ahe8rC1gbb3K3qk+LpBtvjBu1RY9drYk0NymiGbJWZgab6t1jM7sk2vuf0Py O9Hf9XBmK0uE9IgMaiCpc32XV9oASz6UJebwkX+zF2jG5I1BfnO9g7KlotcA/v5ClMjgo6Gl MDY4HxoSRu3i1cqqSDtVlt+AOVBJBACrZcnHAUSuCXBPy0jOlBhxPqRWv6ND4c9PH1xjQ3NP nxJuMBS8rnNg22uyfAgmBKNLpLgAGVRMZGaGoJObGf72s6TeIqKJo/LtggAS9qAUiuKVnygo 3wjfkS9A3DRO+SpU7JqWdsveeIQyeyEJ/8PTowmSQLakF+3fote9ybzd880fSmFuIEJldWxp Y2ggPGpiZXVsaWNoQHN1c2UuY29tPsJgBBMRAgAgBQJZN5xEAhsDBgsJCAcDAgQVAggDBBYC AwECHgECF4AACgkQoDSui/t3IH4J+wCfQ5jHdEjCRHj23O/5ttg9r9OIruwAn3103WUITZee e7Sbg12UgcQ5lv7SzsFNBFk3nEQQCACCuTjCjFOUdi5Nm244F+78kLghRcin/awv+IrTcIWF hUpSs1Y91iQQ7KItirz5uwCPlwejSJDQJLIS+QtJHaXDXeV6NI0Uef1hP20+y8qydDiVkv6l IreXjTb7DvksRgJNvCkWtYnlS3mYvQ9NzS9PhyALWbXnH6sIJd2O9lKS1Mrfq+y0IXCP10eS FFGg+Av3IQeFatkJAyju0PPthyTqxSI4lZYuJVPknzgaeuJv/2NccrPvmeDg6Coe7ZIeQ8Yj t0ARxu2xytAkkLCel1Lz1WLmwLstV30g80nkgZf/wr+/BXJW/oIvRlonUkxv+IbBM3dX2OV8 AmRv1ySWPTP7AAMFB/9PQK/VtlNUJvg8GXj9ootzrteGfVZVVT4XBJkfwBcpC/XcPzldjv+3 HYudvpdNK3lLujXeA5fLOH+Z/G9WBc5pFVSMocI71I8bT8lIAzreg0WvkWg5V2WZsUMlnDL9 mpwIGFhlbM3gfDMs7MPMu8YQRFVdUvtSpaAs8OFfGQ0ia3LGZcjA6Ik2+xcqscEJzNH+qh8V m5jjp28yZgaqTaRbg3M/+MTbMpicpZuqF4rnB0AQD12/3BNWDR6bmh+EkYSMcEIpQmBM51qM EKYTQGybRCjpnKHGOxG0rfFY1085mBDZCH5Kx0cl0HVJuQKC+dV2ZY5AqjcKwAxpE75MLFkr wkkEGBECAAkFAlk3nEQCGwwACgkQoDSui/t3IH7nnwCfcJWUDUFKdCsBH/E5d+0ZnMQi+G0A nAuWpQkjM1ASeQwSHEeAWPgskBQL
- Cc: Romain Caritey <Romain.Caritey@xxxxxxxxxxxxx>, Baptiste Le Duc <baptiste.le-duc@xxxxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Julien Grall <julien@xxxxxxx>, Bertrand Marquis <bertrand.marquis@xxxxxxx>, Michal Orzel <michal.orzel@xxxxxxx>, Volodymyr Babchuk <Volodymyr_Babchuk@xxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Anthony PERARD <anthony.perard@xxxxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, Teddy Astie <teddy.astie@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
- Delivery-date: Fri, 10 Jul 2026 13:50:14 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On 10.07.2026 15:31, Oleksii Kurochko wrote:
> On 7/8/26 12:52 PM, Jan Beulich wrote:
>>> +#ifndef CONFIG_HAS_SHARED_INFO
>>> +/*
>>> + * Placeholder ops for domains with neither a shared_info page nor (yet)
>>> + * a FIFO control block. None of these are ever reachable in practice;
>>> + * they only exist to keep d->evtchn_port_ops non-NULL.
>>> + */
>>> +static void cf_check evtchn_none_set_pending(
>>> + struct vcpu *v, struct evtchn *evtchn) {}
>>> +static void cf_check evtchn_none_noop(
>>> + struct domain *d, struct evtchn *evtchn) {}
>>> +static bool cf_check evtchn_none_false(
>>> + const struct domain *d, const struct evtchn *evtchn) { return false; }
>>> +static void cf_check evtchn_none_print_state(
>>> + struct domain *d, const struct evtchn *evtchn) {}
>>> +
>>> +static const struct evtchn_port_ops evtchn_port_ops_none = {
>>> + .set_pending = evtchn_none_set_pending,
>>> + .clear_pending = evtchn_none_noop,
>>> + .unmask = evtchn_none_noop,
>>> + .is_pending = evtchn_none_false,
>>> + .is_masked = evtchn_none_false,
>>> + .print_state = evtchn_none_print_state,
>>> +};
>>> +
>>> +void evtchn_none_init(struct domain *d)
>>> +{
>>> + d->evtchn_port_ops = &evtchn_port_ops_none;
>>> +}
>>> +#endif /* !CONFIG_HAS_SHARED_INFO */
>> ... we wondering whether any of this is needed when FIFO is available. In
>> v4 all that was noticed was that SHARED_INFO=n together with EVTCHN_FIFO=n
>> is a problem. And having fewer cf_check functions in the build is always a
>> win (I think).
>
> I thought an opposite that it is good to have cf_check when pointer to
> function is used. So why we have to make an exception in this case?
I didn't ask to drop the cf_check (and you can't really as long as these
functions may be used by x86). I asked to limit the number of them we have
(in a particular configuration) as much as possible. I.e. I was merely
trying to explain why it is relevant to have the #if around this as tight
as possible.
Jan
|