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
Cc: 'Peter Maydell' <peter.maydell@linaro.org>,
	'Claudio Fontana' <Claudio.Fontana@huawei.com>,
	'Shannon Zhao' <shannon.zhao@linaro.org>,
	christoffer.dall@linaro.org
Subject: Re: [Qemu-devel] [PATCH v2] Add virt-v3 machine that uses GIC-500
Date: Thu, 14 May 2015 18:27:02 +0300	[thread overview]
Message-ID: <004401d08e5a$6dcee1e0$496ca5a0$@samsung.com> (raw)
In-Reply-To: <B5C21809C482C148A58516F588CD431466EC4D@szxeml557-mbx.china.huawei.com>

 Hello!

> I wonder how it works for you. Do you aware of an alternative way to configure the clock
> irqflags for more then 24 cores, or is it just ignored.

 Unfortunately i don't know how it works. 

> My current status is as follows:
> With 64 cores there is no printouts what so ever.
> With 32 cores the boot usually get stuck after the message "[   45.719102] SCSI
subsystem
> initialized"
> With 24 cores the system noontimes complete the boot and sometimes get stuck like the 32
> cores system.

 I will recheck later when i get back to qemu. I will pull the latest HEAD and fix IRQ
affinity specification. But, i think that most likely you'll have to debug this yourself.
Because i suggest it will work. :)

>>  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.
> 
> I see but I guess that I want aarch64_cpu_initfn to be called and not arm_cpu_initfn.

 I guess that the correct class will be returned. Otherwise it would not work at all. You
can check this if you want to.

>>  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.
> 
> No, this is because I don't have an ARM64 based server needed for running KVM for ARM64.

 Ok. Then it looks like i'm going to be the first to do this. I hope you'll complete the
integration soon because vGICv3 has to be based upon your work.

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

  reply	other threads:[~2015-05-14 15:27 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
2015-05-14 12:01             ` Shlomo Pongratz
2015-05-14 15:27               ` Pavel Fedin [this message]
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='004401d08e5a$6dcee1e0$496ca5a0$@samsung.com' \
    --to=p.fedin@samsung.com \
    --cc=Claudio.Fontana@huawei.com \
    --cc=christoffer.dall@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=shannon.zhao@linaro.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).