On 8/13/2016 2:55 AM, Alex Williamson wrote:
> On Fri, 12 Aug 2016 23:27:01 +0530
> Kirti Wankhede wrote:
>
>> On 8/12/2016 12:13 AM, Alex Williamson wrote:
>>
>>>
>>> TBH, I don't see how providing a default implementation of
>>> validate_map_request() is useful. How many mediated devices are
On Fri, 12 Aug 2016 23:27:01 +0530
Kirti Wankhede wrote:
> On 8/12/2016 12:13 AM, Alex Williamson wrote:
>
> >
> > TBH, I don't see how providing a default implementation of
> > validate_map_request() is useful. How many mediated devices are going
> > to want to identity map resources from the
On 8/12/2016 12:13 AM, Alex Williamson wrote:
>
> TBH, I don't see how providing a default implementation of
> validate_map_request() is useful. How many mediated devices are going
> to want to identity map resources from the parent? Even if they do, it
> seems we can only support a single me
On Thu, 11 Aug 2016 23:16:06 +0530
Kirti Wankhede wrote:
> On 8/11/2016 9:54 PM, Alex Williamson wrote:
> > On Thu, 11 Aug 2016 21:29:35 +0530
> > Kirti Wankhede wrote:
> >
> >> On 8/11/2016 4:30 AM, Alex Williamson wrote:
> >>> On Thu, 11 Aug 2016 02:53:10 +0530
> >>> Kirti Wankhede wrote
On 8/11/2016 9:54 PM, Alex Williamson wrote:
> On Thu, 11 Aug 2016 21:29:35 +0530
> Kirti Wankhede wrote:
>
>> On 8/11/2016 4:30 AM, Alex Williamson wrote:
>>> On Thu, 11 Aug 2016 02:53:10 +0530
>>> Kirti Wankhede wrote:
>>>
On 8/10/2016 12:30 AM, Alex Williamson wrote:
> On Thu,
On Thu, 11 Aug 2016 21:29:35 +0530
Kirti Wankhede wrote:
> On 8/11/2016 4:30 AM, Alex Williamson wrote:
> > On Thu, 11 Aug 2016 02:53:10 +0530
> > Kirti Wankhede wrote:
> >
> >> On 8/10/2016 12:30 AM, Alex Williamson wrote:
> >>> On Thu, 4 Aug 2016 00:33:52 +0530
> >>> Kirti Wankhede wrote
On 8/11/2016 4:30 AM, Alex Williamson wrote:
> On Thu, 11 Aug 2016 02:53:10 +0530
> Kirti Wankhede wrote:
>
>> On 8/10/2016 12:30 AM, Alex Williamson wrote:
>>> On Thu, 4 Aug 2016 00:33:52 +0530
>>> Kirti Wankhede wrote:
>>>
>>
>> ...
>>
+
+ switch (info.index) {
+
On Thu, 11 Aug 2016 02:53:10 +0530
Kirti Wankhede wrote:
> On 8/10/2016 12:30 AM, Alex Williamson wrote:
> > On Thu, 4 Aug 2016 00:33:52 +0530
> > Kirti Wankhede wrote:
> >
>
> ...
>
> >> +
> >> + switch (info.index) {
> >> + case VFIO_PCI_CONFIG_REGION_INDEX:
> >> +
On 8/10/2016 12:30 AM, Alex Williamson wrote:
> On Thu, 4 Aug 2016 00:33:52 +0530
> Kirti Wankhede wrote:
>
...
>> +
>> +switch (info.index) {
>> +case VFIO_PCI_CONFIG_REGION_INDEX:
>> +case VFIO_PCI_BAR0_REGION_INDEX ... VFIO_PCI_BAR5_REGION_INDEX:
>> +
On Thu, 4 Aug 2016 00:33:52 +0530
Kirti Wankhede wrote:
> MPCI VFIO driver registers with MDEV core driver. MDEV core driver creates
> mediated device and calls probe routine of MPCI VFIO driver. This driver
> adds mediated device to VFIO core module.
> Main aim of this module is to manage all VF
Hi Kirti,
[auto build test WARNING on vfio/next]
[also build test WARNING on v4.7 next-20160803]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Kirti-Wankhede/Add-Mediated-device-support/2016080
Hi Kirti,
[auto build test WARNING on vfio/next]
[also build test WARNING on v4.7 next-20160803]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Kirti-Wankhede/Add-Mediated-device-support/2016080
MPCI VFIO driver registers with MDEV core driver. MDEV core driver creates
mediated device and calls probe routine of MPCI VFIO driver. This driver
adds mediated device to VFIO core module.
Main aim of this module is to manage all VFIO APIs for each mediated PCI
device. Those are:
- get region info
13 matches
Mail list logo