qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Fedin <p.fedin@samsung.com>
To: qemu-devel@nongnu.org
Cc: 'Peter Maydell' <peter.maydell@linaro.org>,
	'Shlomo Pongratz' <shlomopongratz@gmail.com>,
	'Shlomo Pongratz' <shlomo.pongratz@huawei.com>
Subject: [Qemu-devel] PING: [PATCH v2 0/2] cpu_arm: Implement irqchip property for	ARM CPU
Date: Fri, 04 Sep 2015 09:49:56 +0300	[thread overview]
Message-ID: <012001d0e6dd$e97e8c10$bc7ba430$@samsung.com> (raw)

 Hi! This message is mainly for Peter. I say you reviewed my major sets, but looks like missed this
one. If it is OK, we could apply it, and i could successfully bring back the missing part in
vGICv3-enabled hw/arm/virt.c which attaches irqchip to CPUs. This would make us more ready for TCG
version of GICv3.

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


> -----Original Message-----
> From: qemu-devel-bounces+p.fedin=samsung.com@nongnu.org [mailto:qemu-devel-
> bounces+p.fedin=samsung.com@nongnu.org] On Behalf Of Pavel Fedin
> Sent: Tuesday, August 25, 2015 3:18 PM
> To: qemu-devel@nongnu.org
> Cc: Peter Maydell; Shlomo Pongratz; Shlomo Pongratz
> Subject: [Qemu-devel] [PATCH v2 0/2] cpu_arm: Implement irqchip property for ARM CPU
> 
> ARMv7m CPU needs a link to NVIC instance for processing interrupts.
> Similarly ARMv8 needs a link to GICv3 for its CPU interface.
> 
> This series builds upon existing mechanism for linking irqchip and
> CPU, bringing the code up to date and making it reusable. Another small
> step towards complete GICv3 implementation.
> 
> v1 => v2:
> - Set link to nvic after it has been initialized
> - Changed object type to "sys-bus-device" because GICv2 and GICv3 do not
>   share common ancestors above that.
> 
> Pavel Fedin (2):
>   cpu_arm: Rename 'nvic' to 'irqchip'
>   armv7m: Use irqchip property instead of direct assignment
> 
>  hw/arm/armv7m.c     |  5 ++---
>  target-arm/cpu.c    |  6 ++++++
>  target-arm/cpu.h    |  5 ++++-
>  target-arm/helper.c | 12 ++++++------
>  4 files changed, 18 insertions(+), 10 deletions(-)
> 
> --
> 1.9.5.msysgit.0

             reply	other threads:[~2015-09-04  6:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04  6:49 Pavel Fedin [this message]
2015-09-04 14:11 ` [Qemu-devel] PING: [PATCH v2 0/2] cpu_arm: Implement irqchip property for ARM CPU Peter Maydell
2015-09-04 14:47   ` Pavel Fedin
2015-09-04 15:01     ` Peter Maydell
2015-09-07 14:12   ` Shlomo Pongratz
2015-09-09  7:07     ` 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='012001d0e6dd$e97e8c10$bc7ba430$@samsung.com' \
    --to=p.fedin@samsung.com \
    --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 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).