[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 3/3] configure: Add new target ppc64el-linux-use

From: 關振德
Subject: Re: [Qemu-devel] [PATCH 3/3] configure: Add new target ppc64el-linux-user
Date: Thu, 8 May 2014 08:51:56 -0700

On Thu, May 8, 2014 at 8:41 AM, Peter Maydell <address@hidden> wrote:
On 8 May 2014 16:32, Doug Kwan (關振德) <address@hidden> wrote:
> What else needs to be fixed?

git grep ENDIAN linux-user is probably a good start on a list.

> I suspect that the user-mode linux kernel
> interface may also need some work but it worked well enough
> in practice for us to build glibc and run gcc testsuite.

The gcc testsuite is really not very much of a workout.
I recommend getting a chroot environment working and then
trying the LTP testsuite:

> Yes ELFv2 is a different ABI but it is not complete different
> from the old one.  A notable change is the
> removal of function descriptor.  That affect how the user mode start the
> first instruction and that is addressed in this set of patches.  It would
> also affect signal handling but user-mode signals do not work at all on
> PPC64 anyway and the parts that would be affected looks unimplemented.

Yes, but we need to actually implement signal handling at
some point, so we don't want to end up having to totally
redo the base support of ppc64le at that point.

The general approach linux-user takes is "one kernel
ABI to one QEMU binary". Maybe we could change that,
but would there be any benefit to it? I can't really
see one.

-- PMM

May I ask what you would suggest to support ppc64le then?  For signal handling, we can check the ELF header to see if we use a function descriptor or an entry for a signal handler when this is implemented for ppc64 in the future.  I don't understand the "redoing the base support" bit.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]