public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: konrad@kernel.org, xen-devel@lists.xenproject.org,
	boris.ostrovsky@oracle.com, david.vrabel@citrix.com,
	linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH v4] PCI back fixes for 3.17.
Date: Mon, 14 Jul 2014 13:45:25 -0400	[thread overview]
Message-ID: <20140714174525.GD12920@laptop.dumpdata.com> (raw)
In-Reply-To: <9210423415.20140714194304@eikelenboom.it>

On Mon, Jul 14, 2014 at 07:43:04PM +0200, Sander Eikelenboom wrote:
> 
> Monday, July 14, 2014, 7:37:53 PM, you wrote:
> 
> >> >> Ad B)
> >> >> 
> >> >> root@dom0:~# xl pci-list router
> >> >> Vdev Device
> >> >> 05.0 0000:00:1b.0
> >> >> 
> >> >> root@dom0:~# xl pci-assignable-list
> >> >> 0000:02:00.0
> >> >> 
> >> >> root@dom0:~# xl pci-detach router 00:1b.0
> >> >> dmesg shows:
> >> >> [  199.742668] pciback 0000:00:1b.0: restoring config space at offset 0x10 (was 0x4, writing 0xf7d30004)
> >> >> [  199.743527] pciback 0000:00:1b.0: restoring config space at offset 0xc (was 0x0, writing 0x10)
> >> >> [  199.744321] pciback 0000:00:1b.0: restoring config space at offset 0x4 (was 0x100000, writing 0x100006)
> >> >> [  199.757184] xen-pciback pci-1-0: xen_pcibk_xenbus_remove freeing pdev @ 0xffff8800589fce40
> >> >> [  199.758139] xen-pciback pci-1-0: xen_pcibk_disconnect pdev @ 0xffff8800589fce40
> >> >> [  199.862595] xen: xen_unregister_device_domain_owner
> >> >> 
> >> >> xl dmesg shows:
> >> >> (XEN) [2014-07-14 16:28:29] memory_map:remove: dom1 gfn=f3070 mfn=f7d30 nr=4
> >> >> (XEN) [2014-07-14 16:28:29] io.c:322: d1: unbind: m_gsi=22 g_gsi=36 dev=00:00.5 intx=0
> >> >> (XEN) [2014-07-14 16:28:29] io.c:390: d1 unmap: m_irq=22 dev=00:00.5 intx=0
> >> >> (XEN) [2014-07-14 16:28:29] [VT-D]iommu.c:1579: d1:PCIe: unmap 0000:00:1b.0
> >> >> (XEN) [2014-07-14 16:28:29] [VT-D]iommu.c:1440: d0:PCIe: map 0000:00:1b.0
> >> >> 
> >> >> root@dom0:~# xl pci-list router
> >> >> root@dom0:~# xl pci-assignable-list
> >> >> 0000:00:1b.0
> >> >> 0000:02:00.0
> >> >> 
> >> >> root@dom0:~# xl pci-assignable-remove 00:1b.0
> >> >> dmesg shows:
> >> >> [  318.827415] xen: xen_unregister_device_domain_owner
> >> >> [  318.828771] xen: xen_unregister_device_domain_owner: ENODEV
> >> >> [  318.930869] pciback 0000:00:1b.0: restoring config space at offset 0x10 (was 0x4, writing 0xf7d30004)
> >> >> [  318.933435] pciback 0000:00:1b.0: restoring config space at offset 0xc (was 0x0, writing 0x10)
> >> >> [  318.935877] pciback 0000:00:1b.0: restoring config space at offset 0x4 (was 0x100000, writing 0x100006)
> >> >> 
> >> >> root@dom0:~# xl pci-list router
> >> >> root@dom0:~# xl pci-assignable-list
> >> >> 0000:02:00.0
> >> >> 
> >> >> 
> >> 
> >> > And if you do:
> >> 
> >> > # xl pci-detach router 02:00.0
> >> 
> 
> > Err, I meant
> > # xl pci-assignable-remove 02:00.0
> 
> Ah ok .. so that is:
> remove a device from pciback that has never been assigned to any guest .. 
> 
> will also give that a go .. although that probably won't be a problem. 

Right. So I think it all works as expected? That is if you have
two PCI devices assigned to a guest and want to re-use them you
have to do the 'pci-detach' twice and then follow that with
 'pci-assignable-remove' twice as well?

  reply	other threads:[~2014-07-14 17:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11 20:08 [PATCH v4] PCI back fixes for 3.17 konrad
2014-07-11 20:08 ` [PATCH v4 1/5] xen-pciback: Document the various parameters and attributes in SysFS konrad
2014-07-11 20:46   ` Boris Ostrovsky
2014-07-14 16:28     ` Konrad Rzeszutek Wilk
2014-07-11 20:08 ` [PATCH v4 2/5] xen/pciback: Don't deadlock when unbinding konrad
2014-07-11 20:48   ` Boris Ostrovsky
2014-07-11 21:02     ` Konrad Rzeszutek Wilk
2014-07-14 14:13       ` Konrad Rzeszutek Wilk
2014-07-14 14:30         ` Boris Ostrovsky
2014-07-14 15:42           ` Konrad Rzeszutek Wilk
2014-07-11 20:08 ` [PATCH v4 3/5] xen/pciback: Include the domain id if removing the device whilst still in use konrad
2014-07-11 20:08 ` [PATCH v4 4/5] xen/pciback: Print out the domain owning the device konrad
2014-07-11 20:08 ` [PATCH v4 5/5] xen/pciback: Remove tons of dereferences konrad
2014-07-11 20:54   ` Boris Ostrovsky
2014-07-14 16:37 ` [Xen-devel] [PATCH v4] PCI back fixes for 3.17 Sander Eikelenboom
2014-07-14 17:22   ` Konrad Rzeszutek Wilk
2014-07-14 17:29     ` Sander Eikelenboom
2014-07-14 17:37       ` Konrad Rzeszutek Wilk
2014-07-14 17:43         ` Sander Eikelenboom
2014-07-14 17:45           ` Konrad Rzeszutek Wilk [this message]
2014-07-14 18:24             ` Sander Eikelenboom
2014-07-14 18:45               ` Konrad Rzeszutek Wilk
2014-07-14 19:01                 ` Sander Eikelenboom
2014-07-14 19:50                   ` Sander Eikelenboom
2014-07-14 19:54                   ` Konrad Rzeszutek Wilk
2014-07-14 20:16                     ` Sander Eikelenboom
2014-07-14 20:18                       ` Konrad Rzeszutek Wilk
2014-07-14 20:21                         ` Sander Eikelenboom
2014-07-14 20:25                           ` Konrad Rzeszutek Wilk

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=20140714174525.GD12920@laptop.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad@kernel.org \
    --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