All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Doug Kwan (關振德)" <dougkwan@google.com>
Cc: Tom Musta <tommusta@gmail.com>, Riku Voipio <riku.voipio@iki.fi>,
	"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH 3/3] configure: Add new target ppc64el-linux-user
Date: Thu, 8 May 2014 16:56:40 +0100	[thread overview]
Message-ID: <CAFEAcA8Ms1VQcf1fYtN3O8JeoKFYSKXebLqNjdxWrxh4USM62A@mail.gmail.com> (raw)
In-Reply-To: <CAH9SEo44hN572KOSRkTfSfEJCivo_mMRAMSEcgY0pzQE04mkXw@mail.gmail.com>

On 8 May 2014 16:51, Doug Kwan (關振德) <dougkwan@google.com> wrote:
> On Thu, May 8, 2014 at 8:41 AM, Peter Maydell <peter.maydell@linaro.org>
> wrote:
>> 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.

> 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.

Do it the same way we support everything else that can
deal with two endianness settings -- handle the other
TARGET_ENDIAN case in the translator. This is pretty
straightforward with the new TCGMemOp TCG ops.

thanks
-- PMM

  reply	other threads:[~2014-05-08 15:57 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08  8:26 [Qemu-devel] [PATCH 0/3] Adding new user mode target ppc64el-linux-user Doug Kwan
2014-05-08  8:26 ` [Qemu-devel] [PATCH 1/3] linux-user: Handle ELFv2 PPC64 binaries in user mode Doug Kwan
2014-05-08  8:36   ` Alexander Graf
2014-05-08  8:43     ` Doug Kwan (關振德)
2014-05-08  8:45       ` Alexander Graf
2014-05-08 13:30       ` Ulrich Weigand
2014-05-08  8:26 ` [Qemu-devel] [PATCH 2/3] PPC: Allow little-endian " Doug Kwan
2014-05-08  8:39   ` Alexander Graf
2014-05-08  8:49     ` Doug Kwan (關振德)
2014-05-08  8:55       ` Alexander Graf
2014-05-08  9:05         ` Doug Kwan (關振德)
2014-05-08  9:11           ` Alexander Graf
2014-05-08  9:24             ` Doug Kwan (關振德)
2014-05-08 12:39     ` Peter Maydell
2014-05-08 12:44       ` Alexander Graf
2014-05-08  8:26 ` [Qemu-devel] [PATCH 3/3] configure: Add new target ppc64el-linux-user Doug Kwan
2014-05-08  8:41   ` Alexander Graf
2014-05-08  8:46     ` Doug Kwan (關振德)
2014-05-08  8:56       ` Alexander Graf
2014-05-08  9:09         ` Doug Kwan (關振德)
2014-05-08 12:18   ` Andreas Färber
2014-05-08 12:28     ` Peter Maydell
2014-05-08 12:45       ` Alexander Graf
2014-05-08 15:57       ` Doug Kwan (關振德)
2014-05-08 14:41   ` Tom Musta
2014-05-08 15:19     ` Doug Kwan (關振德)
2014-05-08 15:25       ` Peter Maydell
2014-05-08 15:32         ` Doug Kwan (關振德)
2014-05-08 15:41           ` Peter Maydell
2014-05-08 15:51             ` Doug Kwan (關振德)
2014-05-08 15:56               ` Peter Maydell [this message]
2014-05-08 15:39         ` Tom Musta
2014-05-08 15:43           ` Peter Maydell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFEAcA8Ms1VQcf1fYtN3O8JeoKFYSKXebLqNjdxWrxh4USM62A@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=agraf@suse.de \
    --cc=dougkwan@google.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=riku.voipio@iki.fi \
    --cc=tommusta@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.