All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Fedin <p.fedin@samsung.com>
To: 'Peter Maydell' <peter.maydell@linaro.org>
Cc: 'Shlomo Pongratz' <shlomo.pongratz@huawei.com>,
	'Shlomo Pongratz' <shlomopongratz@gmail.com>,
	'QEMU Developers' <qemu-devel@nongnu.org>,
	'Christoffer Dall' <christoffer.dall@linaro.org>,
	'Eric Auger' <eric.auger@linaro.org>
Subject: Re: [Qemu-devel] [PATCH v8 2/5] Extract some reusable vGIC code
Date: Tue, 11 Aug 2015 10:23:09 +0300	[thread overview]
Message-ID: <00a901d0d406$93d5a990$bb80fcb0$@samsung.com> (raw)
In-Reply-To: <CAFEAcA--b-mzUrBepJKN5xwhfzyAuqSkFmFiNiEqv+U7wSxjOQ@mail.gmail.com>

 Hello!

> The need to add num_irq to this prototype reveals the ugliness
> of it as an interface.

> I don't think we gain much by making these two functions common,
> and we do get a lot of churn in the existing code below.

 You know, i was also thinking about it. And actually there is a way to resolve this: make some common structure holding num_irqs, num_cpus and dev_fd, and share it between GICv2 and GICv3 code. But wouldn't this be ugly too? So, i decided to make some compromise and leave it this way, at least for now.
 Regarding the latter two functions, i thought that they are useful for future live migration, aren't they? 

> It would be much nicer to convert the
> GIC to using named GPIO arrays for its incoming interrupt
> lines, so that you can handle the different cases of SPIs
> and PPIs naturally rather than exposing the awkward mapping
> from multiple different sets of interrupts into a single
> integer space.

 No no, not now. I believe this would require lots if changes in all machne models, i'm not ready for this...

Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia

  reply	other threads:[~2015-08-11  7:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10 12:06 [Qemu-devel] [PATCH v8 0/5] vGICv3 support Pavel Fedin
2015-08-10 12:06 ` [Qemu-devel] [PATCH v8 1/5] Implement GIC-500 base class Pavel Fedin
2015-08-10 17:23   ` Peter Maydell
2015-08-11  7:53     ` Pavel Fedin
2015-08-11  9:20       ` Peter Maydell
2015-08-11  9:35         ` Pavel Fedin
2015-08-11 10:15           ` Peter Maydell
2015-08-11 10:39             ` Pavel Fedin
2015-08-11 10:42               ` Peter Maydell
2015-08-10 12:06 ` [Qemu-devel] [PATCH v8 2/5] Extract some reusable vGIC code Pavel Fedin
2015-08-10 17:34   ` Peter Maydell
2015-08-11  7:23     ` Pavel Fedin [this message]
2015-08-10 12:06 ` [Qemu-devel] [PATCH v8 3/5] Introduce irqchip type specification for KVM Pavel Fedin
2015-08-10 16:45   ` Peter Maydell
2015-08-12 11:44     ` Pavel Fedin
2015-08-12 11:45       ` Christoffer Dall
2015-08-12 12:27     ` Pavel Fedin
2015-08-12 12:59       ` Peter Maydell
2015-08-12 13:23         ` Christoffer Dall
2015-08-12 14:14           ` Eric Auger
2015-08-12 14:24             ` Christoffer Dall
2015-08-12 15:21               ` Eric Auger
2015-08-10 12:06 ` [Qemu-devel] [PATCH v8 4/5] Initial implementation of vGICv3 Pavel Fedin
2015-08-10 17:18   ` Peter Maydell
2015-08-10 12:06 ` [Qemu-devel] [PATCH v8 5/5] Add gicversion option to virt machine Pavel Fedin
2015-08-10 17:12   ` Peter Maydell
2015-08-13 11:02     ` Pavel Fedin

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='00a901d0d406$93d5a990$bb80fcb0$@samsung.com' \
    --to=p.fedin@samsung.com \
    --cc=christoffer.dall@linaro.org \
    --cc=eric.auger@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=shlomo.pongratz@huawei.com \
    --cc=shlomopongratz@gmail.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.