kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
Cc: kvm <kvm@vger.kernel.org>, Hollis Blanchard <hollisb@us.ibm.com>,
	Carsten Otte <cotte@de.ibm.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [PATCH] kvm: work around inability of older kvm modules to destroy memory regions
Date: Wed, 17 Dec 2008 14:26:20 +0200	[thread overview]
Message-ID: <4948EFEC.2020407@redhat.com> (raw)
In-Reply-To: <493FCD5A.7010308@linux.vnet.ibm.com>

Christian Ehrhardt wrote:
> Hi, this patch breaks all non x86 architectures as libkvm/libkvm-x86.c 
> has the only implementation of the alias functionality.
> Until now only qemu-kvm-x86 has called that functions, but since this 
> patch the generic qemu-kvm.c calls them which leads to unresolved 
> symbols for powerpc, s390 and surely ia64 too.
>
> Well we could insert stubs for these call, but when looking on the 
> kernel side x86 is also the only implementer of the 
> KVM_SET_MEMORY_ALIAS ioctl. Until more arch support that there is no 
> reason to create these functions for non-x86 in libkvm. Also the 
> assumptions which addresses must be aliased base on hardware specific 
> assumptions e.g. vga card -> arch specific too.
>
> For now I hold a no-op stub in my private queue to test powerpc, but 
> eventually this mechanism should be arch dependent and this 
> implementation x86 only.
> Avi could you modify your patch to work for the other arch's too ?

Your band aid should be fine.  Yes, it's ugly, but this will be in flux 
as we merge with upstream qemu.  Please resend it with a signoff.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2008-12-17 12:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20081209161057.DC28A25006D@cleopatra.tlv.redhat.com>
2008-12-10 14:08 ` [PATCH] kvm: work around inability of older kvm modules to destroy memory regions Christian Ehrhardt
2008-12-17 12:26   ` Avi Kivity [this message]
2008-12-17 13:09     ` Christian Ehrhardt
2008-12-17 13:19       ` Avi Kivity

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=4948EFEC.2020407@redhat.com \
    --to=avi@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cotte@de.ibm.com \
    --cc=ehrhardt@linux.vnet.ibm.com \
    --cc=hollisb@us.ibm.com \
    --cc=kvm@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 NNTP newsgroup(s).