qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Fedin <p.fedin@samsung.com>
To: "'Hower, Derek'" <dhower@qti.qualcomm.com>
Cc: 'Shlomo Pongratz' <shlomo.pongratz@huawei.com>,
	'Shlomo Pongratz' <shlomopongratz@gmail.com>,
	"'Cain III, Trey'" <tcain@qti.qualcomm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu-devel Digest, Vol 148, Issue 729
Date: Sun, 19 Jul 2015 16:36:56 +0300	[thread overview]
Message-ID: <00d801d0c227$fbe42390$f3ac6ab0$@samsung.com> (raw)
In-Reply-To: <c943ca0d9d0d429e995041d6915cae1b@NASANEXM01B.na.qualcomm.com>

 Hello!

> We are excited to see the GICv3 patches making progress. Thanks for putting in the effort.

 Thank you :)

>  I see in your message below that software emulation is not supported yet. I was wondering if you
could
> elaborate on what the issues are preventing GICv3 in TCG mode? Is it something fundamental, a lack
of
> testing, etc.?

 Actually, software emulation is developed by Shlomo Pongratz, not me. I do some basic testing and i
would say that it works fine. The last known problem for me is that Peter Maydell doesn't want to
review the huge .c file with SW GICv3 implementation:
http://lists.nongnu.org/archive/html/qemu-devel/2015-07/msg00634.html And i don't have time to take
this over from Shlomo, because actually this is out of scope of my project.
 Recently Shlomo told that he will continue to work on it. We agreed during the discussion that he
will handle all isues related to the emulation itself, while my job is integration + KVM. So my next
series come without TCG part.

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

           reply	other threads:[~2015-07-19 13:37 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <c943ca0d9d0d429e995041d6915cae1b@NASANEXM01B.na.qualcomm.com>]

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='00d801d0c227$fbe42390$f3ac6ab0$@samsung.com' \
    --to=p.fedin@samsung.com \
    --cc=dhower@qti.qualcomm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shlomo.pongratz@huawei.com \
    --cc=shlomopongratz@gmail.com \
    --cc=tcain@qti.qualcomm.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).