From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: KDB improvements for IA64
Date: Tue, 10 May 2005 18:26:17 +0000 [thread overview]
Message-ID: <17024.64713.827619.735000@napali.hpl.hp.com> (raw)
In-Reply-To: <4280D2C5.3060604@bull.net>
>>>>> On Tue, 10 May 2005 17:27:01 +0200, Francois Wellenreiter <Francois.Wellenreiter@bull.net> said:
Francois> - timeouts when exiting from KDB will never occur I have
Francois> noticed that after a long time in KDB, some drivers enter
Francois> in timeout sequences. Now, the different ITC values are
Francois> saved when entering KDB and restored when going out.
This sounds fragile to me. For one thing, the kernel may not use ITC
at all for timeouts (true for most NUMA platforms). Also, even if the
ITC is in use, you'd probably have to resync them on the slave CPUs
after restoring the time-keeper's ITC value. Not to mention that if
the timeout is related to an external event, then faking time won't
help no matter what.
--david
next prev parent reply other threads:[~2005-05-10 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 15:27 KDB improvements for IA64 Francois Wellenreiter
2005-05-10 18:26 ` David Mosberger [this message]
2005-05-11 4:40 ` Keith Owens
2005-05-11 6:06 ` Francois Wellenreiter
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=17024.64713.827619.735000@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.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