From: James Hogan
Date: Mon, 17 Dec 2012 09:51:04 +
> On 10/12/12 12:55, Geert Uytterhoeven wrote:
>> On Mon, Dec 10, 2012 at 11:22 AM, James Hogan wrote:
>>> On 08/12/12 03:43, H. Peter Anvin wrote:
On 12/05/2012 08:08 AM, James Hogan wrote:
> On 64 bit architectures with no effici
On 10/12/12 12:55, Geert Uytterhoeven wrote:
> On Mon, Dec 10, 2012 at 11:22 AM, James Hogan wrote:
>> On 08/12/12 03:43, H. Peter Anvin wrote:
>>> On 12/05/2012 08:08 AM, James Hogan wrote:
On 64 bit architectures with no efficient unaligned access, taskstats
has to add some padding to
On Mon, Dec 10, 2012 at 11:22 AM, James Hogan wrote:
> On 08/12/12 03:43, H. Peter Anvin wrote:
>> On 12/05/2012 08:08 AM, James Hogan wrote:
>>> On 64 bit architectures with no efficient unaligned access, taskstats
>>> has to add some padding to a reply to prevent unaligned access warnings.
>>> H
On 08/12/12 03:43, H. Peter Anvin wrote:
> On 12/05/2012 08:08 AM, James Hogan wrote:
>> On 64 bit architectures with no efficient unaligned access, taskstats
>> has to add some padding to a reply to prevent unaligned access warnings.
>> However this also needs to apply to 32 bit architectures with
On 12/05/2012 08:08 AM, James Hogan wrote:
On 64 bit architectures with no efficient unaligned access, taskstats
has to add some padding to a reply to prevent unaligned access warnings.
However this also needs to apply to 32 bit architectures with 64 bit
struct alignment such as metag (which has
On 64 bit architectures with no efficient unaligned access, taskstats
has to add some padding to a reply to prevent unaligned access warnings.
However this also needs to apply to 32 bit architectures with 64 bit
struct alignment such as metag (which has 64 bit memory accesses).
This is solved by a
6 matches
Mail list logo
