From mboxrd@z Thu Jan 1 00:00:00 1970 From: okaya@codeaurora.org (okaya@codeaurora.org) Date: Thu, 14 Jun 2018 06:33:41 -0400 Subject: Requirement to get BAR pci_bus_address in user space In-Reply-To: References: <20180614102001.GA20836@lst.de> Message-ID: <92a9eeced36f863458ca2fd029f17a20@codeaurora.org> 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@3:50 PM, Christoph Hellwig 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. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Return-Path: MIME-Version: 1.0 Date: Thu, 14 Jun 2018 06:33:41 -0400 From: okaya@codeaurora.org To: Srinath Mannam Subject: Re: Requirement to get BAR pci_bus_address in user space In-Reply-To: References: <20180614102001.GA20836@lst.de> Message-ID: <92a9eeced36f863458ca2fd029f17a20@codeaurora.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-pci-owner@vger.kernel.org, Abhishek Shah , kvm@vger.kernel.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org, Vikram Prakash , Alex Williamson , Bjorn Helgaas , Christoph Hellwig Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "Linux-nvme" Errors-To: linux-nvme-bounces+bjorn=helgaas.com@lists.infradead.org List-ID: 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 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. _______________________________________________ Linux-nvme mailing list Linux-nvme@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-nvme From mboxrd@z Thu Jan 1 00:00:00 1970 From: okaya@codeaurora.org Subject: Re: Requirement to get BAR pci_bus_address in user space Date: Thu, 14 Jun 2018 06:33:41 -0400 Message-ID: <92a9eeced36f863458ca2fd029f17a20@codeaurora.org> References: <20180614102001.GA20836@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Cc: Christoph Hellwig , Bjorn Helgaas , Abhishek Shah , Vikram Prakash , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org, Alex Williamson , kvm@vger.kernel.org, linux-pci-owner@vger.kernel.org To: Srinath Mannam Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org 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 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.