All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
To: Ian Campbell <Ian.Campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	Julien Grall <julien.grall@linaro.org>
Cc: Joel Schopp <joel.schopp@amd.com>,
	xen-devel <xen-devel@lists.xen.org>,
	"Hurwitz, Sherry" <sherry.hurwitz@amd.com>
Subject: Xen on Seattle
Date: Tue, 2 Sep 2014 01:01:08 -0500	[thread overview]
Message-ID: <54055D24.60406@amd.com> (raw)

Hi all,

I am running into an issue booting Xen on Seattle platform where dom0 
kernel failed to make the following hypercall in 
arch/arm/xen/enlighten.c: xen_percpu_init().

  HYPERVISOR_vcpu_op(VCPUOP_register_vcpu_info, cpu, &info)

After investigation, the hypercall failed in the xen/common/domain.c: 
map_vcpu_info(), where it check

     if ( offset > (PAGE_SIZE - sizeof(vcpu_info_t)) )
         return -EINVAL;

Here:

(XEN) DEBUG0: map_vcpu_info: offset = 0x6790
(XEN) DEBUG0: map_vcpu_info: PAGE_SIZE = 0x1000
(XEN) DEBUG0: map_vcpu_info: sizeof(vcpu_info_t) = 0x30

If I understand correctly, it seems that the hypervisor is making 
assumption that the Dom0 guest is using 4K page size.  The PAGE_SHIFT in 
include/asm-arm/config.h is currently set to 12.  So, I have tried 
changing this to 16 (for 64K page). However, there is a restriction on 
the 16-bit value of the struct active_grant_entry { length:16; }. So, I 
cannot boot dom0 with 64K page size. Is this accurate?

Thanks,

Suravee

             reply	other threads:[~2014-09-02  6:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02  6:01 Suravee Suthikulanit [this message]
2014-09-02 18:06 ` Xen on Seattle Stefano Stabellini
2014-09-02 18:10   ` Suravee Suthikulanit
2014-09-02 18:15     ` Stefano Stabellini
2014-09-02 18:31       ` Suravee Suthikulanit
2014-09-02 18:33         ` Stefano Stabellini
2014-09-10 22:38         ` Suravee Suthikulanit
2014-09-10 23:00           ` Julien Grall
2014-09-11  0:36             ` Suravee Suthikulanit
2014-09-11  1:24               ` Stefano Stabellini
2014-09-03  9:51       ` Ian Campbell

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=54055D24.60406@amd.com \
    --to=suravee.suthikulpanit@amd.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=joel.schopp@amd.com \
    --cc=julien.grall@linaro.org \
    --cc=sherry.hurwitz@amd.com \
    --cc=stefano.stabellini@citrix.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.