From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Wei Liu <wei.liu2@citrix.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH RFC 0/5] Xen: introduce Xen PV target
Date: Fri, 24 Jan 2014 15:42:21 +0100 [thread overview]
Message-ID: <52E27BCD.70303@redhat.com> (raw)
In-Reply-To: <CAFEAcA8NLu3-LZ9sMqwLPfBOeAMdXqoHXs1tCkkWp_Rxz5YLRg@mail.gmail.com>
Il 24/01/2014 15:35, Peter Maydell ha scritto:
>> > (1) decide that the Xen ring buffers are little-endian even on big-endian
>> > CPUs
>> >
>> > (2) communicate the endianness of the Xen ring buffers via Xenstore, just
>> > like we do for sizeof(long), and let the guest use either endianness on any
>> > architecture.
> You still have to make a choice about what you think
> TARGET_WORDS_BIGENDIAN should be, and it's still going
> to be wrong half the time and horribly confusing.
> I just think this is completely the wrong solution to
> the problem.
Theoretically the xenpv-softmmu machine shouldn't need any code that
depends on TARGET_WORDS_BIGENDIAN.
If we changed every #ifdef TARGET_WORDS_BIGENDIAN to if(), we could
compile it with "#define TARGET_WORDS_BIGENDIAN abort()".
Paolo
next prev parent reply other threads:[~2014-01-24 14:43 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 22:16 [Qemu-devel] [PATCH RFC 0/5] Xen: introduce Xen PV target Wei Liu
2014-01-23 22:16 ` Wei Liu
2014-01-23 22:16 ` [Qemu-devel] [PATCH RFC 1/5] xen: move Xen PV machine files to hw/xenpv Wei Liu
2014-01-23 22:16 ` Wei Liu
2014-01-23 22:16 ` [PATCH RFC 2/5] xen: factor out common functions Wei Liu
2014-01-23 22:16 ` [Qemu-devel] " Wei Liu
2014-01-23 22:16 ` [PATCH RFC 3/5] exec: guard Xen HVM hooks with CONFIG_XEN_I386 Wei Liu
2014-01-23 22:16 ` [Qemu-devel] " Wei Liu
2014-01-24 7:35 ` Paolo Bonzini
2014-01-24 7:35 ` [Qemu-devel] " Paolo Bonzini
2014-01-23 22:16 ` [Qemu-devel] [PATCH RFC 4/5] xen: implement Xen PV target Wei Liu
2014-01-23 22:16 ` Wei Liu
2014-01-23 22:16 ` [Qemu-devel] [PATCH RFC 5/5] xen: introduce xenpv-softmmu.mak Wei Liu
2014-01-23 22:16 ` Wei Liu
2014-01-24 7:38 ` [Qemu-devel] " Paolo Bonzini
2014-01-24 17:00 ` Wei Liu
2014-01-24 17:00 ` [Qemu-devel] " Wei Liu
2014-01-24 7:38 ` Paolo Bonzini
2014-01-23 22:30 ` [Qemu-devel] [PATCH RFC 0/5] Xen: introduce Xen PV target Peter Maydell
2014-01-24 14:23 ` Wei Liu
2014-01-24 14:23 ` [Qemu-devel] " Wei Liu
2014-01-24 14:38 ` Paolo Bonzini
2014-01-24 14:50 ` Wei Liu
2014-01-24 14:50 ` [Qemu-devel] " Wei Liu
2014-01-24 14:38 ` Paolo Bonzini
2014-01-24 14:30 ` Paolo Bonzini
2014-01-24 14:30 ` [Qemu-devel] " Paolo Bonzini
2014-01-24 14:35 ` Peter Maydell
2014-01-24 14:42 ` Paolo Bonzini
2014-01-24 14:42 ` Paolo Bonzini [this message]
2014-01-24 14:56 ` [Qemu-devel] " Stefano Stabellini
2014-01-24 15:22 ` Ian Campbell
2014-01-24 15:22 ` [Qemu-devel] [Xen-devel] " Ian Campbell
2014-01-24 14:56 ` Stefano Stabellini
2014-01-24 14:35 ` Peter Maydell
2014-01-23 22:30 ` Peter Maydell
2014-01-24 7:36 ` Paolo Bonzini
2014-01-24 7:36 ` [Qemu-devel] " Paolo Bonzini
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=52E27BCD.70303@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.