From: Nathan Lynch <nathanl@linux.ibm.com>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: Tyrel Datwyler <tyreld@linux.ibm.com>,
Michal Hocko <mhocko@suse.com>,
linux-kernel@vger.kernel.org, Chun-Yi <jlee@suse.com>,
Lee@kitsune.suse.cz, Laurent Dufour <ldufour@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/pseries: add lparctl driver for platform-specific functions
Date: Thu, 15 Sep 2022 08:43:20 -0500 [thread overview]
Message-ID: <87leqku51j.fsf@linux.ibm.com> (raw)
In-Reply-To: <20220914081419.GE28810@kitsune.suse.cz>
Michal Suchánek <msuchanek@suse.de> writes:
> On Tue, Sep 13, 2022 at 12:02:42PM -0500, Nathan Lynch wrote:
>> Anyway, of course I intend to support the more complex calls, but
>> supporting the simple calls actually unbreaks a lot of stuff.
>
> The thing is that supporting calls that return more than one page of
> data is absolutely required, and this interface built around fixed size
> data transfer can't do it.
Again, it is appropriate for the system parameter commands and handlers
to deal in small fixed size buffers. Code for VPD retrieval will have to
work differently.
> So it sounds like a ticked for redoing the driver right after it's
> implemented, or ending up with two subtly different interfaces - one for
> the calls that can return multiple pages of data, and one for the simple
> calls.
>
> That does not sound like a good idea at all to me.
That's not my plan, and I won't be trying to get anything merged without
supporting some of the more complex cases. OK?
prev parent reply other threads:[~2022-09-15 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 0:04 [PATCH] powerpc/pseries: add lparctl driver for platform-specific functions Nathan Lynch
2022-08-01 16:40 ` Laurent Dufour
2022-08-12 19:14 ` Nathan Lynch
2022-09-13 9:13 ` Michal Suchánek
2022-09-13 15:59 ` Nathan Lynch
2022-09-13 16:33 ` Michal Suchánek
2022-09-13 17:02 ` Nathan Lynch
2022-09-14 8:14 ` Michal Suchánek
2022-09-15 13:43 ` Nathan Lynch [this message]
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=87leqku51j.fsf@linux.ibm.com \
--to=nathanl@linux.ibm.com \
--cc=Lee@kitsune.suse.cz \
--cc=jlee@suse.com \
--cc=ldufour@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhocko@suse.com \
--cc=msuchanek@suse.de \
--cc=tyreld@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).