On Tue, Jul 28, 2015 at 08:23:04AM -0700, Andy Lutomirski wrote:
> On Tue, Jul 28, 2015 at 7:47 AM, Josh Poimboeuf wrote:
> > Paravirt thunk functions aren't aligned, which can impact performance
> > and is inconsistent with gcc-generated functions.
> >
> > Align them at 16-byte boundaries to be
On Tue, Jul 28, 2015 at 7:47 AM, Josh Poimboeuf wrote:
> Paravirt thunk functions aren't aligned, which can impact performance
> and is inconsistent with gcc-generated functions.
>
> Align them at 16-byte boundaries to be consistent with gcc functions.
IMO stackvalidate shouldn't warn about
Paravirt thunk functions aren't aligned, which can impact performance
and is inconsistent with gcc-generated functions.
Align them at 16-byte boundaries to be consistent with gcc functions.
Signed-off-by: Josh Poimboeuf
---
arch/x86/include/asm/paravirt.h | 1 +
1 file changed, 1 insertion(+)
On Tue, Jul 28, 2015 at 7:47 AM, Josh Poimboeuf jpoim...@redhat.com wrote:
Paravirt thunk functions aren't aligned, which can impact performance
and is inconsistent with gcc-generated functions.
Align them at 16-byte boundaries to be consistent with gcc functions.
IMO stackvalidate shouldn't
Paravirt thunk functions aren't aligned, which can impact performance
and is inconsistent with gcc-generated functions.
Align them at 16-byte boundaries to be consistent with gcc functions.
Signed-off-by: Josh Poimboeuf jpoim...@redhat.com
---
arch/x86/include/asm/paravirt.h | 1 +
1 file
On Tue, Jul 28, 2015 at 08:23:04AM -0700, Andy Lutomirski wrote:
On Tue, Jul 28, 2015 at 7:47 AM, Josh Poimboeuf jpoim...@redhat.com wrote:
Paravirt thunk functions aren't aligned, which can impact performance
and is inconsistent with gcc-generated functions.
Align them at 16-byte
6 matches
Mail list logo
