From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Daniel J Blueman <daniel.blueman@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, H Peter Anvin <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ioapic: fix potential resume deadlock
Date: Mon, 16 May 2011 10:04:31 -0700 [thread overview]
Message-ID: <1305565471.26846.4.camel@sbsiddha-MOBL3.sc.intel.com> (raw)
In-Reply-To: <20110516113205.GF19837@elte.hu>
On Mon, 2011-05-16 at 04:32 -0700, Ingo Molnar wrote:
> * Daniel J Blueman <daniel.blueman@gmail.com> wrote:
>
> > Hi Suresh,
> >
> > On 14 May 2011 01:48, Suresh Siddha <suresh.b.siddha@intel.com> wrote:
> > > On Wed, 2011-05-11 at 09:15 -0700, Daniel J Blueman wrote:
> > >> Superb, this works, tested against 2.6.39-rc7 and addresses the "BUG:
> > >> sleeping function called from invalid context at mm/slub.c:824"
> > >> warning I was previously seeing. It would be good to get this fix into
> > >> 2.6.39-final if possible.
> > >>
> > >> Tested-by: Daniel J Blueman <daniel.blueman@gmail.com>
> > >
> > > Thanks Daniel for testing my quick patch. I have appended the complete
> > > patch which cleans up this code.
> > >
> > > Ingo, This patch is relatively big (mostly removes the duplicate code
> > > and changes the location where we allocate ioapic_saved_data, so that
> > > this can be shared between interrupt-remapping and io-apic
> > > suspend/resume flows). May be this can go into 2.6.40-rc1 and probably
> > > go to 2.6.39-stable?
> > >
> > > Or we can take the Daniel's GFP_ATOMIC patch for 2.6.39 and push this
> > > patch for 2.6.40-rc1. I am ok either way.
> > []
> >
> > Testing this, all looks well in that the patch resolves the
> > potentially sleeping allocation, however I do see (on boot) this
> > suspicious message (though suspend and resume does work):
> >
> > IOAPIC 0: suspend/resume impossible!
> >
> > I guess it's not expected...
oops. I had a spurious initialization, from the earlier attempts to fix
this that was still left out.
> No. Has this been introduced by Suresh's patch?
Ofcourse yes ;(
Will fix this and split the patch into multiple steps.
thanks,
suresh
next prev parent reply other threads:[~2011-05-16 17:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 2:40 Daniel J Blueman
2011-05-10 5:32 ` Daniel J Blueman
2011-05-10 7:35 ` Ingo Molnar
2011-05-10 10:53 ` Daniel J Blueman
2011-05-10 23:58 ` Suresh Siddha
2011-05-11 16:15 ` Daniel J Blueman
2011-05-13 17:48 ` Suresh Siddha
2011-05-14 14:39 ` Daniel J Blueman
2011-05-16 11:32 ` Ingo Molnar
2011-05-16 17:04 ` Suresh Siddha [this message]
2011-05-16 11:34 ` Ingo Molnar
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=1305565471.26846.4.camel@sbsiddha-MOBL3.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=daniel.blueman@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®