qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Fedin <p.fedin@samsung.com>
To: 'Peter Crosthwaite' <crosthwaitepeter@gmail.com>,
	'Paolo Bonzini' <pbonzini@redhat.com>
Cc: 'Peter Maydell' <peter.maydell@linaro.org>,
	'Shlomo Pongratz' <shlomopongratz@gmail.com>,
	'QEMU Developers' <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: Wed, 28 Oct 2015 14:12:44 +0300	[thread overview]
Message-ID: <005b01d11171$92684a60$b738df20$@samsung.com> (raw)
In-Reply-To: <008501d1114c$60e0b1a0$22a214e0$@samsung.com>

 Hello!

>  Ok, so decided. I will convert my code, test the build and send a small patch for this soon,
> perhaps today.

 arm_gicv3_kvm.o is already in obj-y, and arm_gicv3_common.o does not use any of those definitions. So, nothing to move, there will be no patch.

 So far, we have only this small leftover: http://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg02349.html. Needed both by live migration and SW emulation of GICv3.

 Shlomo: Just add your GICv3 code to obj-$(CONFIG_ARM_GIC), and you'll be able to include things you need.

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

  reply	other threads:[~2015-10-28 11:12 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
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 [this message]
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='005b01d11171$92684a60$b738df20$@samsung.com' \
    --to=p.fedin@samsung.com \
    --cc=crosthwaitepeter@gmail.com \
    --cc=pbonzini@redhat.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).