On 06/05/18 13:30, Richard Biener wrote:
> On Mon, Jun 4, 2018 at 8:11 PM Laszlo Ersek wrote:
>>
>> Hi!
>>
>> Apologies if this isn't the right place for asking. For the problem
>> statement, I'll simply steal Ard's writeup [1]:
>>
>>&g
On 06/05/18 10:56, Ard Biesheuvel wrote:
> On 5 June 2018 at 10:54, Laszlo Ersek wrote:
>> On 06/05/18 10:23, Ard Biesheuvel wrote:
>>> On 5 June 2018 at 10:18, Ard Biesheuvel wrote:
>>>> On 5 June 2018 at 10:16, Laszlo Ersek wrote:
>>
>>>&g
On 06/05/18 10:23, Ard Biesheuvel wrote:
> On 5 June 2018 at 10:18, Ard Biesheuvel wrote:
>> On 5 June 2018 at 10:16, Laszlo Ersek wrote:
>>> To my understanding, Daniel has the opposite preference; namely, the
>>> above approach doesn't scale to a large and m
On 06/05/18 10:18, Ard Biesheuvel wrote:
> On 5 June 2018 at 10:16, Laszlo Ersek wrote:
>> On 06/05/18 08:04, Ard Biesheuvel wrote:
>>> On 4 June 2018 at 20:10, Laszlo Ersek wrote:
>>>> Hi!
>>>>
>>>> Apologies if this isn't the right pl
On 06/05/18 08:04, Ard Biesheuvel wrote:
> On 4 June 2018 at 20:10, Laszlo Ersek wrote:
>> Hi!
>>
>> Apologies if this isn't the right place for asking. For the problem
>> statement, I'll simply steal Ard's writeup [1]:
>>
>>> KVM on ARM
Hi!
Apologies if this isn't the right place for asking. For the problem
statement, I'll simply steal Ard's writeup [1]:
> KVM on ARM refuses to decode load/store instructions used to perform
> I/O to emulated devices, and instead relies on the exception syndrome
> information to describe the oper