RE: [PATCH v4 2/2] vfio: no need to pass kvm pointer during device open

From: Tian, Kevin
Date: Sun Feb 05 2023 - 22:53:38 EST

Next message: Stephen Rothwell: "linux-next: build warning after merge of the bpf-next tree"
Previous message: Suthikulpanit, Suravee: "Re: [PATCH] KVM: SVM: Modify AVIC GATag to support max number of 512 vCPUs"
In reply to: Liu, Yi L: "RE: [PATCH v4 2/2] vfio: no need to pass kvm pointer during device open"
Next in thread: Anthony Krowiak: "Re: [PATCH v4 2/2] vfio: no need to pass kvm pointer during device open"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> From: Matthew Rosato <mjrosato@xxxxxxxxxxxxx>
> Sent: Saturday, February 4, 2023 5:50 AM
>
> Nothing uses this value during vfio_device_open anymore so it's safe
> to remove it.
>
> Signed-off-by: Matthew Rosato <mjrosato@xxxxxxxxxxxxx>

Reviewed-by: Kevin Tian <kevin.tian@xxxxxxxxx>

Next message: Stephen Rothwell: "linux-next: build warning after merge of the bpf-next tree"
Previous message: Suthikulpanit, Suravee: "Re: [PATCH] KVM: SVM: Modify AVIC GATag to support max number of 512 vCPUs"
In reply to: Liu, Yi L: "RE: [PATCH v4 2/2] vfio: no need to pass kvm pointer during device open"
Next in thread: Anthony Krowiak: "Re: [PATCH v4 2/2] vfio: no need to pass kvm pointer during device open"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]