public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlo Marcelo Arenas Belon <carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org>
To: "Zhang, Xiantao" <xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH] kvm/qemu: Fix ia64 build broken.
Date: Mon, 31 Dec 2007 19:27:24 -0600	[thread overview]
Message-ID: <20080101012724.GB25562@tapir> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDCB567F5-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>

On Fri, Dec 21, 2007 at 10:58:23PM +0800, Zhang, Xiantao wrote:
> Due to last merge with Qemu upstream, some interfaces are changed, and
> leads to build fail

kvm-58 as released doesn't build in ia64 either because of the tpr/vapic
changes that were done at release date as shown by :

gcc  -Wl,-G0 -Wl,-T,/house/cmarenas/kvm-58/qemu/ia64.ld -L
/house/cmarenas/kvm-58/qemu/../libkvm  -g -o qemu-system-ia64 vl.o osdep.o
monitor.o pci.o loader.o isa_mmio.o migration.o block-raw-posix.o lsi53c895a.o
usb-ohci.o eeprom93xx.o eepro100.o ne2000.o pcnet.o rtl8139.o hypercall.o
ide.o pckbd.o ps2.o vga.o sb16.o es1370.o dma.o fdc.o mc146818rtc.o serial.o
i8259.o ipf.o cirrus_vga.o parallel.o acpi.o piix_pci.o usb-uhci.o
/house/cmarenas/kvm-58/qemu/smbus_eeprom.o ../libqemu_common.a libqemu.a
/house/cmarenas/kvm-58/qemu/../libkvm/libkvm.a  -lm -lz -lkvm   -lrt -lpthread
-lutil
libqemu.a(kvm-tpr-opt.o): In function `kvm_tpr_opt_setup':
/house/cmarenas/kvm-58/qemu/kvm-tpr-opt.c:287: undefined reference to
`kvm_enable_tpr_access_reporting'
libqemu.a(kvm-tpr-opt.o): In function `enable_vapic':
/house/cmarenas/kvm-58/qemu/kvm-tpr-opt.c:221: undefined reference to
`kvm_enable_vapic'

Xiantao, are there any plans to merge into qemu all changes required to get
host/guest support for ia64?, if for nothing else that could help with
problems due to qemu merges.

Avi, how would you like patches to fix build issues in ia64 to be handled?,
should be expected that kvm releases build for ia64? is there any system that
could be used as part of a compile farm / testing for ia64?

if nothing is available hp's testdrive have some itanium systems that could be
used at least to validate the userspace part builds (as I did) :

  http://www.testdrive.hp.com/systems/itanium.shtml

Carlo

PS. there are more warnings and other issues in that build that the ones shown
above.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2008-01-01  1:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21 14:58 [PATCH] kvm/qemu: Fix ia64 build broken Zhang, Xiantao
     [not found] ` <42DFA526FC41B1429CE7279EF83C6BDCB567F5-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-12-21 17:52   ` Amit Shah
     [not found]     ` <200712212322.31805.amit.shah-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-21 18:08       ` Izik Eidus
     [not found]         ` <476C010E.1020606-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-12-21 18:25           ` Amit Shah
2007-12-22  5:00       ` Zhang, Xiantao
2007-12-22 20:25       ` Avi Kivity
     [not found]         ` <476D72D3.8010601-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-02 19:59           ` Hollis Blanchard
2008-01-02 20:32             ` Amit Shah
2007-12-22 20:15   ` Avi Kivity
2007-12-26  8:57   ` Akio Takebe
     [not found]     ` <B1C8479D552433takebe_akio-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2007-12-26  9:03       ` Zhang, Xiantao
2008-01-01  1:27   ` Carlo Marcelo Arenas Belon [this message]
2008-01-01  9:04     ` Avi Kivity
     [not found]       ` <477A0211.9020708-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-01 15:37         ` Zhang, Xiantao
     [not found]           ` <42DFA526FC41B1429CE7279EF83C6BDCBB7441-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2008-01-01 15:51             ` Avi Kivity
     [not found]               ` <477A6193.1080804-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-01 16:07                 ` Zhang, Xiantao
     [not found]                   ` <42DFA526FC41B1429CE7279EF83C6BDCBB7443-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2008-01-01 16:14                     ` Avi Kivity
2008-01-01 15:31     ` Zhang, Xiantao
2008-01-01 16:37     ` Avi Kivity
     [not found]       ` <477A6C43.5030301-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-01 19:49         ` Carlo Marcelo Arenas Belon
2008-01-02  9:22           ` Avi Kivity
     [not found] <20071222135553.1341211901C5@genesis.frugalware.org>
     [not found] ` <42DFA526FC41B1429CE7279EF83C6BDCBB743E-wq7ZOvIWXbMAbVU2wMM1CrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2008-01-06  1:06   ` Miklos Vajna
     [not found]     ` <20080106010600.GD29972-mNO0jnlB3V1KNP/gQ5GeZj64mgHaRSMb@public.gmane.org>
2008-01-06  1:53       ` Carlo Marcelo Arenas Belon
2008-01-10 12:44         ` Miklos Vajna

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=20080101012724.GB25562@tapir \
    --to=carenas-kledwsohozojb6fo7hg9ng@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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