From: Stefan Bader <stefan.bader@canonical.com>
To: Ben Guthro <ben@guthro.net>
Cc: Lin Ming <mlin@ss.pku.edu.cn>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Question about apic ipi interface
Date: Tue, 23 Apr 2013 14:23:41 +0200 [thread overview]
Message-ID: <51767D4D.40308@canonical.com> (raw)
In-Reply-To: <CAOvdn6XppKZ4uYD6MRWHkfE0K6S8LPYsk-SutLWy7qW4Hvcy5g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2230 bytes --]
On 23.04.2013 14:15, Ben Guthro wrote:
> On Tue, Apr 23, 2013 at 11:07 AM, Stefan Bader
> <stefan.bader@canonical.com> wrote:
>> I was looking at some older patch and there is one thing I do not understand.
>>
>> commit f447d56d36af18c5104ff29dcb1327c0c0ac3634
>> xen: implement apic ipi interface
>>
>> Specifically there the implementation of xen_send_IPI_mask_allbutself().
>>
>> void xen_send_IPI_mask_allbutself(const struct cpumask *mask,
>> int vector)
>> {
>> unsigned cpu;
>> unsigned int this_cpu = smp_processor_id();
>>
>> if (!(num_online_cpus() > 1))
>> return;
>>
>> for_each_cpu_and(cpu, mask, cpu_online_mask) {
>> if (this_cpu == cpu)
>> continue;
>>
>> xen_smp_send_call_function_single_ipi(cpu);
>> }
>> }
>>
>> Why is this using xen_smp_send_call_function_single_ipi()? This dumps the
>> supplied vector and always uses XEN_CALL_FUNCTION_SINGLE_VECTOR. In contrast the
>> xen_send_IPI_all() and xen_send_IPI_self() keep the (mapped) vector.
>>
>> Mildly wondering about whether call function would need special casing (just
>> because xen_smp_send_call_function_ipi() is special). But I don't have the big
>> picture there.
>>
>
> Adding Lin Ming here, since this was an evolution of an incomplete
> implementation of mine that was
> ultimately used in a larger context, outside of my original use case
> for it (kgdb of dom0) that ultimately
> gave me credit for this part of the patch, as part of a larger series.
>
> I must admit that I don't recall the reasoning, if there was one.
> It may be an oversight.
>
> This was the original (incomplete) patch, in context:
> http://markmail.org/message/d6ca5zfdmiqipurt
>
>
> Are you seeing issues with the code, or just doing code inspection?
No issues, I was just looking at the patch because we were asked to backport it
to fix another issue (access to the apic IPI functions without checking whether
there is a pointer). Since things did work in most cases before, maybe there is
no real usage. :) I was just curious.
Stefan
>
> Ben
>
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-04-23 12:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 10:07 Question about apic ipi interface Stefan Bader
2013-04-23 12:15 ` Ben Guthro
2013-04-23 12:23 ` Stefan Bader [this message]
2013-04-23 12:48 ` Stefan Bader
2013-05-08 16:26 ` Stefan Bader
2013-05-08 17:00 ` Ben Guthro
2013-05-09 8:56 ` Ian Campbell
2013-05-09 14:33 ` Stefan Bader
2013-05-22 19:40 ` Konrad Rzeszutek Wilk
2013-05-23 9:24 ` Stefan Bader
2013-05-24 14:19 ` Konrad Rzeszutek Wilk
2013-05-28 12:43 ` Konrad Rzeszutek Wilk
2013-05-28 12:50 ` Stefan Bader
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=51767D4D.40308@canonical.com \
--to=stefan.bader@canonical.com \
--cc=ben@guthro.net \
--cc=konrad.wilk@oracle.com \
--cc=mlin@ss.pku.edu.cn \
--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).