All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Li, Xiaoyun" <xiaoyun.li@intel.com>,
	"Xing, Beilei" <beilei.xing@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>
Subject: Re: [PATCH v4] doc: add known issue about legacy intr mode for ixgbe
Date: Mon, 15 Oct 2018 16:14:49 +0000	[thread overview]
Message-ID: <039ED4275CED7440929022BC67E70611532C197C@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1539578194-52527-1-git-send-email-xiaoyun.li@intel.com>



> -----Original Message-----
> From: Li, Xiaoyun
> Sent: Sunday, October 14, 2018 9:37 PM
> To: Xing, Beilei <beilei.xing@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>;
> dev@dpdk.org; Lu, Wenzhuo <wenzhuo.lu@intel.com>; Wu, Jingjing
> <jingjing.wu@intel.com>
> Cc: Li, Xiaoyun <xiaoyun.li@intel.com>
> Subject: [PATCH v4] doc: add known issue about legacy intr mode for ixgbe
> 
> When using uio_pci_generic module or using legacy interrupt mode of
> igb_uio or vfio, X550 cannot get interrupts. Because the Interrupt Status bit is
> not implemented, then the irq cannot be handled correctly and cannot
> report the event fd to DPDK apps.
> 
> Add this hw limitation and details into ixgbe known issue.
> 
> Signed-off-by: Xiaoyun Li <xiaoyun.li@intel.com>

Acked-by: Qi Zhang <qi.z.zhang@intel.com>

Applied to dpdk-next-net-intel.

Thanks
Qi

      reply	other threads:[~2018-10-15 16:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-27  9:16 [PATCH] doc: add known issue about legacy intr mode for ixgbe Xiaoyun Li
2018-09-30  2:24 ` Zhang, Qi Z
2018-09-30  2:46   ` Li, Xiaoyun
2018-09-30  2:48 ` [PATCH v2] " Xiaoyun Li
2018-09-30  2:53 ` [PATCH v3] " Xiaoyun Li
2018-10-03 13:29   ` Zhang, Qi Z
2018-10-15  3:00     ` Li, Xiaoyun
2018-10-15  4:36 ` [PATCH v4] " Xiaoyun Li
2018-10-15 16:14   ` Zhang, Qi Z [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=039ED4275CED7440929022BC67E70611532C197C@SHSMSX103.ccr.corp.intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=wenzhuo.lu@intel.com \
    --cc=xiaoyun.li@intel.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 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.