From: Roland Dreier <rdreier@cisco.com>
To: "Lee Revell" <rlrevell@joe-job.com>
Cc: "David Brown" <dmlb2000@gmail.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: KVM and rtc missing interupts 2.6.21-rc3
Date: Thu, 08 Mar 2007 19:19:53 -0800 [thread overview]
Message-ID: <ada3b4fxfvq.fsf@cisco.com> (raw)
In-Reply-To: <75b66ecd0703081721y75abccbet32a3c5de906132c8@mail.gmail.com> (Lee Revell's message of "Thu, 8 Mar 2007 20:21:42 -0500")
> Holding a lock too long should be easy to debug with the -rt patch -
> set the preemption related options to match mainline, and enable the
> latency tracer.
Good idea, I'll give it a shot when I get a chance.
prev parent reply other threads:[~2007-03-09 3:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 21:48 KVM and rtc missing interupts 2.6.21-rc3 David Brown
2007-03-08 21:57 ` Roland Dreier
2007-03-09 0:47 ` David Brown
2007-03-09 3:19 ` Roland Dreier
2007-03-09 1:21 ` Lee Revell
2007-03-09 3:19 ` Roland Dreier [this message]
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=ada3b4fxfvq.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=dmlb2000@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.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