mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Stahl, Manuel" <manuel.stahl@iis-extern.fraunhofer.de>
To: "dan.carpenter@oracle.com" <dan.carpenter@oracle.com>
Cc: "hjk@linutronix.de" <hjk@linutronix.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"sojkam1@fel.cvut.cz" <sojkam1@fel.cvut.cz>
Subject: Re: [PATCH] Add new uio device for PCI with dynamic memory allocation
Date: Wed, 4 Oct 2017 09:39:18 +0000	[thread overview]
Message-ID: <1507109956.2603.5.camel@iis-extern.fraunhofer.de> (raw)
In-Reply-To: <20171004075923.nl454dbxmvqivqy7@mwanda>

On Mi, 2017-10-04 at 10:59 +0300, Dan Carpenter wrote:
> On Wed, Oct 04, 2017 at 07:24:49AM +0000, Stahl, Manuel wrote:
> > Hi Dan. Thanks for your comments. I can fix all of those.
> > Probably there is also some upgrade needed for the MSI stuff.
> > pci_disable_msi() is not there anymore, so I have to use
> > pci_alloc_irq_vectors(). Doing tests with my PCIe HW I had some
> > problems with masking the legacy IRQs. Probably uio_pci_generic
> > suffers from the same problems.
> > 
> > Can someone tell me how to properly handle legacy and MSI
> > interrupts in irqhandler()? Or should I implement a irqcontrol()
> > function?
> > 
> 
> These questions about above my pay grade.  I've never used the code, I
> just do mechanical reviews.  I'm not certain who to ask either...
> 

Alright. I checked again your comments. Some are copy&paste from the
other drivers, but I can improve this. Some cannot be changed:

1) continue instead of break:
Actually size=0 makes no sense for the maps, so open() and release()
take this as abort condition (see also uio_dmem_genirq.c). The parser
continues in that case, but we could break there as well.

2) char * const buf = kstrdup(uio_dmem_sizes, GFP_KERNEL);
Since buf is a const pointer, it has to be set during declaration.
Also I'd like to keep it const.

I will post another patch set without MSI (just the same functionality
as in uio_pci_generic) and then try to add MSI(X) support to both.

Regards,
Manuel

  reply	other threads:[~2017-10-04  9:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-02 15:02 Stahl, Manuel
2017-10-03  9:48 ` Dan Carpenter
2017-10-04  7:24   ` Stahl, Manuel
2017-10-04  7:59     ` Dan Carpenter
2017-10-04  9:39       ` Stahl, Manuel [this message]
2017-10-04  9:51         ` [PATCH v2] " Stahl, Manuel
2017-10-04 10:40         ` [PATCH] " Dan Carpenter

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=1507109956.2603.5.camel@iis-extern.fraunhofer.de \
    --to=manuel.stahl@iis-extern.fraunhofer.de \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hjk@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sojkam1@fel.cvut.cz \
    /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®