From: Jan Kiszka <jan.kiszka@web.de>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
kvm-ppc <kvm-ppc@vger.kernel.org>
Subject: [Qemu-devel] Re: [PATCH 1 of 2] kvm: Move KVM mp_state accessors to i386-specific code
Date: Mon, 09 Nov 2009 23:12:12 +0100 [thread overview]
Message-ID: <4AF893BC.2040507@web.de> (raw)
In-Reply-To: <204026d59328febd9789.1257800737@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2271 bytes --]
Hollis Blanchard wrote:
> Unbreaks PowerPC and S390 KVM builds.
What breaks precisely?
Note that KVM_GET/SET_MP_STATE are generic IOCTLs and supposed to be
shared with ia64 - one day. We could still move things back then, but
maybe we can handle the build issues already in place, specifically as
qemu-kvm is carrying this in generic code since ages.
Jan
>
> Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
>
> diff --git a/kvm-all.c b/kvm-all.c
> --- a/kvm-all.c
> +++ b/kvm-all.c
> @@ -207,26 +207,6 @@ err:
> return ret;
> }
>
> -int kvm_put_mp_state(CPUState *env)
> -{
> - struct kvm_mp_state mp_state = { .mp_state = env->mp_state };
> -
> - return kvm_vcpu_ioctl(env, KVM_SET_MP_STATE, &mp_state);
> -}
> -
> -int kvm_get_mp_state(CPUState *env)
> -{
> - struct kvm_mp_state mp_state;
> - int ret;
> -
> - ret = kvm_vcpu_ioctl(env, KVM_GET_MP_STATE, &mp_state);
> - if (ret < 0) {
> - return ret;
> - }
> - env->mp_state = mp_state.mp_state;
> - return 0;
> -}
> -
> /*
> * dirty pages logging control
> */
> diff --git a/kvm.h b/kvm.h
> --- a/kvm.h
> +++ b/kvm.h
> @@ -74,9 +74,6 @@ int kvm_vm_ioctl(KVMState *s, int type,
>
> int kvm_vcpu_ioctl(CPUState *env, int type, ...);
>
> -int kvm_get_mp_state(CPUState *env);
> -int kvm_put_mp_state(CPUState *env);
> -
> /* Arch specific hooks */
>
> int kvm_arch_post_run(CPUState *env, struct kvm_run *run);
> diff --git a/target-i386/kvm.c b/target-i386/kvm.c
> --- a/target-i386/kvm.c
> +++ b/target-i386/kvm.c
> @@ -659,6 +659,26 @@ static int kvm_get_msrs(CPUState *env)
> return 0;
> }
>
> +static int kvm_put_mp_state(CPUState *env)
> +{
> + struct kvm_mp_state mp_state = { .mp_state = env->mp_state };
> +
> + return kvm_vcpu_ioctl(env, KVM_SET_MP_STATE, &mp_state);
> +}
> +
> +static int kvm_get_mp_state(CPUState *env)
> +{
> + struct kvm_mp_state mp_state;
> + int ret;
> +
> + ret = kvm_vcpu_ioctl(env, KVM_GET_MP_STATE, &mp_state);
> + if (ret < 0) {
> + return ret;
> + }
> + env->mp_state = mp_state.mp_state;
> + return 0;
> +}
> +
> int kvm_arch_put_registers(CPUState *env)
> {
> int ret;
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-11-09 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 21:05 [Qemu-devel] [PATCH 0 of 2] Fix PowerPC KVM build breaks Hollis Blanchard
2009-11-09 21:05 ` [Qemu-devel] [PATCH 1 of 2] kvm: Move KVM mp_state accessors to i386-specific code Hollis Blanchard
2009-11-09 22:12 ` Jan Kiszka [this message]
2009-11-09 22:21 ` [Qemu-devel] " Alexander Graf
2009-11-09 22:23 ` Hollis Blanchard
2009-11-09 23:03 ` Jan Kiszka
2009-11-09 23:22 ` Anthony Liguori
2009-11-09 21:05 ` [Qemu-devel] [PATCH 2 of 2] kvm ppc: Remove unused label Hollis Blanchard
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=4AF893BC.2040507@web.de \
--to=jan.kiszka@web.de \
--cc=aliguori@us.ibm.com \
--cc=hollisb@us.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--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).