From: Paul Mackerras <paulus@samba.org>
To: Alexander Graf <agraf@suse.de>
Cc: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH 0/3] New PAPR hypercall plus individual hypercall enables, v3
Date: Wed, 25 Jun 2014 23:08:32 +0000 [thread overview]
Message-ID: <20140625230832.GA8289@iris.ozlabs.ibm.com> (raw)
In-Reply-To: <53AB4322.1080906@suse.de>
On Wed, Jun 25, 2014 at 11:46:10PM +0200, Alexander Graf wrote:
>
> On 02.06.14 03:02, Paul Mackerras wrote:
> >This patch series adds a way for userspace to control which sPAPR
> >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 updates the documentation in api.txt as requested.
> >
> >The series is against the queue branch of the kvm tree. I would like
> >these patches to go into 3.16 if possible.
>
> Thanks, applied to kvm-ppc-queue. I don't think there's a bug fix in here
> that would warrant them in 3.16 still :).
I agree. It would be good to get a stable assignment of the number
for KVM_CAP_PPC_ENABLE_HCALL so we can start getting the qemu patches
upstream, though.
Paul.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mackerras <paulus@samba.org>
To: Alexander Graf <agraf@suse.de>
Cc: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH 0/3] New PAPR hypercall plus individual hypercall enables, v3
Date: Thu, 26 Jun 2014 09:08:32 +1000 [thread overview]
Message-ID: <20140625230832.GA8289@iris.ozlabs.ibm.com> (raw)
In-Reply-To: <53AB4322.1080906@suse.de>
On Wed, Jun 25, 2014 at 11:46:10PM +0200, Alexander Graf wrote:
>
> On 02.06.14 03:02, Paul Mackerras wrote:
> >This patch series adds a way for userspace to control which sPAPR
> >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 updates the documentation in api.txt as requested.
> >
> >The series is against the queue branch of the kvm tree. I would like
> >these patches to go into 3.16 if possible.
>
> Thanks, applied to kvm-ppc-queue. I don't think there's a bug fix in here
> that would warrant them in 3.16 still :).
I agree. It would be good to get a stable assignment of the number
for KVM_CAP_PPC_ENABLE_HCALL so we can start getting the qemu patches
upstream, though.
Paul.
next prev parent reply other threads:[~2014-06-25 23:08 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 12:17 [PATCH 0/3] New PAPR hypercall plus individual hypercall enables Paul Mackerras
2014-05-26 12:17 ` Paul Mackerras
2014-05-26 12:17 ` [PATCH 1/3] KVM: PPC: Book3S: Controls for in-kernel PAPR hypercall handling Paul Mackerras
2014-05-26 12:17 ` Paul Mackerras
2014-05-28 13:27 ` Alexander Graf
2014-05-28 13:27 ` Alexander Graf
2014-05-29 5:27 ` Paul Mackerras
2014-05-29 5:27 ` Paul Mackerras
2014-05-29 6:35 ` Alexander Graf
2014-05-29 6:35 ` Alexander Graf
2014-05-26 12:17 ` [PATCH 2/3] KVM: PPC: Book3S: Allow only implemented hcalls to be enabled or disabled Paul Mackerras
2014-05-26 12:17 ` Paul Mackerras
2014-05-28 13:30 ` Alexander Graf
2014-05-28 13:30 ` Alexander Graf
2014-05-26 12:17 ` [PATCH 3/3] KVM: PPC: Book3S HV: Add H_SET_MODE hcall handling Paul Mackerras
2014-05-26 12:17 ` Paul Mackerras
2014-05-28 13:35 ` Alexander Graf
2014-05-28 13:35 ` Alexander Graf
2014-05-29 5:47 ` Michael Neuling
2014-05-29 5:47 ` Michael Neuling
2014-05-29 6:22 ` [PATCH v2 " Michael Neuling
2014-05-29 6:22 ` Michael Neuling
2014-05-29 7:18 ` Alexander Graf
2014-05-29 7:18 ` Alexander Graf
2014-05-29 7:45 ` powerpc/pseries: Use new defines when calling h_set_mode Michael Neuling
2014-05-29 7:45 ` Michael Neuling
2014-05-29 7:45 ` Michael Neuling
2014-05-29 21:27 ` Alexander Graf
2014-05-29 21:27 ` Alexander Graf
2014-05-29 21:27 ` Alexander Graf
2014-05-29 21:52 ` Benjamin Herrenschmidt
2014-05-29 21:52 ` Benjamin Herrenschmidt
2014-05-29 21:52 ` Benjamin Herrenschmidt
2014-05-30 7:44 ` Alexander Graf
2014-05-30 7:44 ` Alexander Graf
2014-05-30 7:44 ` Alexander Graf
2014-05-30 8:56 ` Michael Ellerman
2014-05-30 8:56 ` Michael Ellerman
2014-05-30 8:56 ` Michael Ellerman
2014-05-30 9:10 ` Michael Neuling
2014-05-30 9:10 ` Michael Neuling
2014-05-30 9:10 ` Michael Neuling
2014-05-30 9:13 ` Alexander Graf
2014-05-30 9:13 ` Alexander Graf
2014-05-30 9:13 ` Alexander Graf
2014-05-30 9:44 ` Michael Neuling
2014-05-30 9:44 ` Michael Neuling
2014-05-30 9:44 ` Alexander Graf
2014-05-30 9:44 ` Alexander Graf
2014-05-30 9:44 ` Alexander Graf
2014-05-31 7:21 ` [PATCH 0/3] New PAPR hypercall plus individual hypercall enables, v2 Paul Mackerras
2014-05-31 7:21 ` Paul Mackerras
2014-05-31 7:21 ` [PATCH 1/3] KVM: PPC: Book3S: Controls for in-kernel PAPR hypercall handling Paul Mackerras
2014-05-31 7:21 ` Paul Mackerras
2014-06-01 9:55 ` Alexander Graf
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 ` Paul Mackerras
2014-05-31 7:21 ` [PATCH 3/3] KVM: PPC: Book3S HV: Add H_SET_MODE hcall handling Paul Mackerras
2014-05-31 7:21 ` Paul Mackerras
2014-06-01 10:01 ` [PATCH 0/3] New PAPR hypercall plus individual hypercall enables, v2 Alexander Graf
2014-06-01 10:01 ` Alexander Graf
2014-06-02 1:02 ` [PATCH 0/3] New PAPR hypercall plus individual hypercall enables, v3 Paul Mackerras
2014-06-02 1:02 ` Paul Mackerras
2014-06-02 1:02 ` [PATCH 1/3] KVM: PPC: Book3S: Controls for in-kernel sPAPR hypercall handling Paul Mackerras
2014-06-02 1:02 ` Paul Mackerras
2014-06-02 1:03 ` [PATCH 2/3] KVM: PPC: Book3S: Allow only implemented hcalls to be enabled or disabled Paul Mackerras
2014-06-02 1:03 ` Paul Mackerras
2014-06-02 1:03 ` [PATCH 3/3] KVM: PPC: Book3S HV: Add H_SET_MODE hcall handling Paul Mackerras
2014-06-02 1:03 ` Paul Mackerras
2014-06-25 21:46 ` [PATCH 0/3] New PAPR hypercall plus individual hypercall enables, v3 Alexander Graf
2014-06-25 21:46 ` Alexander Graf
2014-06-25 23:08 ` Paul Mackerras [this message]
2014-06-25 23:08 ` Paul Mackerras
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=20140625230832.GA8289@iris.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=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.