Re: find_vqs operation starting at arbitrary index

2009-06-02 Thread Michael S. Tsirkin
On Tue, Jun 02, 2009 at 10:39:16PM +0530, Amit Shah wrote: > On (Tue) Jun 02 2009 [19:32:27], Michael S. Tsirkin wrote: > > On Tue, Jun 02, 2009 at 08:53:07AM +0930, Rusty Russell wrote: > > > On Mon, 1 Jun 2009 05:33:48 pm Amit Shah wrote: > > > > Hello, > > > > > > > > The recent find_vqs operati

Re: find_vqs operation starting at arbitrary index

2009-06-02 Thread Amit Shah
On (Tue) Jun 02 2009 [19:32:27], Michael S. Tsirkin wrote: > On Tue, Jun 02, 2009 at 08:53:07AM +0930, Rusty Russell wrote: > > On Mon, 1 Jun 2009 05:33:48 pm Amit Shah wrote: > > > Hello, > > > > > > The recent find_vqs operation doesn't allow for a vq to be found at an > > > arbitrary location; i

Re: find_vqs operation starting at arbitrary index

2009-06-02 Thread Michael S. Tsirkin
On Tue, Jun 02, 2009 at 08:53:07AM +0930, Rusty Russell wrote: > On Mon, 1 Jun 2009 05:33:48 pm Amit Shah wrote: > > Hello, > > > > The recent find_vqs operation doesn't allow for a vq to be found at an > > arbitrary location; it's meant to be called once at startup to find all > > possible queues

Re: find_vqs operation starting at arbitrary index

2009-06-01 Thread Rusty Russell
On Mon, 1 Jun 2009 05:33:48 pm Amit Shah wrote: > Hello, > > The recent find_vqs operation doesn't allow for a vq to be found at an > arbitrary location; it's meant to be called once at startup to find all > possible queues and never called again. > > This doesn't work for devices which can have qu

Re: find_vqs operation starting at arbitrary index

2009-06-01 Thread Amit Shah
On (Mon) Jun 01 2009 [11:43:27], Michael S. Tsirkin wrote: > On Mon, Jun 01, 2009 at 02:05:10PM +0530, Amit Shah wrote: > > On (Mon) Jun 01 2009 [11:11:06], Michael S. Tsirkin wrote: > > > On Mon, Jun 01, 2009 at 01:33:48PM +0530, Amit Shah wrote: > > > > Hello, > > > > > > > > The recent find_vqs

Re: find_vqs operation starting at arbitrary index

2009-06-01 Thread Amit Shah
On (Mon) Jun 01 2009 [11:11:06], Michael S. Tsirkin wrote: > On Mon, Jun 01, 2009 at 01:33:48PM +0530, Amit Shah wrote: > > Hello, > > > > The recent find_vqs operation doesn't allow for a vq to be found at an > > arbitrary location; it's meant to be called once at startup to find all > > possible

find_vqs operation starting at arbitrary index

2009-06-01 Thread Amit Shah
Hello, The recent find_vqs operation doesn't allow for a vq to be found at an arbitrary location; it's meant to be called once at startup to find all possible queues and never called again. This doesn't work for devices which can have queues hot-plugged at run-time. This can be made to work by pa

Re: find_vqs operation starting at arbitrary index

2009-06-01 Thread Michael S. Tsirkin
On Mon, Jun 01, 2009 at 02:21:28PM +0530, Amit Shah wrote: > On (Mon) Jun 01 2009 [11:43:27], Michael S. Tsirkin wrote: > > On Mon, Jun 01, 2009 at 02:05:10PM +0530, Amit Shah wrote: > > > On (Mon) Jun 01 2009 [11:11:06], Michael S. Tsirkin wrote: > > > > On Mon, Jun 01, 2009 at 01:33:48PM +0530, A

Re: find_vqs operation starting at arbitrary index

2009-06-01 Thread Michael S. Tsirkin
On Mon, Jun 01, 2009 at 02:21:28PM +0530, Amit Shah wrote: > On (Mon) Jun 01 2009 [11:43:27], Michael S. Tsirkin wrote: > > On Mon, Jun 01, 2009 at 02:05:10PM +0530, Amit Shah wrote: > > > On (Mon) Jun 01 2009 [11:11:06], Michael S. Tsirkin wrote: > > > > On Mon, Jun 01, 2009 at 01:33:48PM +0530, A

Re: find_vqs operation starting at arbitrary index

2009-06-01 Thread Michael S. Tsirkin
On Mon, Jun 01, 2009 at 02:05:10PM +0530, Amit Shah wrote: > On (Mon) Jun 01 2009 [11:11:06], Michael S. Tsirkin wrote: > > On Mon, Jun 01, 2009 at 01:33:48PM +0530, Amit Shah wrote: > > > Hello, > > > > > > The recent find_vqs operation doesn't allow for a vq to be found at an > > > arbitrary loc

Re: find_vqs operation starting at arbitrary index

2009-06-01 Thread Michael S. Tsirkin
On Mon, Jun 01, 2009 at 01:33:48PM +0530, Amit Shah wrote: > Hello, > > The recent find_vqs operation doesn't allow for a vq to be found at an > arbitrary location; it's meant to be called once at startup to find all > possible queues and never called again. > > This doesn't work for devices whic