On Wed, Jan 27, 2016 at 9:26 PM, Santosh Shukla wrote:
> On Wed, Jan 27, 2016 at 9:09 PM, Thomas Monjalon
> wrote:
>> 2016-01-27 21:02, Santosh Shukla:
>>> 1. virtio currently works for vfio+noiommu and likely will work for
>>> vfio+iommu in near future.
>>> 2. So remove __noiommu suffix and alwa
On Wed, Jan 27, 2016 at 9:09 PM, Thomas Monjalon
wrote:
> 2016-01-27 21:02, Santosh Shukla:
>> 1. virtio currently works for vfio+noiommu and likely will work for
>> vfio+iommu in near future.
>> 2. So remove __noiommu suffix and always use default.
>> 3. Introduce vfio resource parsing global fun
On Wed, Jan 27, 2016 at 4:11 PM, Santosh Shukla wrote:
> On Tue, Jan 26, 2016 at 9:51 PM, Santosh Shukla wrote:
>> On Tue, Jan 26, 2016 at 7:58 PM, Thomas Monjalon
>> wrote:
>>> 2016-01-26 19:35, Santosh Shukla:
On Tue, Jan 26, 2016 at 6:30 PM, Thomas Monjalon
wrote:
> 2016-01-26
2016-01-27 21:02, Santosh Shukla:
> 1. virtio currently works for vfio+noiommu and likely will work for
> vfio+iommu in near future.
> 2. So remove __noiommu suffix and always use default.
> 3. Introduce vfio resource parsing global function, That function
> suppose to do parsing for default vfio c
On Tue, Jan 26, 2016 at 9:51 PM, Santosh Shukla wrote:
> On Tue, Jan 26, 2016 at 7:58 PM, Thomas Monjalon
> wrote:
>> 2016-01-26 19:35, Santosh Shukla:
>>> On Tue, Jan 26, 2016 at 6:30 PM, Thomas Monjalon
>>> wrote:
>>> > 2016-01-26 15:56, Santosh Shukla:
>>> >> In my observation, currently virt
On Tue, Jan 26, 2016 at 7:58 PM, Thomas Monjalon
wrote:
> 2016-01-26 19:35, Santosh Shukla:
>> On Tue, Jan 26, 2016 at 6:30 PM, Thomas Monjalon
>> wrote:
>> > 2016-01-26 15:56, Santosh Shukla:
>> >> In my observation, currently virtio work for vfio-noiommu, that's why
>> >> said drv->kdrv need to
On Tue, Jan 26, 2016 at 6:30 PM, Thomas Monjalon
wrote:
> 2016-01-26 15:56, Santosh Shukla:
>> On Mon, Jan 25, 2016 at 8:59 PM, Thomas Monjalon
>> wrote:
>> > 2016-01-21 22:47, Santosh Shukla:
>> >> On Thu, Jan 21, 2016 at 8:16 PM, Thomas Monjalon
>> >> wrote:
>> >> > 2016-01-21 17:34, Santosh S
On Mon, Jan 25, 2016 at 8:59 PM, Thomas Monjalon
wrote:
> 2016-01-21 22:47, Santosh Shukla:
>> On Thu, Jan 21, 2016 at 8:16 PM, Thomas Monjalon
>> wrote:
>> > 2016-01-21 17:34, Santosh Shukla:
>> >> On Thu, Jan 21, 2016 at 4:58 PM, Thomas Monjalon
>> >> wrote:
>> >> > 2016-01-21 16:43, Santosh S
2016-01-26 19:35, Santosh Shukla:
> On Tue, Jan 26, 2016 at 6:30 PM, Thomas Monjalon
> wrote:
> > 2016-01-26 15:56, Santosh Shukla:
> >> In my observation, currently virtio work for vfio-noiommu, that's why
> >> said drv->kdrv need to know vfio mode.
> >
> > It is your observation. It may change i
2016-01-26 15:56, Santosh Shukla:
> On Mon, Jan 25, 2016 at 8:59 PM, Thomas Monjalon
> wrote:
> > 2016-01-21 22:47, Santosh Shukla:
> >> On Thu, Jan 21, 2016 at 8:16 PM, Thomas Monjalon
> >> wrote:
> >> > 2016-01-21 17:34, Santosh Shukla:
> >> >> On Thu, Jan 21, 2016 at 4:58 PM, Thomas Monjalon
>
2016-01-21 22:47, Santosh Shukla:
> On Thu, Jan 21, 2016 at 8:16 PM, Thomas Monjalon
> wrote:
> > 2016-01-21 17:34, Santosh Shukla:
> >> On Thu, Jan 21, 2016 at 4:58 PM, Thomas Monjalon
> >> wrote:
> >> > 2016-01-21 16:43, Santosh Shukla:
> >> >> David Marchand wrote:
> >> >> > This is a mode (s
On Thu, Jan 21, 2016 at 8:16 PM, Thomas Monjalon
wrote:
> 2016-01-21 17:34, Santosh Shukla:
>> On Thu, Jan 21, 2016 at 4:58 PM, Thomas Monjalon
>> wrote:
>> > 2016-01-21 16:43, Santosh Shukla:
>> >> David Marchand wrote:
>> >> > This is a mode (specific to vfio), not a new kernel driver.
>> >> >
On Thu, Jan 21, 2016 at 4:58 PM, Thomas Monjalon
wrote:
> 2016-01-21 16:43, Santosh Shukla:
>> David Marchand wrote:
>> > This is a mode (specific to vfio), not a new kernel driver.
>> >
>> Yes, Specific to VFIO and this is why noiommu appended after vfio i.e..
>> __VFIO and __VFIO_NOIOMMU.
>
> W
On Thu, Jan 21, 2016 at 4:02 PM, David Marchand
wrote:
> Santosh,
>
> On Tue, Jan 19, 2016 at 7:57 PM, Santosh Shukla
> wrote:
> > Adding RTE_KDRV_VFIO_NOIOMMU mode in kernel driver. Also including
> > rte_vfio_is_noiommu() helper function. This function will parse
> > /sys/bus/pci/device// and
2016-01-21 17:34, Santosh Shukla:
> On Thu, Jan 21, 2016 at 4:58 PM, Thomas Monjalon
> wrote:
> > 2016-01-21 16:43, Santosh Shukla:
> >> David Marchand wrote:
> >> > This is a mode (specific to vfio), not a new kernel driver.
> >> >
> >> Yes, Specific to VFIO and this is why noiommu appended afte
2016-01-21 16:43, Santosh Shukla:
> David Marchand wrote:
> > This is a mode (specific to vfio), not a new kernel driver.
> >
> Yes, Specific to VFIO and this is why noiommu appended after vfio i.e..
> __VFIO and __VFIO_NOIOMMU.
Woaaa! Your logic is really disappointing :)
Specific to VFIO => app
Santosh,
On Tue, Jan 19, 2016 at 7:57 PM, Santosh Shukla wrote:
> Adding RTE_KDRV_VFIO_NOIOMMU mode in kernel driver. Also including
> rte_vfio_is_noiommu() helper function. This function will parse
> /sys/bus/pci/device// and make sure that
> - vfio noiommu mode set in kernel driver
> - pci devi
Adding RTE_KDRV_VFIO_NOIOMMU mode in kernel driver. Also including
rte_vfio_is_noiommu() helper function. This function will parse
/sys/bus/pci/device// and make sure that
- vfio noiommu mode set in kernel driver
- pci device attached to vfio-noiommu driver only
If both condition satisfies then se
18 matches
Mail list logo