From: Alexander Graf <agraf@suse.de>
To: kvm-ppc@vger.kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 2/3] KVM: Allow KVM_CHECK_EXTENSION on the vm fd
Date: Mon, 14 Jul 2014 17:16:50 +0000 [thread overview]
Message-ID: <53C41082.4010503@suse.de> (raw)
In-Reply-To: <1405357418-18125-3-git-send-email-agraf@suse.de>
On 14.07.14 19:03, Alexander Graf wrote:
> The KVM_CHECK_EXTENSION is only available on the kvm fd today. Unfortunately
> on PPC some of the capabilities change depending on the way a VM was created.
>
> So instead we need a way to expose capabilities as VM ioctl, so that we can
> see which VM type we're using (HV or PR). To enable this, add the
> KVM_CHECK_EXTENSION ioctl to our vm ioctl portfolio.
>
> Signed-off-by: Alexander Graf <agraf@suse.de>
Hrm, I guess this itself should also get a CAP :).
Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Graf <agraf@suse.de>
To: kvm-ppc@vger.kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 2/3] KVM: Allow KVM_CHECK_EXTENSION on the vm fd
Date: Mon, 14 Jul 2014 19:16:50 +0200 [thread overview]
Message-ID: <53C41082.4010503@suse.de> (raw)
In-Reply-To: <1405357418-18125-3-git-send-email-agraf@suse.de>
On 14.07.14 19:03, Alexander Graf wrote:
> The KVM_CHECK_EXTENSION is only available on the kvm fd today. Unfortunately
> on PPC some of the capabilities change depending on the way a VM was created.
>
> So instead we need a way to expose capabilities as VM ioctl, so that we can
> see which VM type we're using (HV or PR). To enable this, add the
> KVM_CHECK_EXTENSION ioctl to our vm ioctl portfolio.
>
> Signed-off-by: Alexander Graf <agraf@suse.de>
Hrm, I guess this itself should also get a CAP :).
Alex
next prev parent reply other threads:[~2014-07-14 17:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 17:03 [PATCH 0/3] KVM: Make KVM_CHECK_EXTENSION a VM ioctl Alexander Graf
2014-07-14 17:03 ` Alexander Graf
2014-07-14 17:03 ` [PATCH 1/3] KVM: Rename and add argument to check_extension Alexander Graf
2014-07-14 17:03 ` Alexander Graf
2014-07-14 17:03 ` [PATCH 2/3] KVM: Allow KVM_CHECK_EXTENSION on the vm fd Alexander Graf
2014-07-14 17:03 ` Alexander Graf
2014-07-14 17:16 ` Alexander Graf [this message]
2014-07-14 17:16 ` Alexander Graf
2014-07-14 18:18 ` [PATCH v2 " Alexander Graf
2014-07-14 18:18 ` Alexander Graf
2014-07-14 17:03 ` [PATCH 3/3] KVM: PPC: Book3S: Provide different CAPs based on HV or PR mode Alexander Graf
2014-07-14 17:03 ` Alexander Graf
2014-07-15 6:50 ` [PATCH 0/3] KVM: Make KVM_CHECK_EXTENSION a VM ioctl Cornelia Huck
2014-07-15 6:50 ` Cornelia Huck
2014-07-15 7:39 ` Alexander Graf
2014-07-15 7:39 ` Alexander Graf
2014-07-15 10:02 ` Paolo Bonzini
2014-07-15 10:02 ` Paolo Bonzini
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=53C41082.4010503@suse.de \
--to=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--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 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.