All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: <intel-gfx@lists.freedesktop.org>,
	Alexander Usyskin <alexander.usyskin@intel.com>
Subject: Re: [PATCH 1/2] mei: me: Add exported function to check ME device availabiliy
Date: Wed, 16 Jul 2025 09:38:09 -0700	[thread overview]
Message-ID: <5d588a32-fbe5-41c8-8cd5-0d53b1b44637@intel.com> (raw)
In-Reply-To: <2025071622-frequency-sneer-0ad9@gregkh>



On 7/15/2025 10:10 PM, Greg Kroah-Hartman wrote:
> On Tue, Jul 15, 2025 at 04:00:01PM -0700, Daniele Ceraolo Spurio wrote:
>> The intel GFX drivers (i915/xe) interface with the ME device for some of
>> their features (e.g. PXP, HDCP) via the component interface. Given that
>> the MEI device can be hidden by BIOS/Coreboot, the GFX drivers need a
>> way to check if the device is available before attempting to bind the
>> component, otherwise they'll go ahead and initialize features that will
>> never work.
>> The simplest way to check if the device is available is to check the
>> available devices against the PCI ID list of the mei_me driver. To avoid
>> duplication of the list, the function to do such a check is added to
>> the mei_me driver and exported so that the GFX driver can call it
>> directly.
>>
>> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>> Cc: Alexander Usyskin <alexander.usyskin@intel.com>
>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> ---
>>   drivers/misc/mei/pci-me.c | 17 +++++++++++++++++
>>   include/linux/mei_me.h    | 20 ++++++++++++++++++++
>>   2 files changed, 37 insertions(+)
>>   create mode 100644 include/linux/mei_me.h
>>
>> diff --git a/drivers/misc/mei/pci-me.c b/drivers/misc/mei/pci-me.c
>> index 3f9c60b579ae..16e9a11eb286 100644
>> --- a/drivers/misc/mei/pci-me.c
>> +++ b/drivers/misc/mei/pci-me.c
>> @@ -18,6 +18,7 @@
>>   #include <linux/pm_runtime.h>
>>   
>>   #include <linux/mei.h>
>> +#include <linux/mei_me.h>
>>   
>>   #include "mei_dev.h"
>>   #include "client.h"
>> @@ -133,6 +134,22 @@ static const struct pci_device_id mei_me_pci_tbl[] = {
>>   
>>   MODULE_DEVICE_TABLE(pci, mei_me_pci_tbl);
>>   
>> +/**
>> + * mei_me_device_present - check if an ME device is present on the system
>> + *
>> + * Other drivers (e.g., i915, xe) interface with the ME device for some of their
>> + * features (e.g., PXP, HDCP). However, the ME device can be hidden by
>> + * BIOS/coreboot, so this function offers a way for those drivers to check if
>> + * the device is available before attempting to interface with it.
>> + *
>> + * Return: true if an ME device is available, false otherwise
>> + */
>> +bool mei_me_device_present(void)
>> +{
>> +	return pci_dev_present(mei_me_pci_tbl);
> And what happens if the device goes away right after you call this?

Both intel graphics drivers do already handle the device being missing 
or going away, it's just not very clean. Behavior changes based on when 
this happens:

- if the device is never there or disappears before the component binds, 
we timeout waiting for the bind
- if the device disappears after the bind, we handle the case as part of 
the component unbind call

The timeout is quite long and can therefore impact/delay userspace, so 
the aim here is to mitigate that impact in the case where the device is 
just never there, which is easy to check and more likely to happen 
compared to the device going away after initially being there.

Should I add a note about the device going away to the function doc? 
Something like "Callers are still expected to handle the case where the 
device goes away after this check is performed".

>
>> +}
>> +EXPORT_SYMBOL(mei_me_device_present);
> EXPORT_SYMBOL_GPL()?  I have to ask, sorry.

The non-GPL version seemed more appropriate to me because I didn't think 
calling this function qualified as "derivative work", but I don't really 
care either way because both i915 and Xe are part of the kernel and 
GPL-compatible, so I can switch to the GPL version.

>
> And where is patch 2/2?

Sorry, here it is:

https://lore.kernel.org/all/20250715225959.488109-6-daniele.ceraolospurio@intel.com/

It's just i915 bailing early from the PXP init if mei_me_device_present 
is false.

Thanks,
Daniele

>
> thanks,
>
> greg k-h


  reply	other threads:[~2025-07-16 16:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15 23:00 [PATCH 0/2] Check if CSME is available before initializing PXP Daniele Ceraolo Spurio
2025-07-15 23:00 ` [PATCH 1/2] mei: me: Add exported function to check ME device availabiliy Daniele Ceraolo Spurio
2025-07-16  5:10   ` Greg Kroah-Hartman
2025-07-16 16:38     ` Daniele Ceraolo Spurio [this message]
2025-07-16 16:49       ` Greg Kroah-Hartman
2025-07-16 17:57         ` Daniele Ceraolo Spurio
2025-07-30 15:57           ` Daniele Ceraolo Spurio
2025-07-15 23:00 ` [PATCH 2/2] drm/i915/pxp: Do not support PXP if CSME is not available Daniele Ceraolo Spurio
2025-07-16 11:34   ` Valentine Burley
2025-07-15 23:53 ` ✓ i915.CI.BAT: success for Check if CSME is available before initializing PXP Patchwork
2025-07-16 17:45 ` ✗ i915.CI.Full: 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=5d588a32-fbe5-41c8-8cd5-0d53b1b44637@intel.com \
    --to=daniele.ceraolospurio@intel.com \
    --cc=alexander.usyskin@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=intel-gfx@lists.freedesktop.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.