Re: [PATCH RFC] vfio: Move the saving of the config space to the right place in VFIO migration

On Mon, Nov 23, 2020 at 11:14:38AM +0800, Shenming Lu wrote: > External email: Use caution opening links or attachments > > > On 2020/11/21 6:01, Alex Williamson wrote: > > On Fri, 20 Nov 2020 22:05:49 +0800 > > Shenming Lu wrote: > > > >> On 2020/11/20 1:41, Alex Williamson wrote: > >>> On

Re: [RFC PATCH for-QEMU-5.2] vfio: Make migration support experimental

On Tue, Nov 10, 2020 at 08:20:50AM -0700, Alex Williamson wrote: > External email: Use caution opening links or attachments > > > On Tue, 10 Nov 2020 19:46:20 +0530 > Kirti Wankhede wrote: > > > On 11/10/2020 2:40 PM, Dr. David Alan Gilbert wrote: > > > * Alex Williamson

Re: [Qemu-devel] [PATCH 1/2] vfio/mdev: add version field as mandatory attribute for mdev device

On Tue, Apr 23, 2019 at 11:39:39AM +0100, Daniel P. Berrangé wrote: > On Fri, Apr 19, 2019 at 04:35:04AM -0400, Yan Zhao wrote: > > device version attribute in mdev sysfs is used by user space software > > (e.g. libvirt) to query device compatibility for live migration of VFIO > > mdev devices.

Re: [Qemu-devel] [PATCH v3 0/5] Add migration support for VFIO device

On Thu, Feb 21, 2019 at 05:52:53AM +, Tian, Kevin wrote: > > From: Kirti Wankhede [mailto:kwankh...@nvidia.com] > > Sent: Thursday, February 21, 2019 1:25 PM > > > > On 2/20/2019 3:52 PM, Dr. David Alan Gilbert wrote: > > > * Kirti Wankhede (kwankh...@nvidia.com) wrote: > > >> Add migration

Re: [Qemu-devel] [PATCH v14 00/22] Add Mediated device support

On Thu, Nov 17, 2016 at 02:25:15PM -0700, Alex Williamson wrote: > On Thu, 17 Nov 2016 02:16:12 +0530 > Kirti Wankhede wrote: > > > > Documentation/ABI/testing/sysfs-bus-vfio-mdev | 111 ++ > > Documentation/vfio-mediated-device.txt| 399 +++ > > MAINTAINERS

Re: [Qemu-devel] [PATCH 1/2] KVM: page track: add a new notifier type: track_flush_slot

On Fri, Oct 14, 2016 at 10:51:24AM -0600, Alex Williamson wrote: > On Fri, 14 Oct 2016 09:35:45 -0700 > Neo Jia <c...@nvidia.com> wrote: > > > On Fri, Oct 14, 2016 at 08:46:01AM -0600, Alex Williamson wrote: > > > On Fri, 14 Oct 2016 08:41:58 -0600 >

Re: [Qemu-devel] [PATCH 1/2] KVM: page track: add a new notifier type: track_flush_slot

;>> > > > >>> > > > >>> On 11/10/2016 04:39, Xiao Guangrong wrote: > > > >>>> > > > >>>> > > > >>>> On 10/11/2016 02:32 AM, Paolo Bonzini wrote: > > > >>>>>

Re: [Qemu-devel] summary of current vfio mdev upstreaming status

On Thu, Sep 29, 2016 at 05:05:47PM +0800, Xiao Guangrong wrote: > > > On 09/29/2016 04:55 PM, Jike Song wrote: > > Hi all, > > > > In order to have a clear understanding about the VFIO mdev upstreaming > > status, I'd like to summarize it. Please share your opinions on this, > > and correct my

Re: [Qemu-devel] summary of current vfio mdev upstreaming status

On Thu, Sep 29, 2016 at 04:55:39PM +0800, Jike Song wrote: > Hi all, > > In order to have a clear understanding about the VFIO mdev upstreaming > status, I'd like to summarize it. Please share your opinions on this, > and correct my misunderstandings. > > The whole vfio mdev series can be

Re: [Qemu-devel] [libvirt] [RFC v2] libvirt vGPU QEMU integration

On Thu, Sep 29, 2016 at 09:03:40AM +0100, Daniel P. Berrange wrote: > On Wed, Sep 28, 2016 at 12:22:35PM -0700, Neo Jia wrote: > > On Thu, Sep 22, 2016 at 03:26:38PM +0100, Daniel P. Berrange wrote: > > > On Thu, Sep 22, 2016 at 08:19:21AM -0600, Alex Williamson wrote: > >

Re: [Qemu-devel] [libvirt] [RFC v2] libvirt vGPU QEMU integration

On Wed, Sep 28, 2016 at 04:31:25PM -0400, Laine Stump wrote: > On 09/28/2016 03:59 PM, Neo Jia wrote: > > On Wed, Sep 28, 2016 at 07:45:38PM +, Tian, Kevin wrote: > > > > From: Neo Jia [mailto:c...@nvidia.com] > > > > Sent: Thursday, September 29, 2016 3:23 A

Re: [Qemu-devel] [libvirt] [RFC v2] libvirt vGPU QEMU integration

