All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Day <ncmike@ncultra.org>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH 1/6] xics: add flags for interrupts
Date: Wed, 07 May 2014 09:09:06 -0400	[thread overview]
Message-ID: <87eh05u45p.fsf@pixel.localdomain> (raw)
In-Reply-To: <1399442518-26303-2-git-send-email-aik@ozlabs.ru>


>  
>      for (i = 0; i < ics->nr_irqs; i++) {
>          /* FIXME: filter by server#? */
> -        if (ics->islsi[i]) {
> +        if (ics->irqs[i].flags & XICS_FLAGS_LSI) {
>              resend_lsi(ics, i);

Not part of your patch, but I'm curious about this FIXME (there's an
identical FIXME in resend_msi). Has this proved to be a problem? With
these patches you could have many unallocated interrupts in array AFTER
the last allocated interrupt, correct? In that case, the loop would
continue beyond the last allocated interrupt for no purpose.  There are
a couple ways to mitigate this type of situation by using alternative
data structures to inform the loop traversal. I don't know if it is
worth the effort, though.


> +/* @flags == 0 measn the interrupt is not allocated */
> +#define XICS_FLAGS_LSI                 0x1
> +#define XICS_FLAGS_MSI                 0x2

(nit) typo in the above comment

Mike

-- 
Mike Day | "Endurance is a Virtue"

  reply	other threads:[~2014-05-07 13:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07  6:01 [Qemu-devel] [PATCH 0/6] move interrupts from spapr to xics Alexey Kardashevskiy
2014-05-07  6:01 ` [Qemu-devel] [PATCH 1/6] xics: add flags for interrupts Alexey Kardashevskiy
2014-05-07 13:09   ` Mike Day [this message]
2014-05-09  3:12     ` Alexey Kardashevskiy
2014-05-09 12:20       ` Mike Day
2014-05-08 11:52   ` Alexander Graf
2014-05-08 12:08     ` [Qemu-devel] [Qemu-ppc] " Alexander Graf
2014-05-07  6:01 ` [Qemu-devel] [PATCH 2/6] xics: add find_server Alexey Kardashevskiy
2014-05-07 13:14   ` Mike Day
2014-05-07  6:01 ` [Qemu-devel] [PATCH 3/6] xics: disable flags reset on xics reset Alexey Kardashevskiy
2014-05-08 11:57   ` Alexander Graf
2014-05-07  6:01 ` [Qemu-devel] [PATCH 4/6] spapr: move interrupt allocator to xics Alexey Kardashevskiy
2014-05-07  6:01 ` [Qemu-devel] [PATCH 5/6] spapr: remove @next_irq Alexey Kardashevskiy
2014-05-07  6:01 ` [Qemu-devel] [PATCH 6/6] xics: implement xics_ics_free() Alexey Kardashevskiy
2014-05-08 12:07   ` Alexander Graf
2014-05-09  2:13     ` Alexey Kardashevskiy

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=87eh05u45p.fsf@pixel.localdomain \
    --to=ncmike@ncultra.org \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.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 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.