From: Alan Tull <atull@kernel.org>
To: federico.vaga@cern.ch
Cc: Moritz Fischer <mdf@kernel.org>,
linux-fpga@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: fpga: fpga_mgr_get() buggy ?
Date: Tue, 26 Jun 2018 16:00:46 -0500 [thread overview]
Message-ID: <CANk1AXRFK8CYn_c7ckpJeXpFbc-CcZ+xzZiJzUsiDUUS7ancPA@mail.gmail.com> (raw)
In-Reply-To: <22840601.TEhG8FuRZq@pcbe13614>
On Fri, Jun 22, 2018 at 2:53 AM, Federico Vaga <federico.vaga@cern.ch> wrote:
Hi Federico,
>> > What is buggy is the function fpga_mgr_get().
>> > That patch has been done to allow multiple FPGA manager instances
>> > to be linked to the same device (PCI it says). But function
>> > fpga_mgr_get() will return only the first found: what about the
>> > others?
I've had more time with this, I agree with you. I didn't intend to
limit us to one manager per parent device.
>> > Then, all load kernel-doc comments says:
>> >
>> > "This code assumes the caller got the mgr pointer from
>> > of_fpga_mgr_get() or fpga_mgr_get()"
>> >
>> > but that function does not allow me to get, for instance, the
>> > second FPGA manager on my card.
>> >
>> > Since, thanks to this patch I'm actually the creator of the
>> > fpga_manager structure, I do not need to use fpga_mgr_get() to
>> > retrieve that data structure.
>> > Despite this, I believe we still need to increment the module
>> > reference counter (which is done by fpga_mgr_get()).
>> >
>> > We can fix this function by just replacing the argument from
>> > 'device' to 'fpga_manager' (the one returned by create() ).
>>
>> At first thought, that's what I'd want.
>>
>> > Alternatively, we
>> > can add an 'owner' field in "struct fpga_manager_ops" and 'get' it
>> > when we use it. Or again, just an 'owner' argument in the create()
>> > function.
>>
>> It seems like we shouldn't have to do that.
>
> Why?
OK yes, I agree; the kernel has a lot of examples of doing this.
I'll have to play with it, I'll probably add the owner arg to the
create function, add owner to struct fpga_manager, and save.
>
>> > I'm proposing these alternatives because I'm not sure that
>> >
>> > this is correct:
>> > if (!try_module_get(dev->parent->driver->owner))
>> >
>> > What if the device does not have a driver? Do we consider the
>> > following a valid use case?
>> >
>> >
>> > probe(struct device *dev) {
>> >
>> > struct device *mydev;
>> >
>> > mydev->parent = dev;
>> > device_register(mydev);
>> > fpga_mrg_create(mydev, ....);
>> >
>> > }
Sure
>>
>> When would you want to do that?
>
> Not sure when, I'm in the middle of some other development and I
> stumbled into this issue. But of course I can do it ... at some point
> :)
I was meaning to ask something else. I don't mind writing this and
would be interested in your review/feedback. Thanks again for seeing
this and for the thoughtful analysis.
Alan
next prev parent reply other threads:[~2018-06-26 21:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 13:13 fpga: fpga_mgr_get() buggy ? Federico Vaga
2018-06-22 2:07 ` Alan Tull
2018-06-22 7:53 ` Federico Vaga
2018-06-26 21:00 ` Alan Tull [this message]
2018-06-27 9:25 ` Federico Vaga
2018-06-27 21:23 ` Alan Tull
2018-06-28 7:50 ` Federico Vaga
2018-07-18 19:47 ` Alan Tull
2018-07-18 21:47 ` Federico Vaga
2018-08-15 21:02 ` Alan Tull
2018-08-16 7:18 ` Federico Vaga
2018-08-16 18:20 ` Alan Tull
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=CANk1AXRFK8CYn_c7ckpJeXpFbc-CcZ+xzZiJzUsiDUUS7ancPA@mail.gmail.com \
--to=atull@kernel.org \
--cc=federico.vaga@cern.ch \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.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 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).