From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Liwei <xieliwei@gmail.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: BUG: scheduling while atomic: xenwatch
Date: Tue, 12 Jul 2011 15:04:55 -0400 [thread overview]
Message-ID: <20110712190455.GA4766@dumpdata.com> (raw)
In-Reply-To: <CAPE0SYyJ_Q8L4+3g=4cjgcK2eSKE39WAGkQu3aK1SwMzqhwtNw@mail.gmail.com>
On Wed, Jul 13, 2011 at 02:57:43AM +0800, Liwei wrote:
> On 12 July 2011 21:50, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> >
> > Thanks for reporting it. I've a patch for it ready.
>
> Hmm, where? In the latest pull?
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git devel/xen-pciback-0.6.2
Look for patch
commit 52ff6d79b45e68fadad3a93a937171863a7cf451
Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Date: Mon Jul 11 13:18:09 2011 -0400
xen/pciback: Reshuffle the spinlock to not trigger BUG: scheduling while atomic.
>
> >
> > What tree did you pull from?
>
> # git branch
> xen/next-2.6.32
> * xen/next-3.0
OK, so Jeremy's. Do a cherrypick on that and you should be set.
>
> # cat .git/config
> ----snip----
> [remote "origin"]
> fetch = +refs/heads/*:refs/remotes/origin/*
> url = git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> ----snip----
next prev parent reply other threads:[~2011-07-12 19:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 13:24 BUG: scheduling while atomic: xenwatch Liwei
2011-07-12 13:50 ` Konrad Rzeszutek Wilk
2011-07-12 18:57 ` Liwei
2011-07-12 19:04 ` Konrad Rzeszutek Wilk [this message]
2011-07-12 19:29 ` Liwei
2011-07-12 19:54 ` Konrad Rzeszutek Wilk
2011-07-14 15:44 ` Liwei
2011-07-14 17:46 ` Konrad Rzeszutek Wilk
2011-07-15 19:23 ` Liwei
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=20110712190455.GA4766@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
--cc=xieliwei@gmail.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.