From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: =?utf-8?q?=5BPATCH_2/4=5D_x86/MSI-X=3A_access_MSI?= =?utf-8?q?=E2=80=91X_table_only_after_having_enabled_MSI=E2=80=91X?= Date: Fri, 13 Mar 2015 19:18:05 +0000 Message-ID: <550337ED.10705@citrix.com> References: <54FF26F002000078000682F7@mail.emea.novell.com> <54FF29C20200007800068359@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54FF29C20200007800068359@mail.emea.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 10/03/15 16:28, Jan Beulich wrote: > As done in Linux by f598282f51 ("PCI: Fix the NIU MSI-X problem in a > better way") and its broken predecessor, make sure we don't access the > MSI-X table without having enabled MSI-X first, using the mask-all flag > instead to prevent interrupts from occurring. > > Signed-off-by: Jan Beulich General quarms of this series aside, Reviewed-by: Andrew Cooper There is a spurious whitespace change and a spurious comment change which you perhaps didn't mean to include.