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:09:21 +0100 [thread overview]
Message-ID: <C80845D1.13634%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4BE294CF0200007800001825@vpn.id2.novell.com>
On 06/05/2010 09:07, "Jan Beulich" <JBeulich@novell.com> wrote:
>>>> Keir Fraser <keir.fraser@eu.citrix.com> 06.05.10 09:42 >>>
>> Pick something rare like SPURIOUS_APIC_VECTOR. In that particular handler
>> you can even put your check on the unlikely path that checks for and acks a
>> real vectored interrupt.
>
> Hmm, yes, that's indeed better than the event check one.
>
> However, I noticed that even without that change on_selected_cpus()
> is being used in interrupt context, hence I wonder whether indeed only
> the new mechanism should be going the call-func-less route.
If you add this new mechanism to call into __dump_execstate() then there is
no reason not to use it for both the 'old' and 'alt' dumping methods. Indeed
doing it for both will avoid needing your hack to the call_function handler
to pass regs when the info parameter is NULL (which I could understand but
was still icky, and I would probably have changed the interface to the
on_selected/each_cpu functions instead).
-- Keir
prev parent reply other threads:[~2010-05-06 9:09 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
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 [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=C80845D1.13634%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).