From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: "Li, Shaohua" <shaohua.li@intel.com>, <ncunningham@linuxmail.org>,
"Pavel Machek" <pavel@ucw.cz>,
"Patrick Mochel" <mochel@digitalimplant.org>
Subject: Re: Fixing MTRR smp breakage and suspending sysdevs.
Date: Tue, 26 Oct 2004 22:20:38 -0500 [thread overview]
Message-ID: <200410262220.38052.dtor_core@ameritech.net> (raw)
In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD30575699E58@pdsmsx402.ccr.corp.intel.com>
On Tuesday 26 October 2004 09:48 pm, Li, Shaohua wrote:
> >One thing I have noticed is that by adding the sysdev suspend/resume
> >calls, I've gained a few seconds delay. I'll see if I can track down
> the
> >cause.
> Is the problem MTRR resume must be with IRQ enabled, right? Could we
> implement a method sysdev resume with IRQ enabled?
If I understand correctly the point of classifying device as sysdev is
that it (device) is essential for the system and must be suspended last
and resumed first, presumably with interrupts off. IRQ controller comes
to mind...
--
Dmitry
next prev parent reply other threads:[~2004-10-27 3:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 2:48 Fixing MTRR smp breakage and suspending sysdevs Li, Shaohua
2004-10-27 2:49 ` Nigel Cunningham
2004-10-27 3:20 ` Dmitry Torokhov [this message]
2004-10-27 3:17 ` Nigel Cunningham
2004-10-27 3:50 ` Dmitry Torokhov
2004-10-27 3:55 ` Nigel Cunningham
2004-10-27 10:00 ` Pavel Machek
2004-10-28 22:38 ` time and suspending sysdevs [was Re: Fixing MTRR smp breakage and suspending sysdevs.] Pavel Machek
2004-10-29 0:18 ` Nigel Cunningham
-- strict thread matches above, loose matches on Subject: below --
2004-10-29 1:41 Fixing MTRR smp breakage and suspending sysdevs Li, Shaohua
2004-10-28 2:40 Li, Shaohua
2004-10-28 1:54 Pallipadi, Venkatesh
2004-10-28 9:00 ` Pavel Machek
2004-10-27 12:23 Li, Shaohua
2004-10-28 10:20 ` Pavel Machek
2004-10-26 2:39 Nigel Cunningham
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=200410262220.38052.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=ncunningham@linuxmail.org \
--cc=pavel@ucw.cz \
--cc=shaohua.li@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox