From: Pavel Fedin <p.fedin@samsung.com>
To: 'Peter Crosthwaite' <crosthwaitepeter@gmail.com>
Cc: 'Peter Maydell' <peter.maydell@linaro.org>,
'Shlomo Pongratz' <shlomopongratz@gmail.com>,
qemu-devel@nongnu.org,
'Shlomo Pongratz' <shlomo.pongratz@huawei.com>
Subject: Re: [Qemu-devel] [PATCH v2] target-arm: Extract some external ARM CPU API
Date: Tue, 27 Oct 2015 15:02:36 +0300 [thread overview]
Message-ID: <013701d110af$5f601a70$1e204f50$@samsung.com> (raw)
In-Reply-To: <CAPokK=obxkaiws4gZPx0HBUHLmhFfQcdmLnN4VXTgkT7WGM52Q@mail.gmail.com>
Hello!
> We have plenty of precedent in tree for interrupt controllers being
> compiled as arch-specific for reasons such as this. Can we just
> promote GIC to an obj-y (much the same way the KVM GIC or V7MNVIC are
> promoted)? You should them have access to cpu.h and the CP interface.
Huh, indeed, it's so simple... I failed to notice this.
Peter, what do you think, if we indeed simply move gicv3 implementation from common-obj-y to obj-y?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-10-27 12:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 7:46 [Qemu-devel] [PATCH v2] target-arm: Extract some external ARM CPU API Pavel Fedin
2015-10-26 16:39 ` Peter Crosthwaite
2015-10-27 12:02 ` Pavel Fedin [this message]
2015-10-27 13:41 ` Peter Maydell
2015-10-27 14:18 ` Pavel Fedin
2015-10-27 20:17 ` Peter Crosthwaite
2015-10-28 6:46 ` Pavel Fedin
2015-10-28 11:12 ` Pavel Fedin
2015-10-28 11:34 ` Shlomo Pongratz
2015-10-27 12:03 ` 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='013701d110af$5f601a70$1e204f50$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=crosthwaitepeter@gmail.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).