public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Paul Mackerras <paulus@samba.org>
Cc: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH 0/3] New PAPR hypercall plus individual hypercall enables, v2
Date: Sun, 01 Jun 2014 12:01:40 +0200	[thread overview]
Message-ID: <538AFA04.40504@suse.de> (raw)
In-Reply-To: <1401520869-29364-1-git-send-email-paulus@samba.org>


On 31.05.14 09:21, Paul Mackerras wrote:
> This patch series adds a way for userspace to control which PAPR
> hypercalls get handled by kernel handlers vs. being sent up to
> userspace, and then adds an implementation of a new hypercall,
> H_SET_MODE.
>
> This version makes the KVM_CAP_PPC_ENABLE_HCALL capability a VM
> capability rather than a vcpu capability, and checks that the hcall
> numbers in the default-enabled list have an in-kernel implementation.
>
> The series is against the queue branch of the kvm tree.  I would like
> these patches to go into 3.16 if possible.

Thanks, I like all the patches and I think we can manage to get them 
into 3.16. Please just resend patch 1/3 with fixed documentation :).


Alex

      parent reply	other threads:[~2014-06-01 10:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-31  7:21 [PATCH 0/3] New PAPR hypercall plus individual hypercall enables, v2 Paul Mackerras
2014-05-31  7:21 ` [PATCH 1/3] KVM: PPC: Book3S: Controls for in-kernel PAPR hypercall handling Paul Mackerras
2014-06-01  9:55   ` Alexander Graf
2014-05-31  7:21 ` [PATCH 2/3] KVM: PPC: Book3S: Allow only implemented hcalls to be enabled or disabled Paul Mackerras
2014-05-31  7:21 ` [PATCH 3/3] KVM: PPC: Book3S HV: Add H_SET_MODE hcall handling Paul Mackerras
2014-06-01 10:01 ` Alexander Graf [this message]

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=538AFA04.40504@suse.de \
    --to=agraf@suse.de \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=paulus@samba.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