From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Sander Eikelenboom <linux@eikelenboom.it>, xen-devel@lists.xensource.com
Subject: Re: xen-swiotlb: WARNING: at kernel/smp.c:421 smp_call_function_many+0x66/0x1a1()
Date: Thu, 22 Jul 2010 16:07:37 -0400 [thread overview]
Message-ID: <20100722200737.GA5833@phenom.dumpdata.com> (raw)
In-Reply-To: <4C48A320.40707@goop.org>
On Thu, Jul 22, 2010 at 12:59:28PM -0700, Jeremy Fitzhardinge wrote:
> On 07/22/2010 12:32 PM, Sander Eikelenboom wrote:
> > Hi Konrad,
> >
> > Finally found the time to test the xen-swiotlb again (together with usb3/xhci isoc pathes)
> > I began with your tree:
> > git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git devel/merge.2.6.35-rc3
> >
> > and after that i merged in a tree for the xhci part that is based on 2.6.35-rc4:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/sarah/xhci.git amd-isoc
> >
> > That all went without a problem, booting the resulting kernel in a PV domU gives the warnings below, i hope these can be addressed before the next merge window and xen-swiotlb will make it in !
> > Despite the 2 warnings, the usb devices i passed through seem to work ok.
> >
>
> Looks like you need changes:
> c2ae7934bba9f4e0492497953b60ffe75f9c3f5b
> 3ada8ba278a91fc73062d1ff6c6cd80bf7a058f3
Yup!
Thanks for finding them.
Sander, I should have a tree shortly up - with some other fixes in the
xen-pcifront in them.
next prev parent reply other threads:[~2010-07-22 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 19:32 xen-swiotlb: WARNING: at kernel/smp.c:421 smp_call_function_many+0x66/0x1a1() Sander Eikelenboom
2010-07-22 19:59 ` Jeremy Fitzhardinge
2010-07-22 20:07 ` Konrad Rzeszutek Wilk [this message]
2010-07-22 20:11 ` Sander Eikelenboom
2010-07-24 0:02 ` Konrad Rzeszutek Wilk
2010-07-23 9:22 ` Sander Eikelenboom
2010-07-23 14:10 ` Jeremy Fitzhardinge
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=20100722200737.GA5833@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jeremy@goop.org \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xensource.com \
/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.