From: "Piotr Piórkowski" <piotr.piorkowski@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 02/10] drm/xe: Define Virtual Function Identifier
Date: Fri, 29 Dec 2023 22:07:16 +0100 [thread overview]
Message-ID: <20231229210716.f7h2f5gptzfudxxc@intel.com> (raw)
In-Reply-To: <20231227235838.212-3-michal.wajdeczko@intel.com>
Michal Wajdeczko <michal.wajdeczko@intel.com> wrote on czw [2023-gru-28 00:58:30 +0100]:
> According to the PCI Express specification, the SR-IOV Virtual
> Functions (VFs) are numbered starting with 1 (VF1, VF2, ...).
> Additionally, both driver and GuC will refer to Physical Function
> (PF) as VF0. Define helper macro to represent VFn and PF.
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---
> drivers/gpu/drm/xe/xe_sriov_types.h | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_sriov_types.h b/drivers/gpu/drm/xe/xe_sriov_types.h
> index 999a4311b98b..fbeebdb12166 100644
> --- a/drivers/gpu/drm/xe/xe_sriov_types.h
> +++ b/drivers/gpu/drm/xe/xe_sriov_types.h
> @@ -8,6 +8,18 @@
>
> #include <linux/build_bug.h>
>
> +/**
> + * VFID - Virtual Function Identifier
> + * @n: VF number
> + *
> + * Helper macro to represent Virtual Function (VF) Indentifier.
typo
> + * VFID(0) is used as alias to the PFID that represents Physical Function.
> + *
> + * Note: According to PCI spec, SR-IOV VF's numbers are 1-based (VF1, VF2, ...).
> + */
> +#define VFID(n) (n)
> +#define PFID VFID(0)
> +
> /**
> * enum xe_sriov_mode - SR-IOV mode
> * @XE_SRIOV_MODE_NONE: bare-metal mode (non-virtualized)
One typo to fix:
Reviewed-by: Piotr Piórkowski <piotr.piorkowski@intel.com>
> --
> 2.25.1
>
--
next prev parent reply other threads:[~2023-12-29 21:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 23:58 [PATCH 00/10] Introduce Relay Communication for SR-IOV Michal Wajdeczko
2023-12-27 23:58 ` [PATCH 01/10] drm/xe: Allocate dedicated workqueue for SR-IOV workers Michal Wajdeczko
2023-12-29 21:06 ` Piotr Piórkowski
2023-12-27 23:58 ` [PATCH 02/10] drm/xe: Define Virtual Function Identifier Michal Wajdeczko
2023-12-29 21:07 ` Piotr Piórkowski [this message]
2023-12-27 23:58 ` [PATCH 03/10] drm/xe: Introduce GT-oriented SR-IOV logging macros Michal Wajdeczko
2023-12-29 21:07 ` Piotr Piórkowski
2023-12-27 23:58 ` [PATCH 04/10] drm/xe/guc: Add helpers for HXG messages Michal Wajdeczko
2023-12-29 21:08 ` Piotr Piórkowski
2023-12-29 22:10 ` Michal Wajdeczko
2023-12-27 23:58 ` [PATCH 05/10] drm/xe/guc: Update few GuC CTB ABI definitions Michal Wajdeczko
2023-12-29 21:09 ` Piotr Piórkowski
2023-12-27 23:58 ` [PATCH 06/10] drm/xe/guc: Add Relay Communication " Michal Wajdeczko
2023-12-29 21:09 ` Piotr Piórkowski
2023-12-27 23:58 ` [PATCH 07/10] drm/xe/guc: Introduce Relay Communication for SR-IOV Michal Wajdeczko
2023-12-29 21:14 ` Piotr Piórkowski
2023-12-29 22:55 ` Michal Wajdeczko
2023-12-27 23:58 ` [PATCH 08/10] drm/xe/kunit: Allow to replace xe_guc_ct_send_recv() with stub Michal Wajdeczko
2023-12-29 21:15 ` Piotr Piórkowski
2023-12-27 23:58 ` [PATCH 09/10] drm/xe/kunit: Add GuC Relay kunit tests Michal Wajdeczko
2023-12-29 21:15 ` Piotr Piórkowski
2023-12-27 23:58 ` [PATCH 10/10] drm/xe/guc: Start handling GuC Relay event messages Michal Wajdeczko
2023-12-29 21:16 ` Piotr Piórkowski
2024-01-04 5:43 ` ✓ CI.Patch_applied: success for Introduce Relay Communication for SR-IOV Patchwork
2024-01-04 5:43 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-04 5:44 ` ✓ CI.KUnit: success " Patchwork
2024-01-04 5:52 ` ✓ CI.Build: " Patchwork
2024-01-04 5:52 ` ✗ CI.Hooks: failure " Patchwork
2024-01-04 5:53 ` ✓ CI.checksparse: success " Patchwork
2024-01-04 6:30 ` ✗ CI.BAT: failure " Patchwork
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=20231229210716.f7h2f5gptzfudxxc@intel.com \
--to=piotr.piorkowski@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.wajdeczko@intel.com \
/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