On Fri, Jul 15, 2011 at 12:56 AM, Alexander Graf wrote:
>
>
>
>
> Am 14.07.2011 um 21:34 schrieb Blue Swirl :
>
>> Don't compile virtio.c in hwlib, it depends on memory accesses
>> performed in CPU endianness.
>>
>> Make loads and stores in CPU endianness unavailable to devices
>> and poison them
On 07/15/2011 10:02 PM, Blue Swirl wrote:
On Fri, Jul 15, 2011 at 12:56 AM, Alexander Graf wrote:
Am 14.07.2011 um 21:34 schrieb Blue Swirl:
Don't compile virtio.c in hwlib, it depends on memory accesses
performed in CPU endianness.
Make loads and stores in CPU endianness unavailable to d
On Fri, Jul 15, 2011 at 12:56 AM, Alexander Graf wrote:
>
>
>
>
> Am 14.07.2011 um 21:34 schrieb Blue Swirl :
>
>> Don't compile virtio.c in hwlib, it depends on memory accesses
>> performed in CPU endianness.
>>
>> Make loads and stores in CPU endianness unavailable to devices
>> and poison them
Am 14.07.2011 um 21:34 schrieb Blue Swirl :
> Don't compile virtio.c in hwlib, it depends on memory accesses
> performed in CPU endianness.
>
> Make loads and stores in CPU endianness unavailable to devices
> and poison them to avoid further bugs.
Very nice :). Couldn't test execute it, but: