From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: link failure with s390
Date: Mon, 14 Dec 2009 00:13:02 +0200 [thread overview]
Message-ID: <20091213221302.GA26577@redhat.com> (raw)
In-Reply-To: <8E2A839B-F3EA-46E0-9E11-52117F47C5EA@suse.de>
On Sun, Dec 13, 2009 at 10:44:04PM +0100, Alexander Graf wrote:
>
> On 13.12.2009, at 21:19, Michael S. Tsirkin wrote:
>
> > On Sun, Dec 13, 2009 at 09:15:30PM +0100, Alexander Graf wrote:
> >>
> >> Am 13.12.2009 um 20:58 schrieb "Michael S. Tsirkin" <mst@redhat.com>:
> >>
> >>> On Sun, Dec 13, 2009 at 08:21:57PM +0100, Alexander Graf wrote:
> >>>>
> >>>> On 13.12.2009, at 20:08, Michael S. Tsirkin wrote:
> >>>>
> >>>>> On Sun, Dec 13, 2009 at 06:30:56PM +0100, Alexander Graf wrote:
> >>>>>>
> >>>>>> On 13.12.2009, at 15:51, Michael S. Tsirkin wrote:
> >>>>>>
> >>>>>>> s390-virtio-bus.o: In function `virtio_s390_notify':
> >>>>>>> /scm/qemu/hw/s390-virtio-bus.c:310: undefined reference to
> >>>>>>> `kvm_s390_virtio_irq'
> >>>>>>>
> >>>>>>
> >>>>>> Are you sure you're building with --enable-kvm?
> >>>>>
> >>>>> No, I did ./configure --taget-list=s390x-softmmu
> >>>>>
> >>>>>> Currently there's no emulation target for S390.
> >>>>>
> >>>>> So either configure should fail without --enable-kvm,
> >>>>> or better enable kvm by default.
> >>>>
> >>>> Well, that's why you have to explicitly do --target-list=s390-
> >>>> softmmu. I'd love to see S390 bumped to a normal qemu arch with both
> >>>> TCG and KVM backends. But for now we don't have that.
> >>>>
> >>>> But yeah, we should probably add some sort of detection to
> >>>> configure, so it fails when you're building S390 on non-S390 and w/o
> >>>> KVM :-).
> >>>>
> >>>>
> >>>> Alex
> >>>
> >>> By the way, where do you get kernel headers for s390
> >>> which are required to build with --enable-kvm?
> >>> Which distro ships them?
> >>
> >> Uh, that's just the normal kernel headers, right?
> >> SLE11 definitely does ship them.
> >
> > kvm has architecture specific defines, does it not?
>
> In files called the same on x86, just with a different asm link.
Exactly.
ls -l /usr/src/kernels/2.6.30.8-64.fc11.i586/include/asm lrwxrwxrwx 1 root root 7 2009-10-04 17:53
/usr/src/kernels/2.6.30.8-64.fc11.i586/include/asm -> asm-x86
so it won't find link for s390x.
> >
> >> Worst case you just install the kernel
> >> sources.
> >>
> >> Alex
> >>>
> >
> > kernel sources is the wrong things to use for qemu. qemu should use
> > exported sanitized sources.
>
> Same thing as on all other archs. What's your point here?
>
> Alex
Hmm. I'm just trying to understand how does build find kvm headers for
s390 since they are not linked to from asm. Possibly what happens is we just pick
a wrong arch and it kind of works most of the time?
anyway, with --enable-kvm I still get:
s390-virtio-bus.o: In function `virtio_s390_notify':
/scm/qemu/hw/s390-virtio-bus.c:310: undefined reference to
`kvm_s390_virtio_irq'
collect2: ld returned 1 exit status
???
--
MST
next prev parent reply other threads:[~2009-12-13 22:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 14:51 [Qemu-devel] link failure with s390 Michael S. Tsirkin
2009-12-13 17:30 ` [Qemu-devel] " Alexander Graf
2009-12-13 19:08 ` Michael S. Tsirkin
2009-12-13 19:21 ` Alexander Graf
2009-12-13 19:58 ` Michael S. Tsirkin
2009-12-13 20:15 ` Alexander Graf
2009-12-13 20:19 ` Michael S. Tsirkin
2009-12-13 21:44 ` Alexander Graf
2009-12-13 22:13 ` Michael S. Tsirkin [this message]
2009-12-13 22:19 ` Alexander Graf
2009-12-13 22:27 ` Michael S. Tsirkin
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=20091213221302.GA26577@redhat.com \
--to=mst@redhat.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.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.