All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shlomo Pongratz <shlomopongratz@gmail.com>
To: Pavel Fedin <p.fedin@samsung.com>
Cc: "peter.maydell@linaro.org" <peter.maydell@linaro.org>,
	"eric.auger@linaro.org" <eric.auger@linaro.org>,
	Shlomo Pongratz <shlomo.pongratz@huawei.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"shannon.zhao@linaro.org" <shannon.zhao@linaro.org>,
	"ashoks@broadcom.com" <ashoks@broadcom.com>,
	"imammedo@redhat.com" <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC V5 6/9] hw/intc: arm_gicv3_spi_its
Date: Wed, 21 Oct 2015 16:05:08 +0300	[thread overview]
Message-ID: <CAHzK-V0zNYeYDYn6thGW08JJDVf7AQphxUtL6ud9i04TG1iLLQ@mail.gmail.com> (raw)
In-Reply-To: <014301d10bfe$20c00970$62401c50$@samsung.com>

[-- Attachment #1: Type: text/plain, Size: 1480 bytes --]

Hi,

I just added a placeholder, I didn't add any functionality.

On Wednesday, October 21, 2015, Pavel Fedin <p.fedin@samsung.com> wrote:

>  Hello!
>
> > This patch includes a placeholder code for future spi and its
> > implementation.
>
>  Forgot to comment on this. I see that here you are building an ITS into
> GIC as a monolithic thing. This can be wrong because we
> could want to emulate platforms which have GICv3 but don't have ITS. I
> would suggest to implement ITS as a separate class, and i
> have actually done it in
> http://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg04613.html.
>  So, i think we should not bother about ITS for now and suggest you to
> leave it out completely and focus on pure GICv3.
>  Even more, i have software-emulated ITS code in one of my abandoned
> branches, it lacks only GICv3's ability to receive LPIs (which
> is indeed GIC's functionality). After you're done with GIC, i could rebase
> it on top and post at least as an RFC. May be i'll
> complete it myself, may be you'll want to pick it up, i don't know.
> Actually, it works with Linux kernel and successfully translates
> an MSI event into LPI number, which is then injected into the GIC object.
> Just it's GIC missing the appropriate LPI hanlders. I
> wrote it when there was no in-kernel vITS implementation, but abandoned
> when vITS patch series was published.
>
> Kind regards,
> Pavel Fedin
> Expert Engineer
> Samsung Electronics Research center Russia
>
>
>

[-- Attachment #2: Type: text/html, Size: 1881 bytes --]

  reply	other threads:[~2015-10-21 13:05 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20 17:22 [Qemu-devel] [PATCH RFC V5 0/9] Implement GIC-500 from GICv3 family for arm64 Shlomo Pongratz
2015-10-20 17:22 ` [Qemu-devel] [PATCH RFC V5 2/9] hw/intc: arm_gicv3_interrupts Shlomo Pongratz
2015-10-20 17:22 ` [Qemu-devel] [PATCH RFC V5 3/9] hw/intc: arm_gicv3_cpu_interface Shlomo Pongratz
2015-10-20 17:22 ` [Qemu-devel] [PATCH RFC V5 4/9] hw/intc: arm_gicv3_dist Shlomo Pongratz
2015-10-20 17:22 ` [Qemu-devel] [PATCH RFC V5 5/9] hw/intc arm_gicv3_redist Shlomo Pongratz
2015-10-20 17:22 ` [Qemu-devel] [PATCH RFC V5 6/9] hw/intc: arm_gicv3_spi_its Shlomo Pongratz
2015-10-21 12:43   ` Pavel Fedin
2015-10-21 13:05     ` Shlomo Pongratz [this message]
2015-10-21 13:12       ` Pavel Fedin
2015-10-21 13:14         ` Shlomo Pongratz
2015-10-21 13:48           ` Pavel Fedin
2015-10-21 14:19             ` Shlomo Pongratz
2015-10-21 14:26               ` Pavel Fedin
2015-10-21 14:35                 ` Shlomo Pongratz
2015-10-21 14:41                   ` Pavel Fedin
2015-10-21 14:46                     ` Peter Maydell
2015-10-21 14:54                       ` Pavel Fedin
2015-10-20 17:22 ` [Qemu-devel] [PATCH RFC V5 7/9] hw/intc: arm_gicv3 Shlomo Pongratz
2015-10-20 17:22 ` [Qemu-devel] [PATCH RFC V5 8/9] target-arm/cpu64 GICv3 system instructions support Shlomo Pongratz
2015-10-22  7:33   ` Pavel Fedin
2015-10-22  8:19     ` Shlomo Pongratz
2015-10-22  8:33       ` Pavel Fedin
2015-10-22  8:52         ` Shlomo Pongratz
2015-10-22 10:05           ` Pavel Fedin
2015-10-22 10:45             ` Shlomo Pongratz
2015-10-20 17:22 ` [Qemu-devel] [PATCH RFC V5 9/9] hw/arm: Add virt-v3 machine that uses GIC-500 Shlomo Pongratz
2015-10-21  7:02   ` Pavel Fedin
2015-10-21  8:52     ` Shlomo Pongratz
2015-10-21 10:30       ` Pavel Fedin
2015-10-21 11:33         ` Shlomo Pongratz
2015-10-21 12:24           ` Peter Maydell
2015-10-21 13:01             ` Shlomo Pongratz
2015-10-21 13:24               ` Peter Maydell
2015-10-21 13:26               ` Pavel Fedin
2015-10-21 14:05                 ` Shlomo Pongratz
     [not found] ` <1445361732-16257-2-git-send-email-shlomopongratz@gmail.com>
2015-10-22 11:53   ` [Qemu-devel] [PATCH RFC V5 1/9] hw/intc: Implement GIC-500 support files Pavel Fedin
2016-01-29 16:58 ` [Qemu-devel] [PATCH RFC V5 0/9] Implement GIC-500 from GICv3 family for arm64 Christopher Covington
2016-01-31 15:54   ` Shlomo Pongratz
     [not found]     ` <CAFEAcA9yQoPzC917Lw2zDsa7a5NOfgEk+x68wA1o+Y4ocywCgw@mail.gmail.com>
     [not found]       ` <CAHzK-V0Ur=qYM_OAKmSf+smp3M1E49swkT7yUj=jBkLp+J6Pag@mail.gmail.com>
2016-02-21 12:30         ` Shlomo Pongratz
2016-02-21 15:32           ` Peter Maydell
2016-02-22 11:09             ` Peter Maydell

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=CAHzK-V0zNYeYDYn6thGW08JJDVf7AQphxUtL6ud9i04TG1iLLQ@mail.gmail.com \
    --to=shlomopongratz@gmail.com \
    --cc=ashoks@broadcom.com \
    --cc=eric.auger@linaro.org \
    --cc=imammedo@redhat.com \
    --cc=p.fedin@samsung.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=shannon.zhao@linaro.org \
    --cc=shlomo.pongratz@huawei.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.