From: Paolo Bonzini <pbonzini@redhat.com>
To: Jes.Sorensen@redhat.com
Cc: avi@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 5/7] Only export phys_mem create functions for !CONFIG_USER_ONLY builds
Date: Tue, 15 Jun 2010 15:35:21 +0200 [thread overview]
Message-ID: <4C178199.2070404@redhat.com> (raw)
In-Reply-To: <1276599879-22749-6-git-send-email-Jes.Sorensen@redhat.com>
On 06/15/2010 01:04 PM, Jes.Sorensen@redhat.com wrote:
> From: Jes Sorensen<Jes.Sorensen@redhat.com>
>
> Only export phys_mem create functions for !CONFIG_USER_ONLY builds
>
> Signed-off-by: Jes Sorensen<Jes.Sorensen@redhat.com>
> ---
> qemu-kvm.h | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/qemu-kvm.h b/qemu-kvm.h
> index 6f6c6d8..9adbc58 100644
> --- a/qemu-kvm.h
> +++ b/qemu-kvm.h
> @@ -812,6 +812,7 @@ void qemu_kvm_cpuid_on_env(CPUState *env);
> void kvm_inject_interrupt(CPUState *env, int mask);
> void kvm_update_after_sipi(CPUState *env);
> void kvm_update_interrupt_request(CPUState *env);
> +#ifndef CONFIG_USER_ONLY
> void *kvm_cpu_create_phys_mem(target_phys_addr_t start_addr, unsigned long size,
> int log, int writable);
>
> @@ -819,6 +820,7 @@ void kvm_cpu_destroy_phys_mem(target_phys_addr_t start_addr,
> unsigned long size);
> void kvm_qemu_log_memory(target_phys_addr_t start, target_phys_addr_t size,
> int log);
> +#endif
> int kvm_qemu_create_memory_alias(uint64_t phys_start, uint64_t len,
> uint64_t target_phys);
> int kvm_qemu_destroy_memory_alias(uint64_t phys_start);
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Paolo
next prev parent reply other threads:[~2010-06-15 13:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 11:04 [Qemu-devel] [PATCH 0/7] Fix building qemu-kvm for non KVM target Jes.Sorensen
2010-06-15 11:04 ` [Qemu-devel] [PATCH 1/7] Only call kvm_set_irqfd() if CONFIG_KVM is defined Jes.Sorensen
2010-06-15 13:31 ` [Qemu-devel] " Paolo Bonzini
2010-06-15 13:40 ` Jes Sorensen
2010-06-15 13:48 ` Paolo Bonzini
2010-06-15 14:58 ` Michael S. Tsirkin
2010-06-15 11:04 ` [Qemu-devel] [PATCH 2/7] No need for kvm_init() stub as already defined in qemu-kvm.h Jes.Sorensen
2010-06-15 13:34 ` [Qemu-devel] " Paolo Bonzini
2010-06-15 13:59 ` Jes Sorensen
2010-06-15 11:04 ` [Qemu-devel] [PATCH 3/7] time_drift_fix is x86 only, rather than !ia64 Jes.Sorensen
2010-06-15 11:04 ` [Qemu-devel] [PATCH 4/7] Build certain drivers for MIPS as well Jes.Sorensen
2010-06-15 11:04 ` [Qemu-devel] [PATCH 5/7] Only export phys_mem create functions for !CONFIG_USER_ONLY builds Jes.Sorensen
2010-06-15 13:35 ` Paolo Bonzini [this message]
2010-06-15 11:04 ` [Qemu-devel] [PATCH 6/7] Only treat KVM specific cmdline options for KVM enabled builds Jes.Sorensen
2010-06-15 11:04 ` [Qemu-devel] [PATCH 7/7] Only accept -no-hpet for i386 targets Jes.Sorensen
2010-06-15 12:20 ` [Qemu-devel] " Jan Kiszka
2010-06-15 12:28 ` Jes Sorensen
2010-06-15 12:37 ` Jan Kiszka
2010-06-15 12:44 ` Jes Sorensen
2010-06-15 13:38 ` Paolo Bonzini
2010-06-15 13:42 ` Jes Sorensen
2010-06-15 12:04 ` [Qemu-devel] Re: [PATCH 0/7] Fix building qemu-kvm for non KVM target Avi Kivity
2010-06-15 12:06 ` Avi Kivity
2010-06-15 12:10 ` Jes Sorensen
2010-06-15 13:42 ` Juan Quintela
2010-06-15 13:44 ` Jes Sorensen
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=4C178199.2070404@redhat.com \
--to=pbonzini@redhat.com \
--cc=Jes.Sorensen@redhat.com \
--cc=avi@redhat.com \
--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 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).