qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Li Liu <john.liuli@huawei.com>
To: Eric Auger <eric.auger@linaro.org>,
	kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] The status about vhost-net on kvm-arm?
Date: Wed, 13 Aug 2014 10:11:04 +0800	[thread overview]
Message-ID: <53EAC938.3050205@huawei.com> (raw)
In-Reply-To: <53E9C274.1090009@linaro.org>



On 2014/8/12 15:29, Eric Auger wrote:
> On 08/12/2014 04:41 AM, Li Liu wrote:
>> Hi all,
>>
>> Is anyone there can tell the current status of vhost-net on kvm-arm?
>>
>> Half a year has passed from Isa Ansharullah asked this question:
>> http://www.spinics.net/lists/kvm-arm/msg08152.html
>>
>> I have found two patches which have provided the kvm-arm support of
>> eventfd and irqfd:
>>
>> 1) [RFC PATCH 0/4] ARM: KVM: Enable the ioeventfd capability of KVM on ARM
>> http://lists.gnu.org/archive/html/qemu-devel/2014-01/msg01770.html
>>
>> 2) [RFC,v3] ARM: KVM: add irqfd and irq routing support
>> https://patches.linaro.org/32261/
> 
> Hi Li,
> 
> The patch below uses Paul Mackerras' work and removed usage of GSI
> routing table. It is a simpler alternative to 2)
> http://www.spinics.net/lists/kvm/msg106535.html
> 

Thanks for your tips. This looks more clear.

Best Regards

Li

>>
>> And there's a rough patch for qemu to support eventfd from Ying-Shiuan Pan:
>>
>> [Qemu-devel] [PATCH 0/4] ioeventfd support for virtio-mmio
>> https://lists.gnu.org/archive/html/qemu-devel/2014-02/msg00715.html
>>
>> But there no any comments of this patch. And I can found nothing about qemu
>> to support irqfd. Do I lost the track?
> 
> Actually I am using irqfd in QEMU VFIO Platform device
> https://lists.nongnu.org/archive/html/qemu-devel/2014-08/msg01455.html
> 
> Best Regards
> 
> Eric
> 
>>
>> If nobody try to fix it. We have a plan to complete it about virtio-mmio
>> supporing irqfd and multiqueue.
>>
>>
>>
>>
>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe kvm" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
> 
> 
> 

  reply	other threads:[~2014-08-13  2:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12  2:41 [Qemu-devel] The status about vhost-net on kvm-arm? Li Liu
2014-08-12  7:29 ` Eric Auger
2014-08-13  2:11   ` Li Liu [this message]
2014-08-12 15:47 ` Nikolay Nikolaev
2014-08-13  2:23   ` Li Liu
2014-08-13  2:31     ` Ying-Shiuan Pan
2014-08-13  9:10   ` Nikolay Nikolaev
2014-08-13 11:07     ` Li Liu
2014-08-13 11:25     ` Nikolay Nikolaev
2014-08-14  3:50       ` Li Liu
2014-08-14 15:58         ` Joel Schopp
2014-08-15  3:04         ` Li Liu
2014-08-15  7:24           ` Yingshiuan Pan
2014-10-15 14:39             ` GAUGUEY Rémy 228890
2014-10-17 12:26               ` Li Liu
2014-10-17 12:49                 ` GAUGUEY Rémy 228890
2014-10-23 12:16                   ` Li Liu
2014-11-05  8:33   ` Shannon Zhao

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=53EAC938.3050205@huawei.com \
    --to=john.liuli@huawei.com \
    --cc=eric.auger@linaro.org \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=qemu-devel@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 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).