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

Re: [Xen-devel] [PATCH 1/4] x86/vMSI-X: defer intercept handler registration

To: Jan Beulich <JBeulich@xxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>
From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date: Tue, 21 Jun 2016 18:11:50 +0100
Delivery-date: Tue, 21 Jun 2016 17:11:57 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 08/06/16 13:52, Jan Beulich wrote:
> There's no point in registering the internal MSI-X table intercept
> functions on all domains - it is sufficient to do so once a domain gets
> an MSI-X capable device assigned.
>
> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>

Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>

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

References:
- [Xen-devel] [PATCH 0/4] x86/vMSI-X: misc improvements
  - From: Jan Beulich
- [Xen-devel] [PATCH 1/4] x86/vMSI-X: defer intercept handler registration
  - From: Jan Beulich

Prev by Date: [Xen-devel] [PATCH 13/17 v3] xen: move FLASK entry under XSM in Kconfig
Next by Date: [Xen-devel] [xen-unstable-smoke test] 96064: tolerable all pass - PUSHED
Previous by thread: Re: [Xen-devel] [PATCH 1/4] x86/vMSI-X: defer intercept handler registration
Next by thread: [Xen-devel] [PATCH 2/4] x86/vMSI-X: drop list lock
Index(es):
- Date
- Thread

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