Hi Sjur,
On Thu, Dec 6, 2012 at 9:45 PM, Sjur Brændeland wrote:
> I just posted a RFC patch-set on this to linux-kernel@vger.kernel.org.
> Review comments is welcomed :-)
Great, will take a look, thanks a lot!
> I have run into one issue with the dynamically allocated notifyids. When
>
Hi Sjur,
On Thu, Dec 6, 2012 at 9:45 PM, Sjur Brændeland sjurb...@gmail.com wrote:
I just posted a RFC patch-set on this to linux-kernel@vger.kernel.org.
Review comments is welcomed :-)
Great, will take a look, thanks a lot!
I have run into one issue with the dynamically allocated notifyids.
Hi Ohad,
On Sat, Aug 11, 2012 at 2:34 PM, Ohad Ben-Cohen wrote:
> On Fri, Aug 10, 2012 at 6:30 PM, Ohad Ben-Cohen wrote:
>> This will solve all sort of open issues we have (or going to have soon):
>>
...
> 1. dynamically-allocated address of the vrings can be communicated
> 2. vdev statuses can
Hi Ohad,
On Sat, Aug 11, 2012 at 2:34 PM, Ohad Ben-Cohen o...@wizery.com wrote:
On Fri, Aug 10, 2012 at 6:30 PM, Ohad Ben-Cohen o...@wizery.com wrote:
This will solve all sort of open issues we have (or going to have soon):
...
1. dynamically-allocated address of the vrings can be
On Fri, Oct 19, 2012 at 3:45 PM, Sjur Brændeland wrote:
> Has anyone started looking into any of the open issues mentioned above?
No - feel free to take a stab at it.
Thanks,
Ohad.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Hi,
On Fri, Aug 10, 2012 at 5:30 PM, Ohad Ben-Cohen wrote:
> The general direction I have in mind is to put the resource table in
> its final location while we do the first pass of fw parsing.
>
> This will solve all sort of open issues we have (or going to have soon):
>
> 1.
Hi,
On Fri, Aug 10, 2012 at 5:30 PM, Ohad Ben-Cohen o...@wizery.com wrote:
The general direction I have in mind is to put the resource table in
its final location while we do the first pass of fw parsing.
This will solve all sort of open issues we have (or going to have soon):
1.
On Fri, Oct 19, 2012 at 3:45 PM, Sjur Brændeland sjurb...@gmail.com wrote:
Has anyone started looking into any of the open issues mentioned above?
No - feel free to take a stab at it.
Thanks,
Ohad.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
On Fri, Aug 10, 2012 at 6:30 PM, Ohad Ben-Cohen wrote:
> This will solve all sort of open issues we have (or going to have soon):
>
> 1. dynamically-allocated address of the vrings can be communicated
> 2. vdev statuses can be communicated
> 3. virtio config space will finally become
On Fri, Aug 10, 2012 at 6:30 PM, Ohad Ben-Cohen o...@wizery.com wrote:
This will solve all sort of open issues we have (or going to have soon):
1. dynamically-allocated address of the vrings can be communicated
2. vdev statuses can be communicated
3. virtio config space will finally become
Hi Sjur,
On Thu, Aug 9, 2012 at 11:35 PM, Sjur Brændeland wrote:
> Any thoughts on how to go about to fix this?
The general direction I have in mind is to put the resource table in
its final location while we do the first pass of fw parsing.
This will solve all sort of open issues we have (or
Hi Sjur,
On Thu, Aug 9, 2012 at 11:35 PM, Sjur Brændeland sjurb...@gmail.com wrote:
Any thoughts on how to go about to fix this?
The general direction I have in mind is to put the resource table in
its final location while we do the first pass of fw parsing.
This will solve all sort of open
Hi Ohad,
>> I realize that we have the same issue with the virtio rings.
>> Are there any way we can assign the device address of the virtio rings
>> to the resource table in shared memory?
>
> It's a gap we have today, but it should definitely be fixed.
Ok, good.
Any thoughts on how to go about
Hi Sjur,
On Wed, Aug 8, 2012 at 7:55 PM, Sjur Brændeland wrote:
> I realize that we have the same issue with the virtio rings.
> Are there any way we can assign the device address of the virtio rings
> to the resource table in shared memory?
It's a gap we have today, but it should definitely be
Hi Sjur,
On Wed, Aug 8, 2012 at 7:55 PM, Sjur Brændeland sjurb...@gmail.com wrote:
I realize that we have the same issue with the virtio rings.
Are there any way we can assign the device address of the virtio rings
to the resource table in shared memory?
It's a gap we have today, but it
Hi Ohad,
I realize that we have the same issue with the virtio rings.
Are there any way we can assign the device address of the virtio rings
to the resource table in shared memory?
It's a gap we have today, but it should definitely be fixed.
Ok, good.
Any thoughts on how to go about to fix
Hi Ohad,
> Carveout did not set device address when IOMMU is not supported.
> Fix this by assigning dma address to device address to carveout
> if IOMMU is not supported.
I realize that we have the same issue with the virtio rings.
Are there any way we can assign the device address of the virtio
Hi Ohad,
Carveout did not set device address when IOMMU is not supported.
Fix this by assigning dma address to device address to carveout
if IOMMU is not supported.
I realize that we have the same issue with the virtio rings.
Are there any way we can assign the device address of the virtio
On Mon, Jul 2, 2012 at 6:14 PM, Ohad Ben-Cohen wrote:
> On Mon, Jul 2, 2012 at 6:11 PM, Sjur BRENDELAND
> wrote:
>>> To simplify things, will the below work for you?
>>
>> Looks good, feel free to add my Acked-by
>
> Thanks! I'll queue it up for 3.6.
Applied.
--
To unsubscribe from this list:
On Mon, Jul 2, 2012 at 6:14 PM, Ohad Ben-Cohen o...@wizery.com wrote:
On Mon, Jul 2, 2012 at 6:11 PM, Sjur BRENDELAND
sjur.brandel...@stericsson.com wrote:
To simplify things, will the below work for you?
Looks good, feel free to add my Acked-by
Thanks! I'll queue it up for 3.6.
Applied.
20 matches
Mail list logo
