>On Wed, Dec 05, 2018 at 09:15:51AM +0800, Peng Hao wrote:
>> Return 0 when there is enough kvm_mmu_memory_cache object.
>>
>> Signed-off-by: Peng Hao
>> ---
>> virt/kvm/arm/mmu.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/virt/kvm/arm/mmu.c b/virt/kvm/arm/mmu.c
>
>> >Hi,
>> >
>> >On Wed, Nov 21, 2018 at 04:56:54PM +0800, peng.h...@zte.com.cn wrote:
>> >> >On 19/11/2018 09:10, Mark Rutland wrote:
>> >> >> On Sat, Nov 17, 2018 at 10:58:37AM +0800, peng.h...@zte.com.cn wrote:
>> >> On 16/11/18 00:23, peng.h...@zte.com.cn wrote:
>> >> >> Hi,
>> >>
>Hi,
>
>On Wed, Nov 21, 2018 at 04:56:54PM +0800, peng.h...@zte.com.cn wrote:
>> >On 19/11/2018 09:10, Mark Rutland wrote:
>> >> On Sat, Nov 17, 2018 at 10:58:37AM +0800, peng.h...@zte.com.cn wrote:
>> On 16/11/18 00:23, peng.h...@zte.com.cn wrote:
>> >> Hi,
>> >>> When virtual machine
>On 19/11/2018 09:10, Mark Rutland wrote:
>> On Sat, Nov 17, 2018 at 10:58:37AM +0800, peng.h...@zte.com.cn wrote:
On 16/11/18 00:23, peng.h...@zte.com.cn wrote:
>> Hi,
>>> When virtual machine starts, hang up.
>>
>> I take it you mean the *guest* hangs? Because it doesn't get
>On 19/11/2018 09:10, Mark Rutland wrote:
>> On Sat, Nov 17, 2018 at 10:58:37AM +0800, peng.h...@zte.com.cn wrote:
On 16/11/18 00:23, peng.h...@zte.com.cn wrote:
>> Hi,
>>> When virtual machine starts, hang up.
>>
>> I take it you mean the *guest* hangs? Because it doesn't get
>On 16/11/18 00:23, peng.h...@zte.com.cn wrote:
>>> Hi,
When virtual machine starts, hang up.
>>>
>>> I take it you mean the *guest* hangs? Because it doesn't get a timer
>>> interrupt?
>>>
The kernel version of guest
is 4.16. Host support vgic_v3.
>>>
>>> Your host kernel is somethi
>>
>> When virtual machine starts, hang up. The kernel version of guest
>> is 4.16. Host support vgic_v3.
>> It was mainly due to the incorrect vgic_irq's(intid=27) group value
>> during injection interruption. when kvm_vgic_vcpu_init is called,
>> dist is not initialized at this time. Unable to ge
>Hi,
>> When virtual machine starts, hang up.
>
>I take it you mean the *guest* hangs? Because it doesn't get a timer
>interrupt?
>
>> The kernel version of guest
>> is 4.16. Host support vgic_v3.
>
>Your host kernel is something recent, I guess?
>
>> It was mainly due to the incorrect vgic_irq's(i
>Hi Peng,
>
>On 15/11/18 15:14, Peng Hao wrote:
>> When virtual machine starts, hang up. The kernel version of guest
>> is 4.16. Host support vgic_v3.
>
>I don't understand the issue here. the vgic_irq->group field does not
>exist in 4.16 (neither in the first nor the last version). Nor does the
>l
>On 24/03/18 00:42, Peng Hao wrote:
>> Add lpi debug info to vgic-stat.
>> The printed info like this:
>> SPI 287 0 0100 0 160 -1
>> LPI 8192 2 00010000 0 160 -1
>>
>> Signed-off-by: Peng Hao
>> ---
>> virt/kvm/arm/vgic/vgic-de
>On 23/03/18 10:36, Peng Hao wrote:
>> Add lpi debug info to vgic-stat.
>> the printed info like this:
>> SPI 287 0 0100 0 160 -1
>> LPI 8192 2 00010000 0 160 -1
>>
>> Signed-off-by: Peng Hao
>> ---
>> virt/kvm/arm/vgic/vgic-
>On Sat, 10 Mar 2018 03:23:18 +,
>peng hao wrote:
>> >> For emulation devices just like vga, keeping coherent dcache between
>> >> guest and host timely is needed.
>> >> Now the display of vnc-viewer will not update continuously and the
>> >> patch can fix up.
>> >>
>> >> Signed-off-by: Peng H
>On 09/03/18 22:15, Peng Hao wrote:
>> For emulation devices just like vga, keeping coherent dcache between
>> guest and host timely is needed.
>> Now the display of vnc-viewer will not update continuously and the
>> patch can fix up.
>>
>> Signed-off-by: Peng Hao
>> ---
>> virt/kvm/arm/mm
>On 09/03/18 22:15, Peng Hao wrote:
>> For emulation devices just like vga, keeping coherent dcache between
>> guest and host timely is needed.
>> Now the display of vnc-viewer will not update continuously and the
>> patch can fix up.
>>
>> Signed-off-by: Peng Hao
>> ---
>> virt/kvm/arm/mmu.c |
14 matches
Mail list logo
