All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@suse.com>
To: ml-ak@hfp.de
Cc: xen-devel@lists.xen.org
Subject: Re: Regression PCI passthrough from 4.5.5 to 4.6.0-rc1
Date: Mon, 31 Jul 2017 04:12:45 -0600	[thread overview]
Message-ID: <597F029D0200007800103028@prv-mh.provo.novell.com> (raw)
In-Reply-To: <op.y3i38xehppxxz1@kriftel>

>>> "Andreas Kinzler" <ml-ak@hfp.de> 07/17/17 6:32 PM >>>
>>> Jan, I still have access to the hardware so perhaps we can finally solve
>>> this problem.
>> Feel free to go ahead; I'll be on vacation for the next three weeks.
>
>Perhaps we can shortcut debugging a bit because I looked through the  
>patches of XenServer 7.2 and found the attached patch. Now I tried it and  
>it seems to solve all the problems. Does that patch look good to you, too?

Iirc the patch had even been submitted once, and rejected as being not
generally correct (i.e. it cures a symptom rather than the cause). What
we'd need to know is the order of actions the guest takes which ought to
result in the vector getting unmasked, but doesn't in reality.

Jan


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

  parent reply	other threads:[~2017-07-31 10:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-07 16:39 Regression PCI passthrough from 4.5.5 to 4.6.0-rc1 Andreas Kinzler
2017-07-09 19:26 ` Pasi Kärkkäinen
2017-07-10 16:56   ` Andreas Kinzler
2017-07-14 11:46     ` Jan Beulich
2017-07-17 16:32       ` Andreas Kinzler
2017-07-21  8:51         ` Pasi Kärkkäinen
2017-07-31 10:12         ` Jan Beulich [this message]
2017-08-14 11:31           ` Andreas Kinzler
2017-08-14 11:44             ` Jan Beulich
2017-08-14 11:56               ` Roger Pau Monné
2017-08-14 12:08                 ` Andreas Kinzler
2017-08-15  9:55                   ` Roger Pau Monné
2017-08-15 11:00                     ` Roger Pau Monné
2017-08-15 12:12                       ` Jan Beulich
2017-08-15 12:29                         ` Roger Pau Monné
2017-08-17 17:36                     ` Andreas Kinzler
2017-08-18  7:16                       ` Jan Beulich
2017-08-18 11:03                       ` Roger Pau Monné
2017-08-21  9:09                         ` Andreas Kinzler
2017-08-21  9:46                           ` Roger Pau Monné
2017-08-21 11:26                             ` Andreas Kinzler
2017-08-21 12:22                             ` Jan Beulich
2017-08-21 12:32                               ` Andreas Kinzler
2017-08-21 12:39                                 ` Jan Beulich
2017-08-21 14:49                               ` Roger Pau Monné
2017-08-21 15:14                                 ` Jan Beulich
2017-08-21 15:18                                   ` Roger Pau Monné
2017-08-22  8:06                                     ` Roger Pau Monné
2017-08-23 17:13                                       ` Andreas Kinzler
2017-08-24  8:23                                         ` Roger Pau Monné
2017-11-02 17:02                                           ` Pasi Kärkkäinen
2017-11-02 17:11                                             ` Roger Pau Monné
2017-11-02 17:13                                               ` Pasi Kärkkäinen

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=597F029D0200007800103028@prv-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=ml-ak@hfp.de \
    --cc=xen-devel@lists.xen.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 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.