public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Santosh Shukla <santosh.shukla@linaro.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	josh@joshtriplett.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	akpm@linux-foundation.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-api@vger.kernel.org, yuanhan.liu@linux.intel.com
Subject: Re: [PATCH] drivers/char/mem.c: Add /dev/ioports, supporting 16-bit and 32-bit ports
Date: Tue, 29 Dec 2015 14:28:01 +0100	[thread overview]
Message-ID: <5873998.uv0CPtuiff@wuerfel> (raw)
In-Reply-To: <CA+iXiiOsbC0MBaRwc5JgaTVRpdxHub5t2T=LrGaVN1AjKpiJgA@mail.gmail.com>

On Wednesday 23 December 2015 17:04:40 Santosh Shukla wrote:
> On 23 December 2015 at 03:26, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Tuesday 22 December 2015, Santosh Shukla wrote:
> >> }
> >>
> >> So I care for /dev/ioport types interface who could do more than byte
> >> data copy to/from user-space. I tested this patch with little
> >> modification and could able to run pmd driver for arm/arm64 case.
> >>
> >> Like to know how to address pci_io region mapping problem for
> >> arm/arm64, in-case /dev/ioports approach is not acceptable or else I
> >> can spent time on restructuring the patch?
> >>
> >
> > For the use case you describe, can't you use the vfio framework to
> > access the PCI BARs?
> >
> 
> I looked at file: drivers/vfio/pci/vfio_pci.c, func vfio_pci_map() and
> it look to me that it only maps ioresource_mem pci region, pasting
> code snap:
> 
> if (!(pci_resource_flags(pdev, index) & IORESOURCE_MEM))
> return -EINVAL;
> ....
> 
> and I want to map ioresource_io pci region for arm platform in my
> use-case. Not sure vfio maps pci_iobar region?

Mapping I/O BARs is not portable, notably it doesn't work on x86.

You should be able access them using the read/write interface on
the vfio device.

	Arnd

  reply	other threads:[~2015-12-29 13:29 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 19:19 [PATCH] drivers/char/mem.c: Add /dev/ioports, supporting 16-bit and 32-bit ports Josh Triplett
2014-05-09 19:21 ` [PATCH] mem.4, ioports.4: Document /dev/ioports Josh Triplett
2014-05-13  8:27   ` Michael Kerrisk (man-pages)
2014-05-09 19:58 ` [PATCH] drivers/char/mem.c: Add /dev/ioports, supporting 16-bit and 32-bit ports Arnd Bergmann
2014-05-09 20:54   ` H. Peter Anvin
2014-05-09 21:12     ` Arnd Bergmann
2014-05-09 21:20       ` H. Peter Anvin
2014-05-09 22:38         ` Josh Triplett
2014-05-13 22:10           ` H. Peter Anvin
2014-05-15 21:56             ` josh
2014-05-19 12:36               ` Arnd Bergmann
2014-05-28 21:41                 ` H. Peter Anvin
2014-05-29  9:26                   ` Arnd Bergmann
2014-05-29 13:38                     ` H. Peter Anvin
2014-05-30 11:32                       ` Arnd Bergmann
2015-12-22 10:52                         ` Santosh Shukla
2015-12-22 21:56                           ` Arnd Bergmann
2015-12-22 22:02                             ` H. Peter Anvin
2015-12-22 22:11                               ` Arnd Bergmann
2015-12-23 11:34                             ` Santosh Shukla
2015-12-29 13:28                               ` Arnd Bergmann [this message]
2015-12-29 15:53                                 ` Santosh Shukla
2015-12-29 15:55                                   ` Santosh Shukla
2015-12-29 16:20                                     ` Arnd Bergmann
2015-12-29 16:30                                       ` Santosh Shukla
2015-12-29 17:31                                         ` Alex Williamson
2015-12-31  9:33                                           ` Santosh Shukla
2015-12-31 15:41                                             ` Alex Williamson
2016-01-07  9:31                                               ` Santosh Shukla
2014-05-10  7:07 ` Jann Horn
2014-05-10 19:32   ` Josh Triplett
2014-05-11 12:50     ` Jann Horn
2014-05-11 21:05       ` Josh Triplett
2014-06-01 10:35         ` Maciej W. Rozycki
2014-06-04 22:59           ` H. Peter Anvin
2014-06-06  9:02             ` Maciej W. Rozycki
2014-05-10 17:18 ` Greg Kroah-Hartman
2014-05-10 19:36   ` Josh Triplett

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=5873998.uv0CPtuiff@wuerfel \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=santosh.shukla@linaro.org \
    --cc=yuanhan.liu@linux.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