From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NJuwy-0001fj-2E
	for qemu-devel@nongnu.org; Sun, 13 Dec 2009 15:21:52 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NJuws-0001eS-IL
	for qemu-devel@nongnu.org; Sun, 13 Dec 2009 15:21:50 -0500
Received: from [199.232.76.173] (port=60740 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NJuws-0001eP-CD
	for qemu-devel@nongnu.org; Sun, 13 Dec 2009 15:21:46 -0500
Received: from mx1.redhat.com ([209.132.183.28]:63818)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <mst@redhat.com>) id 1NJuws-0005Hq-17
	for qemu-devel@nongnu.org; Sun, 13 Dec 2009 15:21:46 -0500
Date: Sun, 13 Dec 2009 22:19:00 +0200
From: "Michael S. Tsirkin" <mst@redhat.com>
Message-ID: <20091213201900.GA25658@redhat.com>
References: <20091213145132.GA11258@redhat.com>
	<B9955AD1-D8F0-4869-98DB-D3AA0DAD9F52@suse.de>
	<20091213190839.GA25519@redhat.com>
	<C8DBF98B-A337-4ED2-A24A-464FBFA31BA9@suse.de>
	<20091213195809.GA25615@redhat.com>
	<E566F484-9134-4EB4-AB72-992DB369D18F@suse.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E566F484-9134-4EB4-AB72-992DB369D18F@suse.de>
Subject: [Qemu-devel] Re: link failure with s390
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Alexander Graf <agraf@suse.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

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?

> 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.

-- 
MST