From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH 02/03] qemu-kvm: add tcg-traget stub for ia64.
Date: Wed, 12 Aug 2009 11:46:08 +0000 [thread overview]
Message-ID: <4A82AB80.1070907@redhat.com> (raw)
In-Reply-To: <706158FABBBA044BAD4FE898A02E4BC201C04E63D3@pdsmsx503.ccr.corp.intel.com>
On 08/12/2009 07:00 AM, Zhang, Xiantao wrote:
> From 94b7ff3a596b43d82e26494484807f3de7eddd40 Mon Sep 17 00:00:00 2001
> From: Xiantao Zhang<xiantao.zhang@intel.com>
> Date: Wed, 5 Aug 2009 11:27:10 +0800
> Subject: [PATCH] qemu-kvm: add tcg-traget stub for ia64.
>
> Signed-off-by: Xiantao Zhang<xiantao.zhang@intel.com>
> ---
> tcg/ia64/tcg-target.c | 222 +++++++++++++++++++++++++++++++++++++++++++++++++
> tcg/ia64/tcg-target.h | 76 +++++++++++++++++
>
Anthony, what's the best way to upstream ia64 support?
- non-functional tcg?
- disable cpu emulation?
- new target type (user, system/softmmu, system/kvm)?
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-08-12 11:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 4:00 [PATCH 02/03] qemu-kvm: add tcg-traget stub for ia64 Zhang, Xiantao
2009-08-12 11:46 ` Avi Kivity [this message]
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=4A82AB80.1070907@redhat.com \
--to=avi@redhat.com \
--cc=kvm-ia64@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).