[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9461f821-73fd-a66f-e142-c1a55e38e7a0@redhat.com>
Date: Fri, 6 Dec 2019 17:13:30 -0600
From: Eric Blake <eblake@...hat.com>
To: Yan Zhao <yan.y.zhao@...el.com>, alex.williamson@...hat.com
Cc: kevin.tian@...el.com, kvm@...r.kernel.org, libvir-list@...hat.com,
cohuck@...hat.com, linux-kernel@...r.kernel.org,
zhenyuw@...ux.intel.com, qemu-devel@...gnu.org,
shaopeng.he@...el.com, zhi.a.wang@...el.com
Subject: Re: [RFC PATCH 1/9] vfio/pci: introduce mediate ops to intercept
vfio-pci ops
On 12/4/19 9:25 PM, Yan Zhao wrote:
> when vfio-pci is bound to a physical device, almost all the hardware
> resources are passthroughed.
The intent is obvious, but it sounds awkward to a native speaker.
s/passthroughed/passed through/
> Sometimes, vendor driver of this physcial device may want to mediate some
physical
> hardware resource access for a short period of time, e.g. dirty page
> tracking during live migration.
>
> Here we introduce mediate ops in vfio-pci for this purpose.
>
> Vendor driver can register a mediate ops to vfio-pci.
> But rather than directly bind to the passthroughed device, the
passed-through
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
Powered by blists - more mailing lists