From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: [pciback] BUG: spinlock wrong CPU on CPU#2, xenwatch/40 lock: ffff88001dd9d310, .magic: dead4ead, .owner: xenwatch/40, .owner_cpu: 0
Date: Wed, 10 Nov 2010 09:27:26 -0500 [thread overview]
Message-ID: <20101110142726.GB16120@dumpdata.com> (raw)
In-Reply-To: <179943669.20101110101110@eikelenboom.it>
On Wed, Nov 10, 2010 at 10:11:10AM +0100, Sander Eikelenboom wrote:
> Hi Konrad,
>
> I saw you have made a branch for upstream pciback in your tree ?
Wow, you are quick, I just made it on Monday. There is still some
extra work required as the 2.6.37-rc1 does not have the XenBus backend up-ported.
So that branch is not ready.
> I have one request, would it be possible to allow a wildcard (*) for the function .. so xen-pciback.hide=(04:00.*) would work just as it does in the domU .cfg ?
Good idea - will do it.
>
> Apart from that i sometimes get this when starting a domain with pci devices passed through:
>
> Nov 10 09:48:04 localhost kernel: [ 893.055513] BUG: spinlock wrong CPU on CPU#2, xenwatch/40
> Nov 10 09:48:04 localhost kernel: [ 893.056268] lock: ffff88001dd9d310, .magic: dead4ead, .owner: xenwatch/40, .owner_cpu: 0
Yeah, that one is tied in the fact that the XenBus backend thread is taking
the spinlock and in pciback we call xenstore, which can go to sleep, and then
we can wake up on another CPU.
I need to talk to Ian about the XenBus thread to see how this can be made safe.
prev parent reply other threads:[~2010-11-10 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 9:11 [pciback] BUG: spinlock wrong CPU on CPU#2, xenwatch/40 lock: ffff88001dd9d310, .magic: dead4ead, .owner: xenwatch/40, .owner_cpu: 0 Sander Eikelenboom
2010-11-10 14:27 ` Konrad Rzeszutek Wilk [this message]
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=20101110142726.GB16120@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Xen-devel@lists.xensource.com \
--cc=linux@eikelenboom.it \
/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.