All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jike Song <jike.song@intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
	Kirti Wankhede <kwankhede@nvidia.com>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	"guangrong.xiao@linux.intel.com" <guangrong.xiao@linux.intel.com>,
	"cjia@nvidia.com" <cjia@nvidia.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [v7 2/3] vfio: support notifier chain in vfio_group
Date: Wed, 23 Nov 2016 15:53:23 +0800	[thread overview]
Message-ID: <58354AF3.4070406@intel.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D18E0305A8@SHSMSX101.ccr.corp.intel.com>

On 11/23/2016 02:33 PM, Tian, Kevin wrote:
>> From: Song, Jike
>> Sent: Wednesday, November 23, 2016 2:30 PM
>> On 11/23/2016 01:56 PM, Alex Williamson wrote:
>>> On Wed, 23 Nov 2016 10:22:37 +0530
>>> Kirti Wankhede <kwankhede@nvidia.com> wrote:
>>>>
>>>> Most of the distro's kernel have CONFIG_MODVERSIONS enabled and its
>>>> mostly safe to build driver against the kernel to which its going to load.
>>>> For backend IOMMU module, we have same callback functions or
>>>> VFIO_IOMMU_NOTIFY, but as Alex mentioned different IOMMU backend modules
>>>> might have different events/actions. Then the event check shouldn't be
>>>> in vfio module, it should be in backend module.
>>>
>>> Yes, patch 1/3 is wrong, the required events mask should be passed to
>>> the iommu backend and handled there, not in vfio.c.  Thanks,
>>
>> Will change that. BTW, do you think the iommu types should be different?
>> that is to say, having VFIO_IOMMU_NOTIFY_TYPE1 instead of VFIO_IOMMU_NOTIFY?
>>
> 
> Should vendor driver care about underlying IOMMU difference? Assume
> those notification events should be IOMMU vendor agnostic... 

I also lean towards keeping VFIO_IOMMU_NOTIFY, will update [1/3] without
changing that part.

--
Thanks,
Jike

  reply	other threads:[~2016-11-23  7:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22  6:09 [v7 0/3] plumb kvm/vfio to notify kvm:group attach/detach Jike Song
2016-11-22  6:09 ` [v7 1/3] vfio: vfio_register_notifier: classify iommu notifier Jike Song
2016-11-23  8:50   ` [UPDATE v7 " Jike Song
2016-11-22  6:09 ` [v7 2/3] vfio: support notifier chain in vfio_group Jike Song
2016-11-22 13:35   ` Kirti Wankhede
2016-11-22 14:02     ` Alex Williamson
2016-11-22 14:39       ` Kirti Wankhede
2016-11-22 14:50         ` Alex Williamson
2016-11-23  3:20           ` Jike Song
2016-11-23  4:52             ` Kirti Wankhede
2016-11-23  5:56               ` Alex Williamson
2016-11-23  6:29                 ` Jike Song
2016-11-23  6:33                   ` Tian, Kevin
2016-11-23  7:53                     ` Jike Song [this message]
2016-11-23 12:45                       ` Alex Williamson
2016-11-22  6:09 ` [v7 3/3] kvm: set/clear kvm to/from vfio_group when group add/delete Jike Song
2016-11-30 17:02   ` Alex Williamson
2016-12-01  2:47     ` Jike Song
2016-11-29  3:02 ` [v7 0/3] plumb kvm/vfio to notify kvm:group attach/detach Jike Song
2016-11-30 17:06   ` Alex Williamson
2016-12-01  2:27     ` Jike Song
2016-12-01  4:42       ` Kirti Wankhede

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=58354AF3.4070406@intel.com \
    --to=jike.song@intel.com \
    --cc=alex.williamson@redhat.com \
    --cc=cjia@nvidia.com \
    --cc=guangrong.xiao@linux.intel.com \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwankhede@nvidia.com \
    --cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.