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 th
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 the UUID to
> match the QEMU's VM UUID.
No. qemu simply uses the path it get pa
> From: Neo Jia [mailto:c...@nvidia.com]
> Sent: Wednesday, February 17, 2016 6:34 PM
>
> >
> > Qemu is not a kernel component. And UUID is OPTIONAL for Qemu.
> >
> > KVM is the kernel component. It doesn't use UUID at all. the relation
> > between
> > UUID and VM is fully maintained in user spac
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...@nvidia.com]
> > > > Sent: Wednesday, Februa
> 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...@nvidia.com]
> > > Sent: Wednesday, February 17, 2016 3:55 PM
> >
> > 'whoever' is too strict here. I don't think U
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:
>
> - You will pass VM UUID when creatin
> From: Neo Jia [mailto:c...@nvidia.com]
> Sent: Wednesday, February 17, 2016 4:41 PM
>
> 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,
> From: Neo Jia [mailto:c...@nvidia.com]
> Sent: Wednesday, February 17, 2016 3:55 PM
>
> 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 d
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,
> > >
> > > > The answer is simple, having a UUID as part of the
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 device, we can add more sysfs attributes within
> 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,
> >
> > > The answer is simple, having a UUID as part of the device name will give
> > > you a
> > > unique sysfs path that will be op
> From: Neo Jia
> Sent: Wednesday, February 17, 2016 3:26 PM
>
>
> >
> > Qemu doesn't need to know the relation between virtual/physical devices at
> > all. It's just a path regardless of how vgpu name is created (either with
> > your
> > UUID proposal or my descriptive string proposal)
>
> No,
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 nam
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 simple, having a UUID as part of the device name will
> > > > give you a
> > > > unique sysfs pa
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 names persistent because you don't have to store the uuids
somewhere to re-create the
> From: Neo Jia
> Sent: Wednesday, February 17, 2016 1:38 PM
> > > >
> > > >
> > >
> > > Hi Kevin,
> > >
> > > 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.
> > >
> > > vgpu-vendor-0 and vgpu-vendor-1 will
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
> ea
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]
> > > > Sent: Tuesday, February 16, 2016 4:49 PM
> > >
On 02/16/2016 10:04 PM, Tian, Kevin wrote:
>> From: Neo Jia
[meta-comment]
...
On Wed, 2016-02-03 at 09:28 +0100, Gerd Hoffmann wrote:
> Hi,
>
>> Actually I have a long puzzle in this area. Definitely libvirt
>> will
>> use
UUI
> 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]
> > > Sent: Tuesday, February 16, 2016 4:49 PM
> > >
> > > On Tue, Feb 16, 2016 at 08:10:42AM +, Tian, Kevin wrote:
> > >
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.com]
> > > > Sent: Tuesday, February 1
> 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.com]
> > > Sent: Tuesday, February 16, 2016 3:53 PM
> > >
> > > On Tue, Feb 16, 2016 at 07:40:47AM +, Tia
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.com]
> > > > Sent: Tuesday, February 1
> 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.com]
> > > Sent: Tuesday, February 16, 2016 3:37 PM
> > >
> > > On Tue, Feb 16, 2016 at 07:27:09AM +, Tia
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.com]
> > > > Sent: Tuesday, February 1
> 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.com]
> > > Sent: Tuesday, February 16, 2016 3:13 PM
> > >
> > > On Tue, Feb 16, 2016 at 06:49:30AM +, Tia
> 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.william...@redhat.com]
> > > Sent: Thursday, February 04, 2016 3:33 AM
> > >
> > > On Wed, 2016-02-03 at 09:
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.william...@redhat.com]
> > > > Sent:
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 a
> 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 area. Definitely libvirt will use
> > > UUID to
> > > mark a VM. And obviou
> From: Kirti Wankhede
> Sent: Wednesday, February 03, 2016 9:21 PM
>
>
> On 2/3/2016 11:26 AM, Tian, Kevin wrote:
> [...]
> > * @vgpu_create:Called to allocate basic resouces in graphics
> > * driver for a particular vgpu.
> > *
On Wed, 2016-02-03 at 09:28 +0100, Gerd Hoffmann wrote:
> Hi,
>
> > Actually I have a long puzzle in this area. Definitely libvirt will use
> > UUID to
> > mark a VM. And obviously UUID is not recorded within KVM. Then how does
> > libvirt talk to KVM based on UUID? It could be a good reference
On 2/3/2016 11:26 AM, Tian, Kevin wrote:
[...]
* @vgpu_create:Called to allocate basic resouces in graphics
* driver for a particular vgpu.
* @dev: physical pci device structure on which vgpu
*should b
Hi,
> Actually I have a long puzzle in this area. Definitely libvirt will use UUID
> to
> mark a VM. And obviously UUID is not recorded within KVM. Then how does
> libvirt talk to KVM based on UUID? It could be a good reference to this
> design.
libvirt keeps track which qemu instance belongs
> From: Kirti Wankhede
> Sent: Tuesday, February 02, 2016 5:25 PM
>
> On 2/2/2016 1:12 PM, Tian, Kevin wrote:
> >> From: Kirti Wankhede [mailto:kwankh...@nvidia.com]
> >> Sent: Tuesday, February 02, 2016 9:48 AM
> >>
> >> Resending this mail again, somehow my previous mail didn't reached every
> >
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Wednesday, February 03, 2016 1:11 AM
>
> On Tue, 2016-02-02 at 00:31 -0800, Neo Jia wrote:
> > On Tue, Feb 02, 2016 at 08:18:44AM +, Tian, Kevin wrote:
> > > > From: Neo Jia [mailto:c...@nvidia.com]
> > > > Sent: Tuesday, Febr
On Tue, 2016-02-02 at 00:31 -0800, Neo Jia wrote:
> 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,
> >
On 2/2/2016 1:12 PM, Tian, Kevin wrote:
From: Kirti Wankhede [mailto:kwankh...@nvidia.com]
Sent: Tuesday, February 02, 2016 9:48 AM
Resending this mail again, somehow my previous mail didn't reached every
to everyone's inbox.
On 2/2/2016 3:16 AM, Kirti Wankhede wrote:
Design for vGPU Driver:
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,
> > >
> > > > And for UUID, I remember Alex had a concern on using
On Di, 2016-02-02 at 00:13 -0800, Neo Jia wrote:
> 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
> > >
> 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,
> >
> > > 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 Xe
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 would
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 would be the best
> identifier to associate with a VM?
The vgpu code doesn't need
> From: Kirti Wankhede [mailto:kwankh...@nvidia.com]
> Sent: Tuesday, February 02, 2016 9:48 AM
>
> Resending this mail again, somehow my previous mail didn't reached every
> to everyone's inbox.
>
> On 2/2/2016 3:16 AM, Kirti Wankhede wrote:
> > Design for vGPU Driver:
> > Main purpose of vGPU d
Resending this mail again, somehow my previous mail didn't reached every
to everyone's inbox.
On 2/2/2016 3:16 AM, Kirti Wankhede wrote:
Design for vGPU Driver:
Main purpose of vGPU driver is to provide a common interface for vGPU
management that can be used by differnt GPU drivers.
This modul
45 matches
Mail list logo
