On 20/11/17 14:58, Christoffer Dall wrote:
> On Thu, Nov 16, 2017 at 05:58:18PM +, Marc Zyngier wrote:
>> We miss a test against NULL after allocation.
>>
>> Fixes: 6d03a68f8054 ("KVM: arm64: vgic-its: Turn device_id validation into
>> generic ID validation")
>> Cc: sta...@vger.kernel.org # 4.
Hi james,
On 2017/11/16 2:25, James Morse wrote:
> What about 32bit? The register names and sizes are different. User-space would
> need a separate implementation to drive this. This is easier for the kernel
> to do
I agree with you that using different register names and sizes, such as 32 bit.
F
Christoffer Dall writes:
> Hi Alex,
>
> On Thu, Nov 16, 2017 at 03:39:18PM +, Alex Bennée wrote:
>> Hi,
>>
>> This is rev 3 of the series, practically the same than rev 2 but fixed
>> a return 1->0 in the kvm_run loop that Julien caught. I've added his
>> r-b tags to the other patches.
>>
>>
Christoffer Dall writes:
> Hi Alex,
>
> On Thu, Nov 16, 2017 at 03:39:18PM +, Alex Bennée wrote:
>> Hi,
>>
>> This is rev 3 of the series, practically the same than rev 2 but fixed
>> a return 1->0 in the kvm_run loop that Julien caught. I've added his
>> r-b tags to the other patches.
>>
>>
On 21/11/17 12:43, Alex Bennée wrote:
>
> Christoffer Dall writes:
>
>> Hi Alex,
>>
>> On Thu, Nov 16, 2017 at 03:39:18PM +, Alex Bennée wrote:
>>> Hi,
>>>
>>> This is rev 3 of the series, practically the same than rev 2 but fixed
>>> a return 1->0 in the kvm_run loop that Julien caught. I'v
Hi all,
SVE adds some new registers, and their size depends on the hardware ando
on runtime sysreg settings.
Before coding something, I'd like to get people's views on my current
approach here.
--8<--
New vcpu feature flag:
/*
* userspace can support regs up to at least 2048 bits in size via i
