From: "David E. Box" <david.e.box@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
mgross@linux.intel.com, rjw@rjwysocki.net,
srinivas.pandruvada@intel.com
Cc: linux-kernel@vger.kernel.org, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 1/3] platform/x86/intel: pmt: Remove bin_attribute mmap support to runtime pm
Date: Mon, 21 Feb 2022 09:06:57 -0800 [thread overview]
Message-ID: <8cb2722299ecf8b4c6d24ff28a0a19024dcb41f0.camel@linux.intel.com> (raw)
In-Reply-To: <5ba6e52c-d7e9-39fc-cb84-963a403385ca@redhat.com>
On Mon, 2022-02-21 at 10:05 +0100, Hans de Goede wrote:
> Hi,
>
> On 2/14/22 22:32, David E. Box wrote:
> > PMT devices need to support runtime D3. However, binary attributes
> > don't
> > provide access to open/release methods that could be used to
> > control
> > runtime pm. Therefore, remove the mmap operation. The data may
> > still be
> > accessed with read() calls.
> >
> > Signed-off-by: David E. Box <david.e.box@linux.intel.com>
> > ---
> > V0 comments:
> >
> > I expect that this is an undesirable solution because of the ABI
> > change.
> > I don't know if anyone is using this ABI outside of our Intel tools
> > which
> > are willing to make this change. I'd rather find a solution to keep
> > the
> > mmap support. I initially wrote a patch to simply add the missing
> > open and
> > release callbacks to binary attributes but this was thought to be
> > too heavy
> > handed in our internal review. I'm open to suggestions. Thanks.
>
> We really cannot go and break userspace API like this. Even if you
> are
> dropping mmap support from the Intel tools; and we assume that the
> Intel
> tools are the only consumer, then we still cannot drop mmap support
> because users may install a new kernel without updating the tools.
>
> The never break userspace rule applies here and that is a very clear
> and hard rule.
>
> So please respin the series using the approach with open and release
> callbacks.
Thanks Hans. I'll send out that series for comment.
David
next prev parent reply other threads:[~2022-02-21 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 21:32 [PATCH 0/3] Add pm_runtime and DG2 support David E. Box
2022-02-14 21:32 ` [PATCH 1/3] platform/x86/intel: pmt: Remove bin_attribute mmap support to runtime pm David E. Box
2022-02-21 9:05 ` Hans de Goede
2022-02-21 17:06 ` David E. Box [this message]
2022-02-14 21:32 ` [PATCH 2/3] platform/x86/intel: vsec: Enable runtime D3 David E. Box
2022-02-14 21:32 ` [PATCH 3/3] platform/x86/intel: vsec: Add DG2 support David E. Box
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=8cb2722299ecf8b4c6d24ff28a0a19024dcb41f0.camel@linux.intel.com \
--to=david.e.box@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@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
all inboxes | Powered by JetHome®