From: okaya@codeaurora.org
To: Srinath Mannam <srinath.mannam@broadcom.com>
Cc: Christoph Hellwig <hch@lst.de>,
Bjorn Helgaas <bhelgaas@google.com>,
Abhishek Shah <abhishek.shah@broadcom.com>,
Vikram Prakash <vikram.prakash@broadcom.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org,
Alex Williamson <alex.williamson@redhat.com>,
kvm@vger.kernel.org, linux-pci-owner@vger.kernel.org
Subject: Re: Requirement to get BAR pci_bus_address in user space
Date: Thu, 14 Jun 2018 06:33:41 -0400 [thread overview]
Message-ID: <92a9eeced36f863458ca2fd029f17a20@codeaurora.org> (raw)
In-Reply-To: <CABe79T6k387EnDrpydTbQYQ+sZoWXKUee23EDzDJqnkroOmodA@mail.gmail.com>
On 2018-06-14 06:29, Srinath Mannam wrote:
> ++ Alex Williamson, kvm,
>
> Hi Christoph,
>
> Thank you for quick reply.
>
> If we want to add this in vfio then I think we need to do the same in
> uio case also.
>
> As I mentioned in previous mail, in the current implementation
> resource information (address and size) is gathering from resource
> named file created in /sys directory.
> So I expect it would be better to have similar method as existing in
> sysfs.
>
Can you give some info on why you need the actual bar address value?
>
> Regards,
> Srinath.
>
> On Thu, Jun 14, 2018 at 3:50 PM, Christoph Hellwig <hch@lst.de> wrote:
>> The only safe way to use PCI(e) devices in userspace is through vfio.
>> I think that is where you need to take your inquiries.
next prev parent reply other threads:[~2018-06-14 10:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 10:07 Requirement to get BAR pci_bus_address in user space Srinath Mannam
2018-06-14 10:20 ` Christoph Hellwig
2018-06-14 10:29 ` Srinath Mannam
2018-06-14 10:33 ` okaya [this message]
2018-06-14 10:48 ` Srinath Mannam
2018-06-14 14:42 ` Keith Busch
2018-06-14 14:50 ` Alex Williamson
2018-06-14 14:59 ` Christoph Hellwig
2018-06-14 20:04 ` Walker, Benjamin
2018-06-15 6:11 ` Srinath Mannam
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=92a9eeced36f863458ca2fd029f17a20@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=abhishek.shah@broadcom.com \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=hch@lst.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci-owner@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=srinath.mannam@broadcom.com \
--cc=vikram.prakash@broadcom.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