WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: 2.6.28.7 domU: 32-bit emulation seems to be broken

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: 2.6.28.7 domU: 32-bit emulation seems to be broken
From: Sven Köhler <sven.koehler@xxxxxxxxx>
Date: Tue, 17 Mar 2009 15:08:58 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 17 Mar 2009 07:07:26 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type; bh=sDPyGxXgL8PJWXBS5rz3TT86j+eGDyTqDQa2hA8gVx0=; b=yEPljPB8Hj0sHbzBH21+XZbF7ODvE8bkCUlFgBTl96u0P1sJhdey9avLHip7BhTMSq aruSVnnDen8zGz79MfMlXdomlVPPuDd2+sRIhxmBTeZ7d1Hp0AwLK2GXs00AnuY8qhFL AEQY9jyOBMdQPkMOA8Bvq7YdOX9a16osJkxbU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type; b=X+Mo60vKozOAZVyETcZVEwD784xRfVU+IFZhyCyEhbFGyGdj4VF4DpZMrWIGd1WNbu k8WuNpHA4VAAxbM+hx2BMFe4h4TPI9GwXQGyGEVh6Z1WAuQuOwkEAogCfzFnISBhDk0A fMrWHYhrvYZTh22JGcbcoSu37Ict8LWrR9QlI=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49BED46C.2040906@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <gpe0vg$j67$1@xxxxxxxxxxxxx> <gpei6e$gcn$1@xxxxxxxxxxxxx> <49BAFC72.4040501@xxxxxxxx> <49BB0184.1020503@xxxxxxxx> <49BB6F4A.90000@xxxxxxxxx> <49BC2994.6040404@xxxxxxxx> <49BCF38B.3000507@xxxxxxxxx> <49BD2CCA.6070308@xxxxxxxx> <49BD3A87.3060403@xxxxxxxxx> <49BEB487.3090503@xxxxxxxx> <49BEB526.7060608@xxxxxxxx> <49BED2DE.7060203@xxxxxxxxx> <49BED46C.2040906@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.19 (X11/20090103)
Jeremy Fitzhardinge schrieb:
> Sven Köhler wrote:
>> Jeremy Fitzhardinge schrieb:
>>> Jeremy Fitzhardinge wrote:
>>>>
>>>> Do you have auditing enabled?
>>> (No)
>>
>> You answered yourself, right?
>> (yes, CONFIG_AUDIT is disabled)
>>
>> Can I supply you with any further information?
> 
> I need to find/set up an AMD system to try to repro it I think.  I think
> the problem is actually the return from the syscall, rather than the
> syscall entry itself.  What happens if you run the program under either
> strace or gdb?

The program just works:

# strace ./a.out
execve("./a.out", ["./a.out"], [/* 24 vars */]) = 0
[ Process PID=8968 runs in 32 bit mode. ]
uname({sys="Linux", node="xen-to1", ...}) = 0
brk(0)                                  = 0x80c3000
brk(0x80c3cb0)                          = 0x80c3cb0
set_thread_area(0xffa5182c)             = 0
brk(0x80e4cb0)                          = 0x80e4cb0
brk(0x80e5000)                          = 0x80e5000
fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xfffffffff7f51000
write(1, "Hallo Welt!\n"..., 12Hallo Welt!
)        = 12
exit_group(0)                           = ?

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>