[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fa1bdd92-c4c1-8ed4-a06a-13bc253ceed6@nvidia.com>
Date: Mon, 3 Dec 2018 21:57:49 +0530
From: Kirti Wankhede <kwankhede@...dia.com>
To: Christoph Hellwig <hch@...radead.org>
CC: Lu Baolu <baolu.lu@...ux.intel.com>,
Alex Williamson <alex.williamson@...hat.com>,
Joerg Roedel <joro@...tes.org>,
David Woodhouse <dwmw2@...radead.org>, <ashok.raj@...el.com>,
<sanjay.k.kumar@...el.com>, <jacob.jun.pan@...el.com>,
<kevin.tian@...el.com>,
Jean-Philippe Brucker <jean-philippe.brucker@....com>,
<yi.l.liu@...el.com>, <yi.y.sun@...el.com>, <peterx@...hat.com>,
<tiwei.bie@...el.com>, Zeng Xin <xin.zeng@...el.com>,
<iommu@...ts.linux-foundation.org>, <kvm@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
Jacob Pan <jacob.jun.pan@...ux.intel.com>
Subject: Re: [PATCH v4 6/8] vfio/mdev: Add iommu place holders in mdev_device
On 11/21/2018 2:15 PM, Christoph Hellwig wrote:
> On Wed, Nov 21, 2018 at 02:22:08AM +0530, Kirti Wankhede wrote:
>> It is about how mdev framework can be used by existing drivers. These
>> symbols doesn't use any other exported symbols.
>
> That is an unfortunate accident of history, but doesn't extent to new
> ones. It also is another inidicator those drivers probably are derived
> works of the Linux kernel and might be in legal trouble one way or
> another.
>
These symbols are just to associate iommu properties of a physical
device with a mdev device, doesn't include low-level information.
Thanks,
Kirti
Powered by blists - more mailing lists