qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Auger Eric <eric.auger@redhat.com>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: Pavel Fedin <p.fedin@samsung.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Diana Craciun <diana.craciun@freescale.com>,
	Shlomo Pongratz <shlomo.pongratz@huawei.com>,
	Shlomo Pongratz <shlomopongratz@gmail.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Andrew Jones <drjones@redhat.com>,
	Bharat Bhushan <bharat.bhushan@nxp.com>
Subject: Re: [Qemu-devel] [RFC PATCH v3 0/5] vITS support
Date: Wed, 29 Jun 2016 08:45:54 +0200	[thread overview]
Message-ID: <1948c7f8-f1b9-6f87-d533-c02ab888f5cd@redhat.com> (raw)
In-Reply-To: <CAMJs5B9dWaahkTMyN=_ooo-sO1qqmE6=mjPGJOkB6VutSgAGwg@mail.gmail.com>

Hi Christoffer,

On 28/06/2016 10:25, Christoffer Dall wrote:
> On Tue, Jun 28, 2016 at 8:41 AM, Auger Eric <eric.auger@redhat.com> wrote:
>> Dear all,
>>
>> On 24/11/2015 11:13, Pavel Fedin wrote:
>>> This series introduces support for in-kernel GICv3 ITS emulation.
>>> It is based on kernel API which is not released yet, therefore i post
>>> it as an RFC.
>>>
>>> Kernel patch sets which implement this functionality are:
>>> - [PATCH v3 00/16] KVM: arm64: GICv3 ITS emulation
>>>   http://www.spinics.net/lists/kvm/msg121878.html
>>> - [PATCH v3 0/7] KVM: arm/arm64: gsi routing support
>>>   http://www.spinics.net/lists/kvm/msg119567.html
>>
>> For testing KVM/ARM gsi routing and KVM ARM PCIe/MSI passthrough with
>> GICv3 ITS I intend to work on the respin of this series. I now have
>> access to a host featuring GICv3 ITS. Does anyone currently work on this
>> topic or intend to do so in short term or can I proceed?
>>
> Linaro is not working on this feature yet, and we would be happy to
> see you pick up this work.
OK Thanks. Since I did not get any other replies I will proceed then.
Adding Bharat in cc since he is interested in that series too.

Best Regards

Eric
> 
> Thanks,
> -Christoffer
> 

      reply	other threads:[~2016-06-29  6:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24 10:13 [Qemu-devel] [RFC PATCH v3 0/5] vITS support Pavel Fedin
2015-11-24 10:13 ` [Qemu-devel] [RFC PATCH v3 1/5] hw/intc: Implement ITS base class Pavel Fedin
2015-11-27 15:35   ` Peter Maydell
2015-11-30  7:09     ` Pavel Fedin
2015-11-29  8:10   ` Shannon Zhao
2015-11-24 10:13 ` [Qemu-devel] [RFC PATCH v3 2/5] kernel: Add vGICv3 ITS definitions Pavel Fedin
2015-11-24 10:13 ` [Qemu-devel] [RFC PATCH v3 3/5] kvm_arm: Pass requester ID to MSI routing functions Pavel Fedin
2015-11-27 15:45   ` Peter Maydell
2015-11-30  6:41     ` Pavel Fedin
2015-11-24 10:13 ` [Qemu-devel] [RFC PATCH v3 4/5] kvm_arm: Implement support for ITS emulation by KVM Pavel Fedin
2015-11-27 15:47   ` Peter Maydell
2015-11-24 10:13 ` [Qemu-devel] [RFC PATCH v3 5/5] arm/virt: Add ITS to the virt board Pavel Fedin
2015-11-27 16:18   ` Peter Maydell
2015-11-28  3:55     ` Shannon Zhao
2016-06-28  6:41 ` [Qemu-devel] [RFC PATCH v3 0/5] vITS support Auger Eric
2016-06-28  8:25   ` Christoffer Dall
2016-06-29  6:45     ` Auger Eric [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=1948c7f8-f1b9-6f87-d533-c02ab888f5cd@redhat.com \
    --to=eric.auger@redhat.com \
    --cc=bharat.bhushan@nxp.com \
    --cc=christoffer.dall@linaro.org \
    --cc=diana.craciun@freescale.com \
    --cc=drjones@redhat.com \
    --cc=p.fedin@samsung.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=shlomo.pongratz@huawei.com \
    --cc=shlomopongratz@gmail.com \
    /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).