[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v10 6/6] passthrough/io: Fall back to remapping interrupt when we can't use VT-d PI


  • To: "Gao, Chao" <chao.gao@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Wed, 22 Mar 2017 06:34:28 +0000
  • Accept-language: en-US
  • Cc: Jan Beulich <jbeulich@xxxxxxxx>
  • Delivery-date: Wed, 22 Mar 2017 06:34:45 +0000
  • Dlp-product: dlpe-windows
  • Dlp-reaction: no-action
  • Dlp-version: 10.0.102.7
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: AQHSnYXmIUV8D8OQl0WURTCBOzGw/KGgcVJw
  • Thread-topic: [PATCH v10 6/6] passthrough/io: Fall back to remapping interrupt when we can't use VT-d PI

> From: Gao, Chao
> Sent: Wednesday, March 15, 2017 1:11 PM
> 
> The current logic of using VT-d pi is when guest configurates the pirq's
> destination vcpu to a single vcpu, the according IRTE is updated to posted
> format. If the destination of the pirq is multiple vcpus, we just use 
> interrupt
> remapping. 

From the patch I think you actually means the reverse - current
logic will stay in posted format.

> Obviously, we should fall back to remapping interrupt when
> guest wrongly configurate destination of pirq or makes it have multi-
> destination vcpus.
> 
> Signed-off-by: Chao Gao <chao.gao@xxxxxxxxx>

with above comment fixed:

Reviewed-by: Kevin Tian <kevin.tian@xxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.