From: Keir Fraser <keir.xen@gmail.com>
To: Kai Huang <mail.kai.huang@gmail.com>, Xen-devel@lists.xensource.com
Subject: Re: [question] what's the purpose of smp_send_event_check_mask?
Date: Thu, 19 Jan 2012 09:14:04 +0000 [thread overview]
Message-ID: <CB3D8F5C.291AF%keir.xen@gmail.com> (raw)
In-Reply-To: <CANqQZNFTjKuskMBQKOBud_Jx7_HNqQ0AeLjPO-cOZ8N7vk==HQ@mail.gmail.com>
On 19/01/2012 09:02, "Kai Huang" <mail.kai.huang@gmail.com> wrote:
> Hi,
>
> I see cpu_raise_softirq calls smp_send_event_check_mask after setting
> softirq bit for target CPU if target CPU is not the current CPU. I
> thought smp_send_event_check_mask will send IPI to target CPU and then
> trigger target CPU to run pending irq, but seems
> smp_send_event_check_mask does nothing but jast ACK the IPI. So what's
> the purpose of this function? Why do we need this function?
Xen always checks softirqs on return from interrupt context to guest
context, and also in its idle loopon wakeup. Hence the event_check interrupt
handler itself doesn't need to do anything.
> BTW, would someone gives me some knowledge when will the pending irqs
> be triggered to run after setting up the pending bits? Seems normally
> they are called asynchronously.
Yes, of course it's asynchronous, the smp_send_event_check_mask interrupt is
just to make sure it happens "soon".
-- Keir
> Thanks in advance!
>
> -cody
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2012-01-19 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 9:02 [question] what's the purpose of smp_send_event_check_mask? Kai Huang
2012-01-19 9:14 ` Keir Fraser [this message]
2012-01-19 9:18 ` Kai Huang
2012-01-19 9:26 ` Kai Huang
2012-01-19 9:49 ` Keir Fraser
2012-01-19 9:52 ` Kai Huang
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=CB3D8F5C.291AF%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Xen-devel@lists.xensource.com \
--cc=mail.kai.huang@gmail.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 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.