On 11.11.2014 05:22, Ming Lei wrote:
> On Tue, Nov 11, 2014 at 11:24 AM, Ming Lei wrote:
>> On Mon, Nov 10, 2014 at 6:00 PM, alvise rigo
>> wrote:
>>> Hi Claudio,
>>>
>>> On Fri, Nov 7, 2014 at 4:40 PM, Claudio Fontana
>>> wrote:
Hi Alvise,
I now got to test the series for my
On Tue, Nov 11, 2014 at 11:24 AM, Ming Lei wrote:
> On Mon, Nov 10, 2014 at 6:00 PM, alvise rigo
> wrote:
>> Hi Claudio,
>>
>> On Fri, Nov 7, 2014 at 4:40 PM, Claudio Fontana
>> wrote:
>>>
>>> Hi Alvise,
>>>
>>> I now got to test the series for my use case, in particular to enable the
>>> ARM 64
On Mon, Nov 10, 2014 at 6:00 PM, alvise rigo
wrote:
> Hi Claudio,
>
> On Fri, Nov 7, 2014 at 4:40 PM, Claudio Fontana
> wrote:
>>
>> Hi Alvise,
>>
>> I now got to test the series for my use case, in particular to enable the
>> ARM 64bit OSv guest (OSv's devices come from pci + virtio).
>>
>> Coul
Hi Claudio,
On Fri, Nov 7, 2014 at 4:40 PM, Claudio Fontana
wrote:
>
> Hi Alvise,
>
> I now got to test the series for my use case, in particular to enable the
> ARM 64bit OSv guest (OSv's devices come from pci + virtio).
>
> Could you respin the series, possibly including also Rob's patches,
> a
Hi Alvise,
I now got to test the series for my use case, in particular to enable the
ARM 64bit OSv guest (OSv's devices come from pci + virtio).
Could you respin the series, possibly including also Rob's patches,
addressing the issues which have been raised before?
Thanks!
Claudio
On 11.07.20
On Wed, Nov 5, 2014 at 11:23 AM, Claudio Fontana
wrote:
> Hi Alvise,
Hi Claudio,
>
> On 11.07.2014 09:21, Alvise Rigo wrote:
>> This patch series is based on the previous work [1] and [2] by Rob
>> Herring and it tries to enhance this work on these points:
>
> do your patches need to be applied
Hi Alvise,
On 11.07.2014 09:21, Alvise Rigo wrote:
> This patch series is based on the previous work [1] and [2] by Rob
> Herring and it tries to enhance this work on these points:
do your patches need to be applied on top of Rob's?
I ask because I cannot see the patch "hw/arm/virt: Add generic
Hello Claudio,
Unfortunately I'm still not able to reproduce the problem.
I suspect though that the issue concerns the way the tests were conducted, so
I take this opportunity to ask Rob how many disks you used to test the initial
patch series.
I used something like:
-device lsi53c895a -drive if
On 11.07.2014 11:28, Alvise Rigo wrote:
> The kernel version is a very recent one: v3.16.0-rc1.
> Maybe you are right. I will test some older version to see if I'm able
> to reproduce the issue.
>
> Thank you,
> alvise
Any news on this?
I will be soon in the situation when I can start testing th
On Fri, Jul 11, 2014 at 4:28 AM, Alvise Rigo
wrote:
> The kernel version is a very recent one: v3.16.0-rc1.
> Maybe you are right. I will test some older version to see if I'm able
> to reproduce the issue.
BTW, the lsi driver has compile time option to use i/o or memory
accesses. I usually test
The kernel version is a very recent one: v3.16.0-rc1.
Maybe you are right. I will test some older version to see if I'm able
to reproduce the issue.
Thank you,
alvise
Il 11/07/2014 11:09, Peter Maydell ha scritto:
> On 11 July 2014 08:21, Alvise Rigo wrote:
>> This work has been tested attachin
On 11 July 2014 08:21, Alvise Rigo wrote:
> This work has been tested attaching several PCI devices to the mach-virt
> platform. The tested devices are: virtio-blk-pci, virtio-net-pci,
> lsi53c895a and pci-ohci (all attached at the same time).
> Even if the original work was not changed in its co
This patch series is based on the previous work [1] and [2] by Rob
Herring and it tries to enhance this work on these points:
- Some of the hardcoded values have been moved to an header file. This
header file is also used to share some device structures with the
mach-virt machine.
- The inter
13 matches
Mail list logo
