From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH, v2] reduce 'd' debug key's global impact
Date: Thu, 6 May 2010 10:05:48 +0100 [thread overview]
Message-ID: <C80844FC.13630%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4BE2966B0200007800001837@vpn.id2.novell.com>
On 06/05/2010 09:14, "Jan Beulich" <JBeulich@novell.com> wrote:
>>>> Keir Fraser <keir.fraser@eu.citrix.com> 06.05.10 10:01 >>>
>> Although I suppose the event-check vector has a cleaner interface for
>> calling it and should be implemented for all architectures. If you add
>> whatever new flag you need to irq_cpustat_t then it would be cheap to check,
>> being a definite cache hit. I suppose each cpu would
>> check-and-check-and-clear it, and then set it for the next CPU when it is
>> done. That doesn't sound too bad.
>
> Hmm, isn't irq_cpustat_t being used mostly on the local CPU so far,
> and hence introducing reasons for bouncing the cache line wouldn't
> be nice?
It would only get bounced when the 'd' key is pressed, right? I think we
could tolerate that frequency of bounce. :-)
-- Keir
next prev parent reply other threads:[~2010-05-06 9:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 15:34 [PATCH, v2] reduce 'd' debug key's global impact Jan Beulich
2010-05-06 6:46 ` Jan Beulich
2010-05-06 7:42 ` Keir Fraser
2010-05-06 8:01 ` Keir Fraser
2010-05-06 8:14 ` Jan Beulich
2010-05-06 9:05 ` Keir Fraser [this message]
2010-05-06 9:07 ` Jan Beulich
2010-05-06 9:15 ` Keir Fraser
2010-05-06 9:25 ` Jan Beulich
2010-05-06 9:37 ` Keir Fraser
2010-05-06 8:07 ` Jan Beulich
2010-05-06 9:09 ` Keir Fraser
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=C80844FC.13630%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).