From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen pci-passthrough problem with pci-detach and pci-assignable-remove
Date: Fri, 24 Jan 2014 12:48:06 -0500 [thread overview]
Message-ID: <20140124174806.GA15571@phenom.dumpdata.com> (raw)
In-Reply-To: <1889333978.20140124143602@eikelenboom.it>
On Fri, Jan 24, 2014 at 02:36:02PM +0100, Sander Eikelenboom wrote:
>
> Friday, January 10, 2014, 6:38:10 PM, you wrote:
>
> >> > Wow. You just walked in a pile of bugs didn't you? And on Friday
> >> > nonethless.
> >>
> >> As usual ;-)
>
> > Ha!
> > ..snip..
> >> >> [ 489.082358] [<ffffffff81087ac6>] ? mutex_spin_on_owner+0x38/0x45
> >> >> [ 489.106272] [<ffffffff818e5e22>] ? schedule_preempt_disabled+0x6/0x9
> >> >> [ 489.130158] [<ffffffff818e7034>] ? __mutex_lock_slowpath+0x159/0x1b5
> >> >> [ 489.154147] [<ffffffff818e70a6>] ? mutex_lock+0x16/0x25
> >> >> [ 489.177890] [<ffffffff8135972d>] ? pci_reset_function+0x26/0x4e
> >>
> >> > Yeah, that bug my RFC patchset (the one that does the slot/bus reset) should also fix.
> >> > I totally forgot about it !
> >>
> >> Got a link to that patchset ?
>
> > https://lkml.org/lkml/2013/12/13/315
>
> >> I at least could give it a spin .. you never know when fortune is on your side :-)
>
> > It is also at this git tree:
>
> > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git and the
> > branch name is "devel/xen-pciback.slot_and_bus.v0". You will likely
> > want to merge it in your current Linus tree.
>
> > Thank you!
>
>
> Hi Konrad,
>
> Just got time to test this some more, when merging this branch *except* the last commit (9599a5ad38a3bb250e996ccb2cdaab6fb68aaacd)
> seems to help with my problem,i'm no capable of using:
> - xl pci-detach
> - xl pci-assignable-remove
> - echo "BDF" > /sys/bus/pci/drivers/<devicename>/bind
>
> to remove a pci device from a running HVM guest and rebinding it to a driver in dom0 without those nasty stacktraces :-)
> So the first 4 seem to be an improvement.
>
> That last commit (9599a5ad38a3bb250e996ccb2cdaab6fb68aaacd) seems to give troubles of it's own.
Could you email me your lspci output and also which devices you move/switch etc?
Thanks!
>
> --
> Sander
>
next prev parent reply other threads:[~2014-01-24 17:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 14:51 Xen pci-passthrough problem with pci-detach and pci-assignable-remove Sander Eikelenboom
2014-01-10 15:12 ` Konrad Rzeszutek Wilk
2014-01-10 15:57 ` Sander Eikelenboom
2014-01-10 16:12 ` Konrad Rzeszutek Wilk
2014-01-10 16:16 ` Sander Eikelenboom
2014-01-10 17:38 ` Konrad Rzeszutek Wilk
2014-01-10 18:21 ` Sander Eikelenboom
2014-01-10 18:22 ` Sander Eikelenboom
2014-01-24 13:36 ` Sander Eikelenboom
2014-01-24 17:48 ` Konrad Rzeszutek Wilk [this message]
2014-01-24 18:53 ` Sander Eikelenboom
2014-02-20 8:53 ` Sander Eikelenboom
2014-02-20 16:18 ` Sander Eikelenboom
2014-04-01 16:13 ` Konrad Rzeszutek Wilk
2014-04-02 10:43 ` Sander Eikelenboom
2014-04-16 15:30 ` Konrad Rzeszutek Wilk
2014-04-16 15:44 ` Sander Eikelenboom
2014-04-16 16:22 ` Sander Eikelenboom
2014-01-27 16:29 ` George Dunlap
2014-01-27 16:42 ` 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=20140124174806.GA15571@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--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 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.