From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: "Matthew Brost" <matthew.brost@intel.com>,
"Michał Winiarski" <michal.winiarski@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 1/6] drm/xe/pf: Add top level functions to control VFs
Date: Wed, 1 Oct 2025 10:03:33 +0200 [thread overview]
Message-ID: <b5ccedeb-5b93-4fb3-8256-090b6954d5d2@intel.com> (raw)
In-Reply-To: <aNzZgNIIAgd6OBzn@lstrano-desk.jf.intel.com>
On 10/1/2025 9:34 AM, Matthew Brost wrote:
> On Wed, Oct 01, 2025 at 01:35:19AM +0200, Michal Wajdeczko wrote:
>> We already have control functions that we use to control the VF
>> state on the per-GT basis, but that is low level detail from the
>> user point of view, who rather expects VF-level functions.
>>
>> For now add simple functions that just iterate over all GTs and
>> call per-GT control function. We will soon allow to use some of
>> them from the user facing interfaces like debugfs.
>>
>
> Will the VFIO driver hook into the level control like xe_sriov_pf_control.c?
>
it should, but likely through a small glue layer that will convert
from pci_dev to xe_device
+ Michal to confirm
next prev parent reply other threads:[~2025-10-01 8:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 23:35 [PATCH 0/6] More PF improvements Michal Wajdeczko
2025-09-30 23:35 ` [PATCH 1/6] drm/xe/pf: Add top level functions to control VFs Michal Wajdeczko
2025-10-01 7:34 ` Matthew Brost
2025-10-01 8:03 ` Michal Wajdeczko [this message]
2025-10-02 21:26 ` Michał Winiarski
2025-09-30 23:35 ` [PATCH 2/6] drm/xe/pf: Log only top level VF state changes Michal Wajdeczko
2025-10-02 21:33 ` Michał Winiarski
2025-09-30 23:35 ` [PATCH 3/6] drm/xe/pf: Expose VF control operations over debugfs Michal Wajdeczko
2025-10-01 7:30 ` Matthew Brost
2025-10-01 8:21 ` Michal Wajdeczko
2025-10-02 21:37 ` Michał Winiarski
2025-09-30 23:35 ` [PATCH 4/6] drm/xe/pf: Unify VF state tracking log Michal Wajdeczko
2025-10-02 21:46 ` Michał Winiarski
2025-09-30 23:35 ` [PATCH 5/6] drm/xe/pf: Split VF FLR processing function Michal Wajdeczko
2025-10-02 21:47 ` Michał Winiarski
2025-09-30 23:35 ` [PATCH 6/6] drm/xe/pf: Synchronize VF FLR between all GTs Michal Wajdeczko
2025-10-01 7:32 ` Matthew Brost
2025-10-01 8:27 ` Michal Wajdeczko
2025-10-02 21:57 ` Michał Winiarski
2025-10-01 0:59 ` ✗ CI.checkpatch: warning for More PF improvements Patchwork
2025-10-01 1:00 ` ✓ CI.KUnit: success " Patchwork
2025-10-01 1:35 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-01 3:56 ` ✓ Xe.CI.Full: " 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=b5ccedeb-5b93-4fb3-8256-090b6954d5d2@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=michal.winiarski@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