From: "Goel, Sameer" <sgoel@codeaurora.org>
To: xen-devel@lists.xen.org
Subject: Re: Xen on Qualcomm
Date: Wed, 2 Nov 2016 14:37:47 -0600 [thread overview]
Message-ID: <8102e4ae-a9aa-a5e3-aa91-3533f9f80b7f@codeaurora.org> (raw)
In-Reply-To: <CAHdG6+yOFZuGZCetRVYNkeRpSAD0kJFaNrU4A3RCom3i5nQ_7Q@mail.gmail.com>
Can you please post the error and details on Xen you are using?
Thanks,
Sameer
On 11/2/2016 3:04 AM, Suresh Kanzariya wrote:
> Hi,
>
> I am trying to run Xen on Qualcomm 410 platform.
>
> I have come across below link
> https://lists.xenproject.org/archives/html/xen-devel/2016-03/msg03144.html
>
> which suggest a patch to fix Xen crashes on Qualcomm Technology, So does
> anyone has any information on the post support which Qualcomm Platform?
>
> Thanks in advance.
>
> Regards,
> Suresh
>
>
>
>
> On Tue, 1 Nov 2016 at 11:48 Suresh Kanzariya <skanzariya@gmail.com
> <mailto:skanzariya@gmail.com>> wrote:
>
> Hi Julien,
>
> Thanks for the information. Let me get some more information on
> this, and I will get back to the mailing-list for further information.
>
> Thanks,
> Suresh
>
> On Mon, Oct 31, 2016 at 8:34 PM, Julien Grall <julien.grall@arm.com
> <mailto:julien.grall@arm.com>> wrote:
>
>
>
> On 31/10/16 14:59, Suresh Kanzariya wrote:
>
> Hi Julien,
>
>
> Hi,
>
> It seems that I forgot to add xen-devel on CC in my answer.
> Sorry for that.
>
> Thanks for the information.
>
> Just wanted to understand that Qualcomm boot itself contains a
> Hypervisor and also Xen is also a hypervisor, so I am not
> sure Xen
> hypervisor directly fits into the design, I guess Qualcomm
> hypervisor
> need modification or remove completely to support xen. It
> will be
> great if you can spread some light on this.
>
>
> Indeed 2 hypervisors cannot cooperate on the same processor. If
> Qualcomm provides any hypervisor, you would have to remove it.
>
> Although, I don't know much this platform, so I would recommend
> to contact Qualcomm for anything regarding that.
>
> Regards,
>
> --
> Julien Grall
>
>
> --
> Regards,
> Suresh
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
>
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-02 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 9:42 Xen on Qualcomm Suresh Kanzariya
[not found] ` <d75f7c7a-ecd9-5b57-3781-d9dd7a576f37@arm.com>
[not found] ` <CAHdG6+z+unY18M7vfx2t=64q_zHjXVZ1KR0fL+yBJOEA7yM1zw@mail.gmail.com>
2016-10-31 15:04 ` Julien Grall
2016-11-01 6:18 ` Suresh Kanzariya
2016-11-02 9:04 ` Suresh Kanzariya
2016-11-02 20:37 ` Goel, Sameer [this message]
2016-11-03 9:05 ` Julien Grall
2016-11-03 10:39 ` Suresh Kanzariya
2016-11-07 12:39 ` Suresh Kanzariya
2016-11-07 15:24 ` Julien Grall
2016-11-08 6:44 ` Suresh Kanzariya
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=8102e4ae-a9aa-a5e3-aa91-3533f9f80b7f@codeaurora.org \
--to=sgoel@codeaurora.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).