From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: 4.0/4.1 requests - IO-APIC EOI v4 [RFC]
Date: Mon, 12 Sep 2011 12:30:54 +0100 [thread overview]
Message-ID: <CA93ABFE.20BB7%keir.xen@gmail.com> (raw)
In-Reply-To: <4E6DF9AB0200007800055B2F@nat28.tlf.novell.com>
On 12/09/2011 11:23, "Jan Beulich" <JBeulich@suse.com> wrote:
>>>> On 12.09.11 at 12:15, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>> On 12/09/11 07:50, Jan Beulich wrote:
>>>>>> On 09.09.11 at 18:47, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>>>> + * Xen code doesn't actually prevent multiple IO-APIC
>>>> + * entries being assigned the same vector, so EOI all
>>>> + * pins which have the correct vector.
>>>> + *
>>>> + * Remove the following code when the above assertion
>>>> + * is fulfilled. */
>>>> +
>>> Why don't you just call __io_apic_eoi() recursively here?
>>>
>>> Jan
>>
>> If I call the function recursively, it will loop forever. Anyway, the
>
> Why would it loop forever? You get in here only with pin == -1, and
> for the recursive call you'd pass the pin number you determined.
Exactly. Please re-send the patch with the recursive call. It makes the
function quite a bit shorter.
-- Keir
>> need to clear multiple pins is only temorary until George finishes his
>> per-device AMD interrupt remap patch which will enforce vector
>> uniqueness in each IO-APIC. My expectation is that this issue will be
>> fixed in the next few weeks.
>
> Sure.
>
> Jan
>
prev parent reply other threads:[~2011-09-12 11:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 9:19 4.0/4.1 requests Jan Beulich
2011-09-08 10:12 ` Jan Beulich
2011-09-08 11:29 ` Keir Fraser
2011-09-08 10:17 ` Keir Fraser
2011-09-08 10:48 ` Andrew Cooper
2011-09-08 11:11 ` Keir Fraser
2011-09-08 11:44 ` Jan Beulich
2011-09-08 13:18 ` 4.0/4.1 requests - IO-APIC EOI [RFC] Andrew Cooper
2011-09-08 13:40 ` Jan Beulich
2011-09-08 13:56 ` Andrew Cooper
2011-09-09 15:06 ` Re: 4.0/4.1 requests - IO-APIC EOI v2 [RFC] Andrew Cooper
2011-09-09 15:39 ` Jan Beulich
2011-09-09 15:55 ` Andrew Cooper
2011-09-09 16:03 ` Jan Beulich
2011-09-09 16:22 ` Re: 4.0/4.1 requests - IO-APIC EOI v3 [RFC] Andrew Cooper
2011-09-09 16:47 ` Re: 4.0/4.1 requests - IO-APIC EOI v4 [RFC] Andrew Cooper
2011-09-09 16:50 ` Andrew Cooper
2011-09-12 6:50 ` Jan Beulich
2011-09-12 10:15 ` Andrew Cooper
2011-09-12 10:23 ` Jan Beulich
2011-09-12 11:30 ` 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=CA93ABFE.20BB7%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.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 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.