mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Sander Eikelenboom <linux@eikelenboom.it>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: <gregkh@linuxfoundation.org>, <boris.ostrovsky@oracle.com>,
	<xen-devel@lists.xenproject.org>,
	David Vrabel <david.vrabel@citrix.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH v5] Fixes to Xen pciback for 3.17.
Date: Tue, 5 Aug 2014 10:31:08 +0100	[thread overview]
Message-ID: <53E0A45C.4050400@citrix.com> (raw)
In-Reply-To: <75613802.20140805104438@eikelenboom.it>

On 05/08/14 09:44, Sander Eikelenboom wrote:
> 
> Monday, August 4, 2014, 8:43:18 PM, you wrote:
> 
>> On Fri, Aug 01, 2014 at 04:30:05PM +0100, David Vrabel wrote:
>>> On 14/07/14 17:18, Konrad Rzeszutek Wilk wrote:
>>>> Greg: goto GHK
>>>>
>>>> This is v5 version of patches to fix some issues in Xen PCIback.
>>>
>>> Applied to devel/for-linus-3.17.
> 
>> Thank you.
>>>
>>> I dropped the stable Cc for #2 pending a final decision on whether it
>>> really is a stable candidate.
> 
>> OK.
>>>
>>> David
> 
> Hi Konrad / David,
> 
> This series still lacks a resolution on the sysfs /do_flr /reset,
> as a result the pci devices are not reset after shutdown of a guest.
> (no more pciback 0000:xx:xx.x: restoring config space at offset xxx)
> 
> So this series now introduces a regression to 3.16, which causes devices to malfunction 
> after a guest reboot or after assigning the devices to another guest.

I don't follow what you're saying.  The lack of a device reset for PCI
devices with no FLR method isn't a regression as this has never worked.
 Can you explain in more detail what the regression is and which patch
caused it?

> Apart from that .. i can't resist to remind the other issue with removing pci
> devices passed through to HVM guests related to the signaling via xenstore,
> described in:
> 
> http://lists.xen.org/archives/html/xen-devel/2014-07/msg01875.html

I don't remember seeing you posting a patch...?

David

  reply	other threads:[~2014-08-05  9:31 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 16:18 Konrad Rzeszutek Wilk
2014-07-14 16:18 ` [PATCH v5 1/6] xen-pciback: Document the various parameters and attributes in SysFS Konrad Rzeszutek Wilk
2014-07-28 13:04   ` David Vrabel
2014-07-28 14:56     ` Greg KH
2014-08-01 14:59       ` [Xen-devel] " David Vrabel
2014-07-14 16:18 ` [PATCH v5 2/6] xen/pciback: Don't deadlock when unbinding Konrad Rzeszutek Wilk
2014-07-28 13:06   ` David Vrabel
2014-08-04 18:42     ` Konrad Rzeszutek Wilk
2014-08-05  9:27       ` [Xen-devel] " David Vrabel
2014-07-14 16:18 ` [PATCH v5 3/6] driver core: Provide an wrapper around the mutex to do lockdep warnings Konrad Rzeszutek Wilk
2014-07-14 17:39   ` Greg KH
2014-07-14 16:18 ` [PATCH v5 4/6] xen/pciback: Include the domain id if removing the device whilst still in use Konrad Rzeszutek Wilk
2014-07-14 16:18 ` [PATCH v5 5/6] xen/pciback: Print out the domain owning the device Konrad Rzeszutek Wilk
2014-07-14 16:18 ` [PATCH v5 6/6] xen/pciback: Remove tons of dereferences Konrad Rzeszutek Wilk
2014-07-14 17:40 ` [PATCH v5] Fixes to Xen pciback for 3.17 Greg KH
2014-07-14 17:39   ` Konrad Rzeszutek Wilk
2014-08-01 15:30 ` David Vrabel
2014-08-04 18:43   ` Konrad Rzeszutek Wilk
2014-08-05  8:44     ` [Xen-devel] " Sander Eikelenboom
2014-08-05  9:31       ` David Vrabel [this message]
2014-08-05  9:44         ` Sander Eikelenboom
2014-08-05 13:49           ` Konrad Rzeszutek Wilk
2014-08-05 14:04             ` Sander Eikelenboom
2014-08-06 18:59               ` Sander Eikelenboom
2014-08-06 19:18                 ` Konrad Rzeszutek Wilk
2014-08-06 19:25                   ` Sander Eikelenboom
2014-08-06 19:39                     ` Konrad Rzeszutek Wilk
2014-08-06 19:47                       ` Sander Eikelenboom
2014-08-06 20:09                         ` Konrad Rzeszutek Wilk
2014-08-06 20:17                           ` Sander Eikelenboom
2014-08-06 22:08                             ` Sander Eikelenboom
2014-08-07  9:04                       ` David Vrabel
2014-08-25 17:18                         ` Sander Eikelenboom
2014-08-05 14:33             ` Sander Eikelenboom

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=53E0A45C.4050400@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@eikelenboom.it \
    --cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome