From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] x86/IO-APIC: refine EOI-ing of migrating level interrupts
Date: Tue, 15 Nov 2011 13:35:27 +0000 [thread overview]
Message-ID: <4EC26A9F.8050501@citrix.com> (raw)
In-Reply-To: <4EC276E90200007800061160@nat28.tlf.novell.com>
On 15/11/11 13:27, Jan Beulich wrote:
>>>> On 15.11.11 at 14:19, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>> On 15/11/11 13:14, Jan Beulich wrote:
>>> if ( ioapic_has_eoi_reg(apic) )
>>> {
>>> /* If vector is unknown, read it from the IO-APIC */
>>> - if ( vector == -1 )
>>> + if ( vector == IRQ_VECTOR_UNASSIGNED )
>> Quick style query: I consider IRQ_VECTOR_UNASSIGNED logically different
>> from passing -1 in as a value for vector, even though they are the are
>> the same value. Is it sensible to mix them?
> I view it quite the other way around: One should explicitly pass
> IRQ_VECTOR_UNASSIGNED when passing a literal value (which
> currently doesn't happen anyway. Primarily because passing
> desc->arch.vector or desc->arch.old_vector could happen to also
> hold this very value.
>
> Jan
Ok.
Do you want any other patches to be tested on the problem server?
--
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com
next prev parent reply other threads:[~2011-11-15 13:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 13:14 [PATCH] x86/IO-APIC: refine EOI-ing of migrating level interrupts Jan Beulich
2011-11-15 13:19 ` Andrew Cooper
2011-11-15 13:27 ` Jan Beulich
2011-11-15 13:35 ` Andrew Cooper [this message]
2011-11-15 13:43 ` Jan Beulich
2011-11-17 16:12 ` Andrew Cooper
2011-11-18 8:31 ` Jan Beulich
2011-11-18 18:01 ` Andrew Cooper
2011-11-18 18:57 ` Andrew Cooper
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=4EC26A9F.8050501@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.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).