> From: Daniel P. Berrangé
> Sent: Friday, April 29, 2022 12:20 AM
>
> On Thu, Apr 28, 2022 at 08:24:48AM -0600, Alex Williamson wrote:
> > On Thu, 28 Apr 2022 03:21:45 +
> > "Tian, Kevin" wrote:
> >
> > > > From: Alex Williamson
> > > > Sent: Wednesday, April 27, 2022 12:22 AM
> > > > > >
On Thu, Apr 28, 2022 at 08:24:48AM -0600, Alex Williamson wrote:
> On Thu, 28 Apr 2022 03:21:45 +
> "Tian, Kevin" wrote:
>
> > > From: Alex Williamson
> > > Sent: Wednesday, April 27, 2022 12:22 AM
> > > > >
> > > > > My expectation would be that libvirt uses:
> > > > >
> > > > > -object
On Thu, 28 Apr 2022 03:21:45 +
"Tian, Kevin" wrote:
> > From: Alex Williamson
> > Sent: Wednesday, April 27, 2022 12:22 AM
> > > >
> > > > My expectation would be that libvirt uses:
> > > >
> > > > -object iommufd,id=iommufd0,fd=NNN
> > > > -device vfio-pci,fd=MMM,iommufd=iommufd0
> > >
> From: Alex Williamson
> Sent: Wednesday, April 27, 2022 12:22 AM
> > >
> > > My expectation would be that libvirt uses:
> > >
> > > -object iommufd,id=iommufd0,fd=NNN
> > > -device vfio-pci,fd=MMM,iommufd=iommufd0
> > >
> > > Whereas simple QEMU command line would be:
> > >
> > > -object iomm
On Tue, 26 Apr 2022 13:42:17 -0300
Jason Gunthorpe wrote:
> On Tue, Apr 26, 2022 at 10:21:59AM -0600, Alex Williamson wrote:
> > We also need to be able to advise libvirt as to how each iommufd object
> > or user of that object factors into the VM locked memory requirement.
> > When used by vfio-
On Tue, 26 Apr 2022 08:37:41 +
"Tian, Kevin" wrote:
> > From: Alex Williamson
> > Sent: Monday, April 25, 2022 10:38 PM
> >
> > On Mon, 25 Apr 2022 11:10:14 +0100
> > Daniel P. Berrangé wrote:
> >
> > > On Fri, Apr 22, 2022 at 04:09:43PM -0600, Alex Williamson wrote:
> > > > [Cc +libv
> From: Alex Williamson
> Sent: Monday, April 25, 2022 10:38 PM
>
> On Mon, 25 Apr 2022 11:10:14 +0100
> Daniel P. Berrangé wrote:
>
> > On Fri, Apr 22, 2022 at 04:09:43PM -0600, Alex Williamson wrote:
> > > [Cc +libvirt folks]
> > >
> > > On Thu, 14 Apr 2022 03:46:52 -0700
> > > Yi Liu wrote:
Hi Alex,
On 4/23/22 12:09 AM, Alex Williamson wrote:
> [Cc +libvirt folks]
>
> On Thu, 14 Apr 2022 03:46:52 -0700
> Yi Liu wrote:
>
>> With the introduction of iommufd[1], the linux kernel provides a generic
>> interface for userspace drivers to propagate their DMA mappings to kernel
>> for assig
On Mon, 25 Apr 2022 22:23:05 +0200
Eric Auger wrote:
> Hi Alex,
>
> On 4/23/22 12:09 AM, Alex Williamson wrote:
> > [Cc +libvirt folks]
> >
> > On Thu, 14 Apr 2022 03:46:52 -0700
> > Yi Liu wrote:
> >
> >> With the introduction of iommufd[1], the linux kernel provides a generic
> >> interface
On Mon, 25 Apr 2022 11:10:14 +0100
Daniel P. Berrangé wrote:
> On Fri, Apr 22, 2022 at 04:09:43PM -0600, Alex Williamson wrote:
> > [Cc +libvirt folks]
> >
> > On Thu, 14 Apr 2022 03:46:52 -0700
> > Yi Liu wrote:
> >
> > > With the introduction of iommufd[1], the linux kernel provides a gene
On Fri, Apr 22, 2022 at 04:09:43PM -0600, Alex Williamson wrote:
> [Cc +libvirt folks]
>
> On Thu, 14 Apr 2022 03:46:52 -0700
> Yi Liu wrote:
>
> > With the introduction of iommufd[1], the linux kernel provides a generic
> > interface for userspace drivers to propagate their DMA mappings to kern
[Cc +libvirt folks]
On Thu, 14 Apr 2022 03:46:52 -0700
Yi Liu wrote:
> With the introduction of iommufd[1], the linux kernel provides a generic
> interface for userspace drivers to propagate their DMA mappings to kernel
> for assigned devices. This series does the porting of the VFIO devices
> o
12 matches
Mail list logo