On Wed, Sep 28, 2016 at 01:55:47PM -0600, Alex Williamson wrote: > On Wed, 28 Sep 2016 12:22:35 -0700 > Neo Jia <c...@nvidia.com> wrote: > > > On Thu, Sep 22, 2016 at 03:26:38PM +0100, Daniel P. Berrange wrote: > > > On Thu, Sep 22, 2016 at 08:19:21A

Re: [Qemu-devel] [libvirt] [RFC v2] libvirt vGPU QEMU integration

On Wed, Sep 28, 2016 at 07:45:38PM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Thursday, September 29, 2016 3:23 AM > > > > On Thu, Sep 22, 2016 at 03:26:38PM +0100, Daniel P. Berrange wrote: > > > On Thu, Sep 22, 2016 at 08:19:

Re: [Qemu-devel] [RFC v2] libvirt vGPU QEMU integration

On Tue, Sep 20, 2016 at 10:47:53AM +0100, Daniel P. Berrange wrote: > On Tue, Sep 20, 2016 at 02:05:52AM +0530, Kirti Wankhede wrote: > > > > Hi libvirt experts, > > > > Thanks for valuable input on v1 version of RFC. > > > > Quick brief, VFIO based mediated device framework provides a way to >

Re: [Qemu-devel] [libvirt] [RFC v2] libvirt vGPU QEMU integration

On Thu, Sep 22, 2016 at 03:26:38PM +0100, Daniel P. Berrange wrote: > On Thu, Sep 22, 2016 at 08:19:21AM -0600, Alex Williamson wrote: > > On Thu, 22 Sep 2016 09:41:20 +0530 > > Kirti Wankhede wrote: > > > > > > My concern is that a type id seems arbitrary but we're

Re: [Qemu-devel] [PATCH v7 1/4] vfio: Mediated device Core driver

