[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100613065837.GA5623@liondog.tnic>
Date: Sun, 13 Jun 2010 08:58:37 +0200
From: Borislav Petkov <bp@...en8.de>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Paolo Giarrusso <p.giarrusso@...il.com>,
"H. Peter Anvin" <hpa@...or.com>,
Borislav Petkov <borislav.petkov@....com>,
Toralf Förster <toralf.foerster@....de>,
user-mode-linux-devel@...ts.sourceforge.net,
linux-kernel@...r.kernel.org, Jeff Dike <jdike@...toit.com>
Subject: Re: [uml-devel] [PATCH] x86, hweight: Fix UML boot crash
From: Geert Uytterhoeven <geert@...ux-m68k.org>
Date: Sat, Jun 12, 2010 at 08:37:39PM +0200
> > Cool :). However, according to Geert, this doesn't fix it:
> >
> > http://marc.info/?l=linux-kernel&m=127522065202435&w=2
> >
> > It could be related to the -mregparm being broken on 32-bit UML since
> > Geert's UML "guest" is 32-bit. However, even if we fix this, it won't
>
> No, guest and host are both x86_64.
Ok, maybe I don't understand UML - it's just that all address values in
the backtrace are 32-bit (e.g. RDX: 00000000ffff8aed, with the upper
8 bytes zeroed out) and I assumed that this is a 32-bit "guest" on a
64-bit host.
--
Regards/Gruss,
Boris.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists