From: Nicholas Lee <nic-lists@plumtree.co.nz>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net, ian.pratt@cl.cam.ac.uk
Subject: Re: Interrupt levels
Date: Thu, 10 Mar 2005 18:41:02 +1300 [thread overview]
Message-ID: <20050310054100.GA651@plumtree.co.nz> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3550@liverpoolst.ad.cl.cam.ac.uk>
On Thu, Mar 10, 2005 at 02:28:46AM -0000, Ian Pratt wrote:
> Yep, this is a problem that's cropped up several times before. I would
> argue strongly that it's a bug in the bridge code to add a timer for the
> current jiffies value.
You guys need a decent community oriented FAQ/Wiki. If this is a known
issue I probably would have been able to self-diagnose.
> However, the bridge's behaviour is still pretty evil -- you'll still end
> up executing the code HZ (100/1000) times a second, and the intention of
> the user was probably to disable execution of the code altogether. It
> won't slay the machine (like executing int 200k times a second), but its
> not ideal.
Thanks for the help and staying on top of this. I'm glad its not
something major like a hardware driver bug.
Nicholas
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-10 5:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 2:28 Interrupt levels Ian Pratt
2005-03-10 5:41 ` Nicholas Lee [this message]
2005-03-10 10:47 ` James Bulpin
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 22:24 Ian Pratt
2005-03-10 1:56 ` Nicholas Lee
2005-03-09 21:33 Ian Pratt
2005-03-09 22:12 ` Nicholas Lee
2005-03-09 15:20 Ian Pratt
2005-03-09 20:03 ` Nicholas Lee
2005-03-09 9:38 Ian Pratt
2005-03-09 10:59 ` Nicholas Lee
2005-03-09 8:47 Ian Pratt
2005-03-09 9:22 ` Nicholas Lee
2005-03-09 8:03 Ian Pratt
2005-03-09 8:17 ` Nicholas Lee
2005-03-08 23:24 Ian Pratt
2005-03-08 12:50 Ian Pratt
2005-03-09 0:48 ` Nicholas Lee
2005-03-09 3:32 ` Nicholas Lee
2005-03-08 11:07 Ian Pratt
2005-03-08 23:17 ` Nicholas Lee
2005-03-08 23:22 ` Nivedita Singhvi
2005-03-09 0:38 ` Nicholas Lee
2005-03-08 7:52 Ian Pratt
2005-03-08 8:50 ` Nicholas Lee
2005-03-08 9:14 ` Keir Fraser
2005-03-08 9:45 ` Nicholas Lee
2005-03-08 11:45 ` Nicholas Lee
2005-03-08 6:52 Nicholas Lee
2005-03-08 21:58 ` Kurt Garloff
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=20050310054100.GA651@plumtree.co.nz \
--to=nic-lists@plumtree.co.nz \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.