linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org, linux-doc@vger.kernel.org,
	Alexey Kardashevskiy <aik@ozlabs.ru>,
	linux-kernel@vger.kernel.org, kvm-ppc@vger.kernel.org,
	Alexander Graf <agraf@suse.de>, Paul Mackerras <paulus@samba.org>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 02/10] KVM: PPC: reserve a capability number for multitce support
Date: Tue, 27 Aug 2013 17:35:05 +1000	[thread overview]
Message-ID: <1377588905.3819.115.camel@pasglop> (raw)
In-Reply-To: <20130827064114.GC22899@redhat.com>

On Tue, 2013-08-27 at 09:41 +0300, Gleb Natapov wrote:
> > Oh and Alexey mentions that there are two capabilities and you only
> > applied one :-)
> > 
> Another one is:
>  [PATCH v8] KVM: PPC: reserve a capability and ioctl numbers for
> realmode VFIO
> ?

Yes, thanks !

Cheers,
Ben.

  reply	other threads:[~2013-08-27  7:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-01  4:44 [PATCH 00/10 v7] KVM: PPC: IOMMU in-kernel handling Alexey Kardashevskiy
2013-08-01  4:44 ` [PATCH 01/10] hashtable: add hash_for_each_possible_rcu_notrace() Alexey Kardashevskiy
2013-08-01  4:44 ` [PATCH 02/10] KVM: PPC: reserve a capability number for multitce support Alexey Kardashevskiy
2013-08-14  0:51   ` Benjamin Herrenschmidt
2013-08-26 12:37     ` Gleb Natapov
2013-08-27  4:19       ` Benjamin Herrenschmidt
2013-08-27  4:22         ` Benjamin Herrenschmidt
2013-08-27  6:41           ` Gleb Natapov
2013-08-27  7:35             ` Benjamin Herrenschmidt [this message]
2013-08-27  6:40         ` Gleb Natapov
2013-08-27  7:34           ` Benjamin Herrenschmidt
2013-08-01  4:44 ` [PATCH 03/10] KVM: PPC: reserve a capability and ioctl numbers for realmode VFIO Alexey Kardashevskiy
2013-08-15  7:16   ` Alexander Graf
2013-08-15  7:22     ` Alexey Kardashevskiy
2013-08-15  7:24       ` Alexander Graf
2013-08-15  7:25         ` Alexander Graf
2013-08-15  7:42           ` Alexey Kardashevskiy
2013-08-15  7:43             ` Alexander Graf
2013-08-15  7:54               ` Alexey Kardashevskiy
2013-08-15  7:56                 ` Alexander Graf
2013-08-01  4:44 ` [PATCH 04/10] powerpc: Prepare to support kernel handling of IOMMU map/unmap Alexey Kardashevskiy
2013-08-01  4:44 ` [PATCH 05/10] powerpc: add real mode support for dma operations on powernv Alexey Kardashevskiy
2013-08-01  4:44 ` [PATCH 06/10] KVM: PPC: enable IOMMU_API for KVM_BOOK3S_64 permanently Alexey Kardashevskiy
2013-08-01  4:44 ` [PATCH 07/10] KVM: PPC: Add support for multiple-TCE hcalls Alexey Kardashevskiy
2013-08-01  4:44 ` [PATCH 08/10] powerpc/iommu: rework to support realmode Alexey Kardashevskiy
2013-08-01  4:44 ` [PATCH 09/10] KVM: PPC: Add support for IOMMU in-kernel handling Alexey Kardashevskiy
2013-08-01  4:44 ` [PATCH 10/10] KVM: PPC: Add hugepage " Alexey Kardashevskiy

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=1377588905.3819.115.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=gleb@redhat.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).