From: Wei Liu <wei.liu2@citrix.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
QEMU Developers <qemu-devel@nongnu.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Qemu-devel] [PATCH RFC 0/5] Xen: introduce Xen PV target
Date: Fri, 24 Jan 2014 14:23:37 +0000 [thread overview]
Message-ID: <20140124142337.GH24675@zion.uk.xensource.com> (raw)
In-Reply-To: <CAFEAcA888Gr7hfq9M_x6Ue9Vt03TJKo5a_heYL_nfYXnL2Sn0g@mail.gmail.com>
On Thu, Jan 23, 2014 at 10:30:16PM +0000, Peter Maydell wrote:
> On 23 January 2014 22:16, Wei Liu <wei.liu2@citrix.com> wrote:
> > As promised I hacked a prototype based on Paolo's disable TCG series.
> > However I coded some stubs for TCG anyway. So this series in principle
> > should work with / without Paolo's series.
>
> I'm afraid I still think this is a terrible idea. "Xen" isn't a CPU, and
Thanks for being blunt. ;-)
> "the binary is smaller" isn't IMHO sufficient justification for breaking
> QEMU's basic structure of "target-* define target CPUs and we have
> a lot of compile time constants which are specific to a CPU which
> get defined there". How would you support a bigendian Xen CPU,
> just to pick one example of where this falls down?
>
I think about this deeper. From Xen's (and I speculate this applies to
other hardware assisted virtulization solution as well) PoV only the
native endianess is supported, does it make sense to have a
target-native thing?
Wei.
> thanks -- PMM
next prev parent reply other threads:[~2014-01-24 14:23 UTC|newest]
Thread overview: 19+ 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 ` [Qemu-devel] [PATCH RFC 1/5] xen: move Xen PV machine files to hw/xenpv Wei Liu
2014-01-23 22:16 ` [Qemu-devel] [PATCH RFC 2/5] xen: factor out common functions Wei Liu
2014-01-23 22:16 ` [Qemu-devel] [PATCH RFC 3/5] exec: guard Xen HVM hooks with CONFIG_XEN_I386 Wei Liu
2014-01-24 7:35 ` 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 ` [Qemu-devel] [PATCH RFC 5/5] xen: introduce xenpv-softmmu.mak Wei Liu
2014-01-24 7:38 ` Paolo Bonzini
2014-01-24 17:00 ` Wei Liu
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 [this message]
2014-01-24 14:38 ` Paolo Bonzini
2014-01-24 14:50 ` Wei Liu
2014-01-24 14:30 ` Paolo Bonzini
2014-01-24 14:35 ` Peter Maydell
2014-01-24 14:42 ` Paolo Bonzini
2014-01-24 14:56 ` Stefano Stabellini
2014-01-24 15:22 ` [Qemu-devel] [Xen-devel] " Ian Campbell
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=20140124142337.GH24675@zion.uk.xensource.com \
--to=wei.liu2@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).