From: jerin.jacob@caviumnetworks.com (Jerin Jacob)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm64: pci: add support for pci_mmap_page_range
Date: Mon, 18 Apr 2016 20:23:49 +0530 [thread overview]
Message-ID: <20160418145348.GA2342@localhost.localdomain> (raw)
In-Reply-To: <10832709.SG7ma9Lsjb@wuerfel>
On Mon, Apr 18, 2016 at 04:15:28PM +0200, Arnd Bergmann wrote:
> On Monday 18 April 2016 19:31:20 Jerin Jacob wrote:
> > Regarding existing user space applications,
> > AFAIK, DPDK has the feature to support both /sysfs and vifo scheme.
> > X11 uses only /sysfs scheme.
> >
> > IMO, Nothing wrong in providing this feature in arm64 kernel.
> > Except arm64, almost all the major architecture has this support.
>
> My understanding was that it's considered deprecated and only
> supported for backwards compatibility, but now I can't find any
> indication of that in the source code and I don't know if that
> is actually the case.
>
> I agree with Will that we should not expose the procfs interface,
> it's just far too ugly.
Me too agree with Will and I don't like it either.
My point was, Irrespective of this change, the /proc/bus/pci/*/* entries
will be created. i.e disabling /proc/bus/pci should be a seprate patch
and it does not depend on this patch.
>
> Arnd
next prev parent reply other threads:[~2016-04-18 14:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 21:10 [PATCH v2] arm64: pci: add support for pci_mmap_page_range Jerin Jacob
2016-04-15 13:09 ` Will Deacon
2016-04-15 18:45 ` Arnd Bergmann
2016-04-18 14:01 ` Jerin Jacob
2016-04-18 14:15 ` Arnd Bergmann
2016-04-18 14:53 ` Jerin Jacob [this message]
2016-04-18 15:00 ` Arnd Bergmann
2016-04-18 15:21 ` Jerin Jacob
2016-04-18 15:31 ` Arnd Bergmann
2016-04-18 15:40 ` Will Deacon
2016-04-18 17:45 ` Jerin Jacob
2016-04-18 17:46 ` Arnd Bergmann
2017-03-15 21:01 ` David Woodhouse
2017-03-20 13:18 ` Will Deacon
2017-03-20 14:07 ` David Woodhouse
2016-04-18 13:43 ` Jerin Jacob
2017-03-16 12:17 ` David Woodhouse
2017-03-20 13:21 ` Will Deacon
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=20160418145348.GA2342@localhost.localdomain \
--to=jerin.jacob@caviumnetworks.com \
--cc=linux-arm-kernel@lists.infradead.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).