From: Julien Grall <julien.grall@linaro.org>
To: Suriyan Ramasami <suriyan.r@gmail.com>
Cc: keir@xen.org, Ian Campbell <ian.campbell@citrix.com>,
ian.jackson@eu.citrix.com, Tim Deegan <tim@xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [ARM:PATCH v1 1/1] Add Odroid-XU (Exynos5410) support
Date: Mon, 28 Jul 2014 13:53:30 +0100 [thread overview]
Message-ID: <53D647CA.8010502@linaro.org> (raw)
In-Reply-To: <CANoR_OBXV+xPe8vTiimtPDoo6AMqgW0GJOoFgGqBrKYb2fL2fQ@mail.gmail.com>
Hi Suriyan,
On 07/27/2014 07:12 PM, Suriyan Ramasami wrote:
>>
>>> I was wondering if dom0 is touching the physical CPUs by mistake (mainly
>>> because we map some regions used to control them).
>>> It might be worse to check that no cpufreq or power management is called
>>> on DOM0 at any time.
>>
> I shall dig into this some more.
> Thanks!
I would give a try with:
- Xen: 2 CPUs
- DOM0: 1 VCPU
- Guest: 1 VCPU
You can restrict the number of DOM0 VCPUs with dom0_max_vcpus=n where n
is the number of VCPUs for DOM0.
If it's not failing then the error is in Linux.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-07-28 12:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 22:47 [ARM:PATCH v1 1/1] Add Odroid-XU (Exynos5410) support Suriyan Ramasami
2014-07-25 8:18 ` Ian Campbell
2014-07-25 12:19 ` Julien Grall
2014-07-25 12:39 ` Ian Campbell
2014-07-25 17:45 ` Suriyan Ramasami
2014-07-25 20:05 ` Ian Campbell
2014-07-26 0:06 ` Suriyan Ramasami
2014-07-26 7:26 ` Suriyan Ramasami
2014-07-26 11:28 ` Julien Grall
2014-07-26 16:02 ` Suriyan Ramasami
2014-07-26 17:58 ` Julien Grall
2014-07-26 20:26 ` Suriyan Ramasami
2014-07-26 21:24 ` Julien Grall
2014-07-26 21:26 ` Julien Grall
2014-07-27 18:12 ` Suriyan Ramasami
2014-07-28 12:53 ` Julien Grall [this message]
2014-07-28 18:06 ` Suriyan Ramasami
2014-07-28 20:19 ` Suriyan Ramasami
2014-07-28 22:25 ` Suriyan Ramasami
2014-07-29 7:30 ` Ian Campbell
2014-07-29 15:49 ` Suriyan Ramasami
2014-07-29 17:36 ` Ian Campbell
2014-08-12 19:05 ` Suriyan Ramasami
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=53D647CA.8010502@linaro.org \
--to=julien.grall@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=suriyan.r@gmail.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
/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).