Re: [XENBUS PATCH v4 07/11] xenfilt: Add Xenbus device precedence mechanism

[Owen Smith <owen.smith@xxxxxxxxx>]

I think the separation here would be helpful - keeping the precedence values separate from the parent-id to emulated type mappings could help.

Owen

On Tue, Aug 12, 2025 at 5:14 PM Tu Dinh <ngoc-tu.dinh@xxxxxxxxxx> wrote:

On 08/08/2025 16:03, Tu Dinh wrote:
> Define registry values in xenfilt\Parameters with the names being
> compatible IDs and values being numeric precedences.
>
> The Xenbus device with the highest precedence should always be activated
> over devices with lower precedence, ignoring Active* values.
>
> If a device is force-activated, get its IDs directly instead of via
> Active* values.
>
> Define XENBUS_EMULATED_ACTIVATION_STATUS in emulated_interface.h for
> latter use.
>
> Signed-off-by: Tu Dinh <ngoc-tu.dinh@xxxxxxxxxx>
> ---

I wonder if it's better to move the precedence values to a dedicated key
under Parameters, e.g. xenfilt\Parameters\Precedence.


Ngoc Tu Dinh | Vates XCP-ng Developer

XCP-ng & Xen Orchestra - Vates solutions

web: https://vates.tech