On Thu, Sep 08, 2016 at 04:09:39PM +0800, Jike Song wrote: > On 08/25/2016 11:53 AM, Kirti Wankhede wrote: > > + > > +/** > > + * struct parent_ops - Structure to be registered for each parent device to > > + * register the device to mdev module. > > + * > > + * @owner: The module owner. >

Re: [Qemu-devel] [PATCH v7 0/4] Add Mediated device support

On Wed, Sep 07, 2016 at 07:27:19PM +0100, Daniel P. Berrange wrote: > On Wed, Sep 07, 2016 at 11:17:39AM -0700, Neo Jia wrote: > > On Wed, Sep 07, 2016 at 10:44:56AM -0600, Alex Williamson wrote: > > > On Wed, 7 Sep 2016 21:45:31 +0530 > > > Kirti Wankhede &

Re: [Qemu-devel] [PATCH v7 0/4] Add Mediated device support

On Wed, Sep 07, 2016 at 10:44:56AM -0600, Alex Williamson wrote: > On Wed, 7 Sep 2016 21:45:31 +0530 > Kirti Wankhede wrote: > > > To hot-plug mdev device to a domain in which there is already a mdev > > device assigned, mdev device should be created with same group number

Re: [Qemu-devel] [RFC v2 0/4] adding mdev bus and vfio support

On Wed, Sep 07, 2016 at 10:22:26AM +0800, Jike Song wrote: > On 09/02/2016 11:03 PM, Alex Williamson wrote: > > On Fri, 2 Sep 2016 16:16:08 +0800 > > Jike Song wrote: > > > >> This patchset is based on NVidia's "Add Mediated device support" series, > >> version 6: > >> >

Re: [Qemu-devel] [RFC v2 4/4] docs: Add Documentation for Mediated devices

of > > mediated device framework. > > > > Signed-off-by: Kirti Wankhede <kwankh...@nvidia.com> > > Signed-off-by: Neo Jia <c...@nvidia.com> > > Signed-off-by: Jike Song <jike.s...@intel.com> > > --- > > Documentation/vfio-mediate

Re: [Qemu-devel] [RFC v2 0/4] adding mdev bus and vfio support

On Fri, Sep 02, 2016 at 09:03:52AM -0600, Alex Williamson wrote: > On Fri, 2 Sep 2016 16:16:08 +0800 > Jike Song wrote: > > > This patchset is based on NVidia's "Add Mediated device support" series, > > version 6: > > > >

Re: [Qemu-devel] [libvirt] [RFC] libvirt vGPU QEMU integration

On Fri, Aug 19, 2016 at 03:22:48PM -0400, Laine Stump wrote: > On 08/18/2016 12:41 PM, Neo Jia wrote: > > Hi libvirt experts, > > > > I am starting this email thread to discuss the potential solution / > > proposal of > > integrating vGPU support i

Re: [Qemu-devel] [libvirt] [RFC] libvirt vGPU QEMU integration

On Fri, Aug 19, 2016 at 02:42:27PM +0200, Michal Privoznik wrote: > On 18.08.2016 18:41, Neo Jia wrote: > > Hi libvirt experts, > > Hi, welcome to the list. > > > > > I am starting this email thread to discuss the potential solution / > > proposal of >

[Qemu-devel] [RFC] libvirt vGPU QEMU integration

Hi libvirt experts, I am starting this email thread to discuss the potential solution / proposal of integrating vGPU support into libvirt for QEMU. Some quick background, NVIDIA is implementing a VFIO based mediated device framework to allow people to virtualize their devices without SR-IOV, for

Re: [Qemu-devel] [RFC v6-based v1 0/5] refine mdev framework

On Wed, Aug 17, 2016 at 04:58:14PM +0800, Dong Jia wrote: > On Tue, 16 Aug 2016 16:14:12 +0800 > Jike Song wrote: > > > > > This patchset is based on NVidia's "Add Mediated device support" series, > > version 6: > > > > http://www.spinics.net/lists/kvm/msg136472.html

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Tue, Aug 16, 2016 at 02:51:03PM -0600, Alex Williamson wrote: > On Tue, 16 Aug 2016 13:30:06 -0700 > Neo Jia <c...@nvidia.com> wrote: > > > On Mon, Aug 15, 2016 at 04:47:41PM -0600, Alex Williamson wrote: > > > On Mon, 15 Aug 2016 12:59:08 -0700 > &g

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Mon, Aug 15, 2016 at 04:47:41PM -0600, Alex Williamson wrote: > On Mon, 15 Aug 2016 12:59:08 -0700 > Neo Jia <c...@nvidia.com> wrote: > > > > > > > > > > > I'm not sure a comma separated list makes sense here, for both > > > > > si

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Tue, Aug 16, 2016 at 05:58:54AM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Tuesday, August 16, 2016 1:44 PM > > > > On Tue, Aug 16, 2016 at 04:52:30AM +, Tian, Kevin wrote: > > > > From: Neo Jia [mailto:c...@nvidia.c

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Tue, Aug 16, 2016 at 04:52:30AM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Tuesday, August 16, 2016 12:17 PM > > > > On Tue, Aug 16, 2016 at 03:50:44AM +, Tian, Kevin wrote: > > > > From: Neo Jia [mailto:c...@nvidia.c

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Tue, Aug 16, 2016 at 03:50:44AM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Tuesday, August 16, 2016 11:46 AM > > > > On Tue, Aug 16, 2016 at 12:30:25AM +, Tian, Kevin wrote: > > > > From: Neo Jia [mailto:c...@nvidia.c

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Tue, Aug 16, 2016 at 12:30:25AM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Tuesday, August 16, 2016 3:59 AM > > > > > > > > For NVIDIA vGPU solution we need to know all devices assigned to a VM in > > > > on

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Mon, Aug 15, 2016 at 04:47:41PM -0600, Alex Williamson wrote: > On Mon, 15 Aug 2016 12:59:08 -0700 > Neo Jia <c...@nvidia.com> wrote: > > > On Mon, Aug 15, 2016 at 09:38:52AM +, Tian, Kevin wrote: > > > > From: Kirti Wankhede [mailto:kwankh...@nvidia.com]

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Mon, Aug 15, 2016 at 04:52:39PM -0600, Alex Williamson wrote: > On Mon, 15 Aug 2016 15:09:30 -0700 > Neo Jia <c...@nvidia.com> wrote: > > > On Mon, Aug 15, 2016 at 09:59:26AM -0600, Alex Williamson wrote: > > > On Mon, 15 Aug 2016 09:38:52 + > > > &qu

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Mon, Aug 15, 2016 at 09:59:26AM -0600, Alex Williamson wrote: > On Mon, 15 Aug 2016 09:38:52 + > "Tian, Kevin" wrote: > > > > From: Kirti Wankhede [mailto:kwankh...@nvidia.com] > > > Sent: Saturday, August 13, 2016 8:37 AM > > > > > > > > > > > > On 8/13/2016 2:46

Re: [Qemu-devel] [PATCH v6 1/4] vfio: Mediated device Core driver

On Mon, Aug 15, 2016 at 09:38:52AM +, Tian, Kevin wrote: > > From: Kirti Wankhede [mailto:kwankh...@nvidia.com] > > Sent: Saturday, August 13, 2016 8:37 AM > > > > > > > > On 8/13/2016 2:46 AM, Alex Williamson wrote: > > > On Sat, 13 Aug 2016 00:14:39 +0530 > > > Kirti Wankhede

Re: [Qemu-devel] [RFC PATCH v4 1/3] Mediated device Core driver

On Wed, Jun 08, 2016 at 02:13:49PM +0800, Dong Jia wrote: > On Tue, 7 Jun 2016 20:48:42 -0700 > Neo Jia <c...@nvidia.com> wrote: > > > On Wed, Jun 08, 2016 at 11:18:42AM +0800, Dong Jia wrote: > > > On Tue, 7 Jun 2016 19:39:21 -0600 > > > Alex Willia

Re: [Qemu-devel] [RFC PATCH v4 1/3] Mediated device Core driver

> > > > > > > > > From: Alex Williamson [mailto:alex.william...@redhat.com] > > > > > > Sent: Tuesday, June 07, 2016 3:31 AM > > > > > > > > > > > > On Mon, 6 Jun 2016 10:44:25 -0700 > > > > &

Re: [Qemu-devel] [RFC PATCH v4 1/3] Mediated device Core driver

On Mon, Jun 06, 2016 at 04:29:11PM +0800, Dong Jia wrote: > On Sun, 5 Jun 2016 23:27:42 -0700 > Neo Jia <c...@nvidia.com> wrote: > > 2. VFIO_DEVICE_CCW_CMD_REQUEST > This intends to handle an intercepted channel I/O instruction. It > basically need to do the followi

Re: [Qemu-devel] [RFC PATCH v4 1/3] Mediated device Core driver

On Mon, Jun 06, 2016 at 02:01:48PM +0800, Dong Jia wrote: > On Mon, 6 Jun 2016 10:57:49 +0530 > Kirti Wankhede wrote: > > > > > > > On 6/3/2016 2:27 PM, Dong Jia wrote: > > > On Wed, 25 May 2016 01:28:15 +0530 > > > Kirti Wankhede wrote: > > > > >

Re: [Qemu-devel] [RFC PATCH v4 3/3] VFIO Type1 IOMMU: Add support for mediated devices

On Wed, Jun 01, 2016 at 04:40:19PM +0800, Dong Jia wrote: > On Wed, 25 May 2016 01:28:17 +0530 > Kirti Wankhede wrote: > > > + > > +/* > > + * Pin a set of guest PFNs and return their associated host PFNs for API > > + * supported domain only. > > + * @vaddr [in]: array of

Re: [Qemu-devel] [RFC PATCH v3 3/3] VFIO Type1 IOMMU change: to support with iommu and without iommu

On Fri, May 13, 2016 at 05:23:44PM +0800, Jike Song wrote: > On 05/13/2016 04:31 PM, Neo Jia wrote: > > On Fri, May 13, 2016 at 07:45:14AM +, Tian, Kevin wrote: > >> > >> We use page tracking framework, which is newly added to KVM recently, > >> to mark RAM

Re: [Qemu-devel] [RFC PATCH v3 3/3] VFIO Type1 IOMMU change: to support with iommu and without iommu

On Fri, May 13, 2016 at 05:46:17PM +0800, Jike Song wrote: > On 05/13/2016 04:12 AM, Neo Jia wrote: > > On Thu, May 12, 2016 at 01:05:52PM -0600, Alex Williamson wrote: > >> > >> If you're trying to equate the scale of what we need to track vs what > >

Re: [Qemu-devel] [RFC PATCH v3 3/3] VFIO Type1 IOMMU change: to support with iommu and without iommu

On Fri, May 13, 2016 at 04:39:37PM +0800, Dong Jia wrote: > On Fri, 13 May 2016 00:24:34 -0700 > Neo Jia <c...@nvidia.com> wrote: > > > On Fri, May 13, 2016 at 03:10:22PM +0800, Dong Jia wrote: > > > On Thu, 12 May 2016 13:05:52 -0600 > > > Alex Willia

Re: [Qemu-devel] [RFC PATCH v3 3/3] VFIO Type1 IOMMU change: to support with iommu and without iommu

On Fri, May 13, 2016 at 08:02:41AM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Friday, May 13, 2016 3:38 PM > > > > On Fri, May 13, 2016 at 07:13:44AM +, Tian, Kevin wrote: > > > > From: Neo Jia [mailto:c...@nvidia.com]

Re: [Qemu-devel] [RFC PATCH v3 3/3] VFIO Type1 IOMMU change: to support with iommu and without iommu

On Fri, May 13, 2016 at 07:45:14AM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Friday, May 13, 2016 3:42 PM > > > > On Fri, May 13, 2016 at 03:30:27PM +0800, Jike Song wrote: > > > On 05/13/2016 02:43 PM, Neo Jia wrote: > >

Re: [Qemu-devel] [RFC PATCH v3 3/3] VFIO Type1 IOMMU change: to support with iommu and without iommu

On Fri, May 13, 2016 at 03:30:27PM +0800, Jike Song wrote: > On 05/13/2016 02:43 PM, Neo Jia wrote: > > On Fri, May 13, 2016 at 02:22:37PM +0800, Jike Song wrote: > >> On 05/13/2016 10:41 AM, Tian, Kevin wrote: > >>>> From: Neo Jia [mailto:c...@nvidia.com] Sent: Fr

Re: [Qemu-devel] [RFC PATCH v3 3/3] VFIO Type1 IOMMU change: to support with iommu and without iommu

On Fri, May 13, 2016 at 07:13:44AM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Friday, May 13, 2016 2:42 PM > > > > > > > > > > We possibly have the same requirement from the mediate driver backend: > > > &g

Re: [Qemu-devel] [RFC PATCH v3 3/3] VFIO Type1 IOMMU change: to support with iommu and without iommu

gt; > > > From: Alex Williamson [mailto:alex.william...@redhat.com] > > > > Sent: Thursday, May 12, 2016 6:06 AM > > > > > > > > On Wed, 11 May 2016 17:15:15 +0800 > > > > Jike Song <jike.s...@intel.com> wrote: > > > &

Re: [Qemu-devel] [RFC PATCH v3 3/3] VFIO Type1 IOMMU change: to support with iommu and without iommu

On Fri, May 13, 2016 at 02:22:37PM +0800, Jike Song wrote: > On 05/13/2016 10:41 AM, Tian, Kevin wrote: > >> From: Neo Jia [mailto:c...@nvidia.com] > >> Sent: Friday, May 13, 2016 3:49 AM > >> > >>> > >>>> Perhaps one possibility would be

Re: [Qemu-devel] [RFC PATCH v3 3/3] VFIO Type1 IOMMU change: to support with iommu and without iommu

On Fri, May 13, 2016 at 02:08:36PM +0800, Jike Song wrote: > On 05/13/2016 03:49 AM, Neo Jia wrote: > > On Thu, May 12, 2016 at 12:11:00PM +0800, Jike Song wrote: > >> On Thu, May 12, 2016 at 6:06 AM, Alex Williamson > >> <alex.william...@redhat.com> wrote: > &g

Re: [Qemu-devel] [RFC PATCH v3 3/3] VFIO Type1 IOMMU change: to support with iommu and without iommu

6 AM > > > > > > On Wed, 11 May 2016 17:15:15 +0800 > > > Jike Song <jike.s...@intel.com> wrote: > > > > > > > On 05/11/2016 12:02 AM, Neo Jia wrote: > > > > > On Tue, May 10, 2016 at 03:52:27PM +0800, Jike Song wrote: >

Re: [Qemu-devel] [RFC PATCH v3 3/3] VFIO Type1 IOMMU change: to support with iommu and without iommu

On Thu, May 12, 2016 at 12:11:00PM +0800, Jike Song wrote: > On Thu, May 12, 2016 at 6:06 AM, Alex Williamson > <alex.william...@redhat.com> wrote: > > On Wed, 11 May 2016 17:15:15 +0800 > > Jike Song <jike.s...@intel.com> wrote: > > > >> On 05/11/201

Re: [Qemu-devel] [RFC PATCH v3 3/3] VFIO Type1 IOMMU change: to support with iommu and without iommu

On Tue, May 10, 2016 at 03:52:27PM +0800, Jike Song wrote: > On 05/05/2016 05:27 PM, Tian, Kevin wrote: > >> From: Song, Jike > >> > >> IIUC, an api-only domain is a VFIO domain *without* underlying IOMMU > >> hardware. It just, as you said in another mail, "rather than > >> programming them into

Re: [Qemu-devel] [PATCH RFC 0/8] basic vfio-ccw infrastructure

On Thu, May 05, 2016 at 01:19:45PM -0600, Alex Williamson wrote: > [cc +Intel,NVIDIA] > > On Thu, 5 May 2016 18:29:08 +0800 > Dong Jia wrote: > > > On Wed, 4 May 2016 13:26:53 -0600 > > Alex Williamson wrote: > > > > > On Wed, 4 May

Re: [Qemu-devel] [RFC PATCH v3 2/3] VFIO driver for vGPU device

On Thu, May 05, 2016 at 09:24:26AM +, Tian, Kevin wrote: > > From: Alex Williamson > > Sent: Thursday, May 05, 2016 1:06 AM > > > > > + > > > > > +static int vgpu_dev_mmio_fault(struct vm_area_struct *vma, struct > > > > > vm_fault > > *vmf) > > > > > +{ > > > > > + int ret = 0; > > > > >

Re: [Qemu-devel] [RFC PATCH v3 2/3] VFIO driver for vGPU device

On Wed, May 04, 2016 at 11:06:19AM -0600, Alex Williamson wrote: > On Wed, 4 May 2016 03:23:13 + > "Tian, Kevin" wrote: > > > > From: Alex Williamson [mailto:alex.william...@redhat.com] > > > Sent: Wednesday, May 04, 2016 6:43 AM > > > > + > > > > + if

Re: [Qemu-devel] [RFC PATCH v3 0/3] Add vGPU support

On Wed, May 04, 2016 at 01:05:36AM +, Tian, Kevin wrote: > > From: Kirti Wankhede > > Sent: Tuesday, May 03, 2016 2:41 AM > > > > This series adds vGPU support to v4.6 Linux host kernel. Purpose of this > > series > > is to provide a common interface for vGPU management that can be used > >

Re: [Qemu-devel] [RFC PATCH v2 3/3] VFIO: Type1 IOMMU mapping support for vGPU

On Fri, Mar 11, 2016 at 10:56:24AM -0700, Alex Williamson wrote: > On Fri, 11 Mar 2016 08:55:44 -0800 > Neo Jia <c...@nvidia.com> wrote: > > > > > Alex, what's your opinion on this? > > > > > > The sticky point is how vfio, which is only handling th

Re: [Qemu-devel] [RFC PATCH v2 3/3] VFIO: Type1 IOMMU mapping support for vGPU

On Fri, Mar 11, 2016 at 09:13:15AM -0700, Alex Williamson wrote: > On Fri, 11 Mar 2016 04:46:23 + > "Tian, Kevin" <kevin.t...@intel.com> wrote: > > > > From: Neo Jia [mailto:c...@nvidia.com] > > > Sent: Friday, March 11, 2016 12:20 PM > >

Re: [Qemu-devel] [RFC PATCH v2 3/3] VFIO: Type1 IOMMU mapping support for vGPU

On Fri, Mar 11, 2016 at 04:46:23AM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Friday, March 11, 2016 12:20 PM > > > > On Thu, Mar 10, 2016 at 11:10:10AM +0800, Jike Song wrote: > > > > > > >> Is it supposed t

Re: [Qemu-devel] [RFC PATCH v2 3/3] VFIO: Type1 IOMMU mapping support for vGPU

On Thu, Mar 10, 2016 at 11:10:10AM +0800, Jike Song wrote: > > >> Is it supposed to be the caller who should set > >> up IOMMU by DMA api such as dma_map_page(), after calling > >> vgpu_dma_do_translate()? > >> > > > > Don't think you need to call dma_map_page here. Once you have the pfn > >

Re: [Qemu-devel] [RFC PATCH v2 3/3] VFIO: Type1 IOMMU mapping support for vGPU

On Mon, Mar 07, 2016 at 02:07:15PM +0800, Jike Song wrote: > Hi Neo, > > On Fri, Mar 4, 2016 at 3:00 PM, Neo Jia <c...@nvidia.com> wrote: > > On Wed, Mar 02, 2016 at 04:38:34PM +0800, Jike Song wrote: > >> On 02/24/2016 12:24 AM, Kirti Wankhede wrote: > &g

Re: [Qemu-devel] [RFC PATCH v2 3/3] VFIO: Type1 IOMMU mapping support for vGPU

On Wed, Mar 02, 2016 at 04:38:34PM +0800, Jike Song wrote: > On 02/24/2016 12:24 AM, Kirti Wankhede wrote: > > + vgpu_dma->size = map->size; > > + > > + vgpu_link_dma(vgpu_iommu, vgpu_dma); > > Hi Kirti & Neo, > > seems that no one actually setup mappings for IOMMU here? > Hi Jike, Yes.

Re: [Qemu-devel] [RFC PATCH v2 1/3] vGPU Core driver

On Mon, Feb 29, 2016 at 05:39:02AM +, Tian, Kevin wrote: > > From: Kirti Wankhede > > Sent: Wednesday, February 24, 2016 12:24 AM > > > > Signed-off-by: Kirti Wankhede <kwankh...@nvidia.com> > > Signed-off-by: Neo Jia <c...@nvidia.com> > >

[Qemu-devel] [PATCH v2] replace fixed str limit by g_strdup_printf

A trivial change to remove string limit by using g_strdup_printf Tested-by: Neo Jia <c...@nvidia.com> Signed-off-by: Neo Jia <c...@nvidia.com> Signed-off-by: Kirti Wankhede <kwankh...@nvidia.com> --- hw/vfio/pci.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) di

[Qemu-devel] [PATCH] replace fixed str limit by g_strdup_printf

A trivial change to remove string limit by using g_strdup_printf and g_strconcat Tested-by: Neo Jia <c...@nvidia.com> Signed-off-by: Neo Jia <c...@nvidia.com> Signed-off-by: Kirti Wankhede <kwankh...@nvidia.com> --- hw/vfio/pci.c | 19 --- 1 file changed, 1

Re: [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide common interface for vGPU.

On Wed, Feb 17, 2016 at 02:08:18PM +0100, Gerd Hoffmann wrote: > Hi, > > > For example, how to locate the path of a given VM? > > You go ask libvirt, the domain xml will have the info. > > > Whoever is going to configure > > the qemu has to walk through *all* the current vgpu path to locate

Re: [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide common interface for vGPU.

On Wed, Feb 17, 2016 at 09:52:04AM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Wednesday, February 17, 2016 5:35 PM > > > > On Wed, Feb 17, 2016 at 08:57:08AM +, Tian, Kevin wrote: > > > > From: Neo Jia [mailto:c...

Re: [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide common interface for vGPU.

On Wed, Feb 17, 2016 at 08:57:08AM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Wednesday, February 17, 2016 3:55 PM > > 'whoever' is too strict here. I don't think UUID is required in all scenarios. > > In your scenario: > >

Re: [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide common interface for vGPU.

On Wed, Feb 17, 2016 at 07:51:12AM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Wednesday, February 17, 2016 3:32 PM > > > > On Wed, Feb 17, 2016 at 07:52:53AM +0100, Gerd Hoffmann wrote: > > > Hi, > > > > >

Re: [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide common interface for vGPU.

On Wed, Feb 17, 2016 at 07:46:15AM +, Tian, Kevin wrote: > > From: Neo Jia > > Sent: Wednesday, February 17, 2016 3:26 PM > > > > > > > > > If your most concern is having this kind of path doesn't provide enough > > information of the virtual de

Re: [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide common interface for vGPU.

On Wed, Feb 17, 2016 at 07:52:53AM +0100, Gerd Hoffmann wrote: > Hi, > > > The answer is simple, having a UUID as part of the device name will give > > you a > > unique sysfs path that will be opened by QEMU. > > A descriptive name will work too, and I think it'll be easier to make > those

Re: [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide common interface for vGPU.

On Wed, Feb 17, 2016 at 06:02:36AM +, Tian, Kevin wrote: > > From: Neo Jia > > Sent: Wednesday, February 17, 2016 1:38 PM > > > > > > > > > > > > > > > > > > Hi Kevin, > > > > > > > > The answer is simp

Re: [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide common interface for vGPU.

On Tue, Feb 16, 2016 at 10:09:43PM -0700, Eric Blake wrote: > * PGP Signed by an unknown key > > On 02/16/2016 10:04 PM, Tian, Kevin wrote: > > > ...rather than making readers scroll through 16k bytes of repetitions of > the same things they saw earlier in the thread, but getting worse with >

Re: [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide common interface for vGPU.

On Wed, Feb 17, 2016 at 05:04:31AM +, Tian, Kevin wrote: > > From: Neo Jia > > Sent: Wednesday, February 17, 2016 12:18 PM > > > > On Wed, Feb 17, 2016 at 03:31:24AM +, Tian, Kevin wrote: > > > > From: Neo Jia [mailto:c...@nvidia.com] > > &g

Re: [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide common interface for vGPU.

On Wed, Feb 17, 2016 at 03:31:24AM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Tuesday, February 16, 2016 4:49 PM > > > > On Tue, Feb 16, 2016 at 08:10:42AM +, Tian, Kevin wrote: > > > > From: Neo Jia [mailto:c...@nvidia.

Re: [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide common interface for vGPU.

On Tue, Feb 16, 2016 at 08:10:42AM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Tuesday, February 16, 2016 3:53 PM > > > > On Tue, Feb 16, 2016 at 07:40:47AM +, Tian, Kevin wrote: > > > > From: Neo Jia [mailto:c...@nvidia.

Re: [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide common interface for vGPU.

On Tue, Feb 16, 2016 at 07:40:47AM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Tuesday, February 16, 2016 3:37 PM > > > > On Tue, Feb 16, 2016 at 07:27:09AM +, Tian, Kevin wrote: > > > > From: Neo Jia [mailto:c...@nvidia.

Re: [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide common interface for vGPU.

On Tue, Feb 16, 2016 at 07:27:09AM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Tuesday, February 16, 2016 3:13 PM > > > > On Tue, Feb 16, 2016 at 06:49:30AM +, Tian, Kevin wrote: > > > > From: Alex Williamson [mailto:alex

Re: [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide common interface for vGPU.

On Tue, Feb 16, 2016 at 06:49:30AM +, Tian, Kevin wrote: > > From: Alex Williamson [mailto:alex.william...@redhat.com] > > Sent: Thursday, February 04, 2016 3:33 AM > > > > On Wed, 2016-02-03 at 09:28 +0100, Gerd Hoffmann wrote: > > >   Hi, > > > > > > > Actually I have a long puzzle in this

Re: [Qemu-devel] RE: [iGVT-g] VFIO based vGPU(was Re: [Announcement] 2015-Q3 release of XenGT - a Mediated ...)

On Wed, Feb 03, 2016 at 08:04:16AM +, Tian, Kevin wrote: > > From: Zhiyuan Lv > > Sent: Tuesday, February 02, 2016 3:35 PM > > > > Hi Gerd/Alex, > > > > On Mon, Feb 01, 2016 at 02:44:55PM -0700, Alex Williamson wrote: > > > On Mon, 2016-02-01 at 14:10 +0100, Gerd Hoffmann wrote: > > > >  

Re: [Qemu-devel] [iGVT-g] RE: VFIO based vGPU(was Re: [Announcement] 2015-Q3 release of XenGT - a Mediated ...)

On Thu, Feb 04, 2016 at 03:01:36AM +, Tian, Kevin wrote: > > From: Alex Williamson [mailto:alex.william...@redhat.com] > > Sent: Thursday, February 04, 2016 4:45 AM > > > > > > First, Jike told me before his vacation, that we cannot do any change to > > > KVM module according to community

Re: [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide common interface for vGPU.

On Tue, Feb 02, 2016 at 09:00:43AM +0100, Gerd Hoffmann wrote: > Hi, > > > And for UUID, I remember Alex had a concern on using it in kernel. > > Honestly speaking I don't have a good idea here. In Xen side there is a VM > > ID > > which can be easily used as the index. But for KVM, what

Re: [Qemu-devel] [RFC PATCH v1 1/1] vGPU core driver : to provide common interface for vGPU.

On Tue, Feb 02, 2016 at 08:18:44AM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Tuesday, February 02, 2016 4:13 PM > > > > On Tue, Feb 02, 2016 at 09:00:43AM +0100, Gerd Hoffmann wrote: > > > Hi, > > > > >

Re: [Qemu-devel] VFIO based vGPU(was Re: [Announcement] 2015-Q3 release of XenGT - a Mediated ...)

On Wed, Jan 27, 2016 at 09:10:16AM -0700, Alex Williamson wrote: > On Wed, 2016-01-27 at 01:14 -0800, Neo Jia wrote: > > On Tue, Jan 26, 2016 at 04:30:38PM -0700, Alex Williamson wrote: > > > On Tue, 2016-01-26 at 14:28 -0800, Neo Jia wrote: > > > > On Tue, Jan 26,

Re: [Qemu-devel] VFIO based vGPU(was Re: [Announcement] 2015-Q3 release of XenGT - a Mediated ...)

On Tue, Jan 26, 2016 at 04:30:38PM -0700, Alex Williamson wrote: > On Tue, 2016-01-26 at 14:28 -0800, Neo Jia wrote: > > On Tue, Jan 26, 2016 at 01:06:13PM -0700, Alex Williamson wrote: > > > > 1.1 Under per-

Re: [Qemu-devel] VFIO based vGPU(was Re: [Announcement] 2015-Q3 release of XenGT - a Mediated ...)

ed: == 7.1 QEMU console VNC QEMU console VNC is not covered in this RFC as it is a pretty isolated module and not impacting the basic vGPU functionality, also we already have a good discussion about the new VFIO interf

Re: [Qemu-devel] VFIO based vGPU(was Re: [Announcement] 2015-Q3 release of XenGT - a Mediated ...)

ean up resource. Eventually, those virtual GPUs can be removed by writing to vgpu_destroy under device sysfs. 7. What is not covered: == 7.1 QEMU console VNC QEMU console VNC is not covered in this RFC as it is a pretty isolated module and not imp

Re: [Qemu-devel] VFIO based vGPU(was Re: [Announcement] 2015-Q3 release of XenGT - a Mediated ...)

On Tue, Jan 26, 2016 at 07:24:52PM +, Tian, Kevin wrote: > > From: Neo Jia [mailto:c...@nvidia.com] > > Sent: Tuesday, January 26, 2016 6:21 PM > > > > 0. High level overview > > = > >

Re: [Qemu-devel] VFIO based vGPU(was Re: [Announcement] 2015-Q3 release of XenGT - a Mediated ...)

On Tue, Jan 26, 2016 at 09:21:42PM +, Tian, Kevin wrote: > > From: Alex Williamson [mailto:alex.william...@redhat.com] > > Sent: Wednesday, January 27, 2016 12:37 AM > > > > On Tue, 2016-01-26 at 22:05 +0800, Yang Zhang wrote: > > > On 2016/1/26 15:41, Jike Song wrote: > > > > On 01/26/2016

Re: [Qemu-devel] VFIO based vGPU(was Re: [Announcement] 2015-Q3 release of XenGT - a Mediated ...)

On Tue, Jan 26, 2016 at 01:06:13PM -0700, Alex Williamson wrote: > On Tue, 2016-01-26 at 02:20 -0800, Neo Jia wrote: > > On Mon, Jan 25, 2016 at 09:45:14PM +, Tian, Kevin wrote: > > > > From: Alex Williamson [mailto:alex.william...@redhat.com] > >  > > Hi Alex

[Qemu-devel] Windows guest debugging on KVM/Qemu

hi, I am using KVM/Qemu to debug my Windows guest according to KVM wiki page (http://www.linux-kvm.org/page/WindowsGuestDrivers/GuestDebugging). It works for me and also I can only use one Windows guest and bind its serial port to a TCP port and run Virtual Serial Ports Emulator on my Windows dev

[Qemu-devel] Windows guest debugging on KVM/Qemu

hi, I am using KVM/Qemu to debug my Windows guest according to KVM wiki page (http://www.linux-kvm.org/page/WindowsGuestDrivers/GuestDebugging). It works for me and also I can only use one Windows guest and bind its serial port to a TCP port and run Virtual Serial Ports Emulator on my Windows dev

[Qemu-devel] Re: guest kernel debugging through serial port

Here is what I have asked before. The problem that I want to assign a real serial port to the guest is that the debugging through network becomes really slow. Thanks, Neo On Thu, Mar 11, 2010 at 2:44 AM, Neo Jia neo...@gmail.com wrote: hi, I have followed the windows guest debugging procedure

[Qemu-devel] guest kernel debugging through serial port

hi, I have followed the windows guest debugging procedure from http://www.linux-kvm.org/page/WindowsGuestDrivers/GuestDebugging. And it works when I start two guests and bind tcp port to guest serial port, but it is really slow. And if I use -serial /dev/ttyS1 for the guest debugging target, I

[Qemu-devel] Could not initialize SDL (kqemu)

hi, When I am trying to using kqemu on my IA32 linux, it throws out Could not initialize SDL -- exiting. Could you help me to figure it out? Thanks, Neo -- I would remember that if researchers were not ambitious probably today we haven't the technology we are using!

[Qemu-devel] How can qemu to generate a signal 0 on i386 target (Linux) and i386 host?

hi, I am using kgdb to debug Linux kernel. Both the target and host are IA32 platform. But I got the following from my gdb console: Program terminated with signal 0, Signal 0. The program no longer exists. In fact, this signal is not defined on my gdb. From the post

[Qemu-devel] Re: How to debug Linux kernel on qemu with kgdb?

On 4/25/07, Jan Kiszka [EMAIL PROTECTED] wrote: Neo Jia wrote: hi, I am trying to use debug kgdb patched linux kernel on my qemu. Both the native and target platform are IA32. I am wondering if there is anyone can show me the procedure? Yep, see https://mail.gna.org/public/xenomai-core

[Qemu-devel] Re: How to debug Linux kernel on qemu with kgdb?

On 4/25/07, Neo Jia [EMAIL PROTECTED] wrote: On 4/25/07, Jan Kiszka [EMAIL PROTECTED] wrote: Neo Jia wrote: hi, I am trying to use debug kgdb patched linux kernel on my qemu. Both the native and target platform are IA32. I am wondering if there is anyone can show me the procedure

[Qemu-devel] Re: How to debug Linux kernel on qemu with kgdb?

On 4/25/07, Jan Kiszka [EMAIL PROTECTED] wrote: Neo Jia wrote: On 4/25/07, Jan Kiszka [EMAIL PROTECTED] wrote: Neo Jia wrote: hi, I am trying to use debug kgdb patched linux kernel on my qemu. Both the native and target platform are IA32. I am wondering if there is anyone can show me

  1   2   >