Re: [Qemu-devel] [PATCH qemu] spapr/target-ppc/kvm: Only add hcall-instructions if KVM supports it

2016-03-19 Thread Alexey Kardashevskiy
On 03/16/2016 05:04 PM, Thomas Huth wrote: On 16.03.2016 03:43, Alexey Kardashevskiy wrote: On 03/15/2016 10:32 PM, Thomas Huth wrote: On 15.03.2016 10:42, Alexey Kardashevskiy wrote: On 03/15/2016 07:18 PM, Thomas Huth wrote: Hi Alexey, On 15.03.2016 06:51, Alexey Kardashevskiy wrote:

Re: [Qemu-devel] [PATCH qemu] spapr/target-ppc/kvm: Only add hcall-instructions if KVM supports it

2016-03-16 Thread Thomas Huth
On 16.03.2016 03:43, Alexey Kardashevskiy wrote: > On 03/15/2016 10:32 PM, Thomas Huth wrote: >> On 15.03.2016 10:42, Alexey Kardashevskiy wrote: >>> On 03/15/2016 07:18 PM, Thomas Huth wrote: Hi Alexey, On 15.03.2016 06:51, Alexey Kardashevskiy wrote: > ePAPR defines

Re: [Qemu-devel] [PATCH qemu] spapr/target-ppc/kvm: Only add hcall-instructions if KVM supports it

2016-03-15 Thread Alexey Kardashevskiy
On 03/15/2016 10:32 PM, Thomas Huth wrote: On 15.03.2016 10:42, Alexey Kardashevskiy wrote: On 03/15/2016 07:18 PM, Thomas Huth wrote: Hi Alexey, On 15.03.2016 06:51, Alexey Kardashevskiy wrote: ePAPR defines "hcall-instructions" device-tree property which contains code to call

Re: [Qemu-devel] [PATCH qemu] spapr/target-ppc/kvm: Only add hcall-instructions if KVM supports it

2016-03-15 Thread Thomas Huth
On 15.03.2016 10:42, Alexey Kardashevskiy wrote: > On 03/15/2016 07:18 PM, Thomas Huth wrote: >> >> Hi Alexey, >> >> On 15.03.2016 06:51, Alexey Kardashevskiy wrote: >>> ePAPR defines "hcall-instructions" device-tree property which contains >>> code to call hypercalls in ePAPR paravirtualized

Re: [Qemu-devel] [PATCH qemu] spapr/target-ppc/kvm: Only add hcall-instructions if KVM supports it

2016-03-15 Thread David Gibson
On Tue, Mar 15, 2016 at 08:42:05PM +1100, Alexey Kardashevskiy wrote: > On 03/15/2016 07:18 PM, Thomas Huth wrote: > > > > Hi Alexey, > > > >On 15.03.2016 06:51, Alexey Kardashevskiy wrote: > >>ePAPR defines "hcall-instructions" device-tree property which contains > >>code to call hypercalls in

Re: [Qemu-devel] [PATCH qemu] spapr/target-ppc/kvm: Only add hcall-instructions if KVM supports it

2016-03-15 Thread Alexey Kardashevskiy
On 03/15/2016 09:19 PM, Alexander Graf wrote: On 15.03.16 06:51, Alexey Kardashevskiy wrote: ePAPR defines "hcall-instructions" device-tree property which contains code to call hypercalls in ePAPR paravirtualized guests. However this property is also present for pseries guests where it does

Re: [Qemu-devel] [PATCH qemu] spapr/target-ppc/kvm: Only add hcall-instructions if KVM supports it

2016-03-15 Thread Alexey Kardashevskiy
On 03/15/2016 08:59 PM, David Gibson wrote: On Tue, Mar 15, 2016 at 04:51:20PM +1100, Alexey Kardashevskiy wrote: ePAPR defines "hcall-instructions" device-tree property which contains code to call hypercalls in ePAPR paravirtualized guests. However this property is also present for pseries

Re: [Qemu-devel] [PATCH qemu] spapr/target-ppc/kvm: Only add hcall-instructions if KVM supports it

2016-03-15 Thread Alexander Graf
On 15.03.16 10:59, David Gibson wrote: > On Tue, Mar 15, 2016 at 04:51:20PM +1100, Alexey Kardashevskiy wrote: >> ePAPR defines "hcall-instructions" device-tree property which contains >> code to call hypercalls in ePAPR paravirtualized guests. However this >> property is also present for

Re: [Qemu-devel] [PATCH qemu] spapr/target-ppc/kvm: Only add hcall-instructions if KVM supports it

2016-03-15 Thread David Gibson
On Tue, Mar 15, 2016 at 04:51:20PM +1100, Alexey Kardashevskiy wrote: > ePAPR defines "hcall-instructions" device-tree property which contains > code to call hypercalls in ePAPR paravirtualized guests. However this > property is also present for pseries guests where it does not make sense, > even

Re: [Qemu-devel] [PATCH qemu] spapr/target-ppc/kvm: Only add hcall-instructions if KVM supports it

2016-03-15 Thread Alexander Graf
On 15.03.16 06:51, Alexey Kardashevskiy wrote: > ePAPR defines "hcall-instructions" device-tree property which contains > code to call hypercalls in ePAPR paravirtualized guests. However this > property is also present for pseries guests where it does not make sense, > even though it contains

Re: [Qemu-devel] [PATCH qemu] spapr/target-ppc/kvm: Only add hcall-instructions if KVM supports it

2016-03-15 Thread Alexey Kardashevskiy
On 03/15/2016 07:18 PM, Thomas Huth wrote: Hi Alexey, On 15.03.2016 06:51, Alexey Kardashevskiy wrote: ePAPR defines "hcall-instructions" device-tree property which contains code to call hypercalls in ePAPR paravirtualized guests. However this property is also present for pseries guests

Re: [Qemu-devel] [PATCH qemu] spapr/target-ppc/kvm: Only add hcall-instructions if KVM supports it

2016-03-15 Thread Thomas Huth
Hi Alexey, On 15.03.2016 06:51, Alexey Kardashevskiy wrote: > ePAPR defines "hcall-instructions" device-tree property which contains > code to call hypercalls in ePAPR paravirtualized guests. However this > property is also present for pseries guests where it does not make sense, > even though

[Qemu-devel] [PATCH qemu] spapr/target-ppc/kvm: Only add hcall-instructions if KVM supports it

2016-03-14 Thread Alexey Kardashevskiy
ePAPR defines "hcall-instructions" device-tree property which contains code to call hypercalls in ePAPR paravirtualized guests. However this property is also present for pseries guests where it does not make sense, even though it contains dummy code which simply fails. Instead of maintaining the