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 and never
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; it's meant to
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 operation doesn't allow
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 which can
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 location; it's
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, Amit Shah
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, 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
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 queues
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 operation
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 queues
11 matches
Mail list logo
