All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
	Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] spapr-iommu: extend SPAPR_TCE_TABLE class
Date: Fri, 14 Mar 2014 10:19:03 +1100	[thread overview]
Message-ID: <53223CE7.2010702@ozlabs.ru> (raw)
In-Reply-To: <5321FE01.3050708@suse.de>

On 03/14/2014 05:50 AM, Andreas Färber wrote:
> Am 13.03.2014 19:04, schrieb Mike Day:
>> On 20/11/13 16:39 +1100, Alexey Kardashevskiy wrote:
>>> This adds a put_tce() callback to the SPAPR TCE TABLE device class.
>>> The new callback allows to have different IOMMU types such as upcoming
>>> VFIO IOMMU and it will be used more by the upcoming Multi-TCE support.
>>>
>>> This reworks the H_PUT_TCE handler to make use of the new put_tce()
>>> callback.
>>>
>>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>> Reviewed-by: Mike Day <ncmike@ncultra.org>
> 
> Looks reasonable, but not needed for 2.0 unless a second implementation
> comes up.

Thanks! What is now? It goes to your ppc-next? Or Alex's ppc-next? I am
confused with recent activity in PPC field :)


> Reviewed-by: Andreas Färber <afaerber@suse.de>



-- 
Alexey

  reply	other threads:[~2014-03-13 23:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20  5:39 [Qemu-devel] [PATCH] spapr-iommu: extend SPAPR_TCE_TABLE class Alexey Kardashevskiy
2013-12-05  9:39 ` Alexey Kardashevskiy
2013-12-20  2:47   ` Alexey Kardashevskiy
2014-03-12  3:54     ` Alexey Kardashevskiy
2014-03-13 18:04 ` [Qemu-devel] " Mike Day
2014-03-13 18:50   ` Andreas Färber
2014-03-13 23:19     ` Alexey Kardashevskiy [this message]
2014-03-13 23:59       ` Alexander Graf

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=53223CE7.2010702@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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 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.