qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Fedin <p.fedin@samsung.com>
To: 'Shlomo Pongratz' <shlomo.pongratz@huawei.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] Add virt-v3 machine that uses GIC-500
Date: Wed, 13 May 2015 16:57:18 +0300	[thread overview]
Message-ID: <006901d08d84$ba7f0370$2f7d0a50$@samsung.com> (raw)
In-Reply-To: <B5C21809C482C148A58516F588CD431466E704@szxeml557-mbx.china.huawei.com>

 Hello!

> 1. In fdt_add_timer why you didn't used the 24 bit limit I posed on the irqflags? Please
note that
> the argument is 32 bits wide and 8 bits are for flags.

  Simply missed it when checking for differences. Please fix. :) Perhaps it is the reason
why >=24 CPUs fail for you.

> 2. In machvirt_init, I used TYPE_AARCH64_CPU while you reverted it to TYPE_ARM_CPU, I
> assume this is because you want to support cortex-a15. Don't you think It should be
according
> to the cortex type?

 Yes, i just left it as it was because it already works fine with ARM64. Actually,
TYPE_AARCH64_CPU is a subclass of TYPE_ARM_CPU.

> (BTW you removed cortex-a53).

 Yes, because i didn't see how it is different from a57 (or a15). I tried to follow
minimal intervention principle.
 But perhaps i was wrong because there was real support for a53 added recently:
http://lists.nongnu.org/archive/html/qemu-devel/2015-05/msg01304.html, so feel free to
re-add it back.

 BTW, just for interest, have you tried to do anything with KVM support of vGICv3? I have
some code but it's inherently unstable and lock up for unknown (yet) reason.

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

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

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08 13:09 [Qemu-devel] [PATCH v2] Add virt-v3 machine that uses GIC-500 Pavel Fedin
2015-05-11 11:30 ` Shlomo Pongratz
2015-05-12  9:05   ` Pavel Fedin
2015-05-12 11:29     ` Shlomo Pongratz
2015-05-12 12:33       ` Pavel Fedin
2015-05-13 10:34         ` Shlomo Pongratz
2015-05-13 13:57           ` Pavel Fedin [this message]
2015-05-14 12:01             ` Shlomo Pongratz
2015-05-14 15:27               ` Pavel Fedin
2015-05-12  9:11   ` Pavel Fedin
2015-05-12  9:20 ` Daniel P. Berrange
2015-05-12  9:32   ` Pavel Fedin
2015-05-12  9:56   ` Peter Maydell
2015-05-12 11:15     ` Pavel Fedin
2015-05-12 11:20       ` Daniel P. Berrange

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='006901d08d84$ba7f0370$2f7d0a50$@samsung.com' \
    --to=p.fedin@samsung.com \
    --cc=qemu-devel@nongnu.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 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).