xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86: fix off-by-one in nr_irqs_gsi calculation
Date: Thu, 26 Jul 2012 17:27:12 +0100	[thread overview]
Message-ID: <CC372E70.39A48%keir.xen@gmail.com> (raw)
In-Reply-To: <501181AA0200007800090B57@nat28.tlf.novell.com>

On 26/07/2012 16:43, "Jan Beulich" <JBeulich@suse.com> wrote:

>>>> On 26.07.12 at 17:31, Keir Fraser <keir@xen.org> wrote:
>> On 26/07/2012 16:06, "Jan Beulich" <JBeulich@suse.com> wrote:
>> 
>>> highest_gsi() returns the last valid GSI, not a count.
>>> 
>>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>> 
>> Why not "nr_irqs_gsi = max(nr_irqs_gsi, highest_gsi()+1)"?
> 
> While I think x = max(y, z) is fine, I generally find x = max(x, y)
> pretty useless - what's the point of assigning a value to itself?
> This is __init code, so code size considerations probably don't
> matter, but I'd still like to not encourage inefficient code like this
> to be used elsewhere by giving a bad example...

I think the code is clearer with max(). An even stronger argument is that it
makes the intent of the patch much more obvious too. I think you should
leave the max() construct in place in this patch.

 -- Keir

> Jan
> 
>>> --- a/xen/arch/x86/io_apic.c
>>> +++ b/xen/arch/x86/io_apic.c
>>> @@ -2531,7 +2531,9 @@ void __init init_ioapic_mappings(void)
>>>          }
>>>      }
>>>  
>>> -    nr_irqs_gsi = max(nr_irqs_gsi, highest_gsi());
>>> +    i = highest_gsi();
>>> +    if ( i >= nr_irqs_gsi )
>>> +        nr_irqs_gsi = i + 1;
>>>  
>>>      if ( max_gsi_irqs == 0 )
>>>          max_gsi_irqs = nr_irqs ? nr_irqs / 8 : PAGE_SIZE;
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xen.org
>>> http://lists.xen.org/xen-devel
> 
> 
> 

      reply	other threads:[~2012-07-26 16:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 15:06 [PATCH] x86: fix off-by-one in nr_irqs_gsi calculation Jan Beulich
2012-07-26 15:31 ` Keir Fraser
2012-07-26 15:43   ` Jan Beulich
2012-07-26 16:27     ` 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=CC372E70.39A48%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xen.org \
    /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).