From: bharat gohil <ghl.bhrt@gmail.com>
To: Julien Grall <julien.grall@arm.com>
Cc: Oleksandr Tyshchenko <olekstysh@gmail.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Andrii Anisov <andrii_anisov@epam.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Xen Devel <xen-devel@lists.xen.org>
Subject: Re: ARM64:Porting xen to new hardware
Date: Tue, 3 Oct 2017 12:35:14 +0530 [thread overview]
Message-ID: <CABdg74cugG=EyNOWKZ1SJrHcstOFTV5nnyRmqtz2bC08xtFXvw@mail.gmail.com> (raw)
In-Reply-To: <7125b13d-aaea-0578-8a85-8e75e2abbe45@arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 4414 bytes --]
On Fri, Sep 29, 2017 at 11:12 PM, Julien Grall <julien.grall@arm.com> wrote:
>
>
> On 09/29/2017 09:15 AM, bharat gohil wrote:
>
>> Hello
>>
>
> Hi,
>
> Please avoid top-posting.
>
> The patch didn't work in my case.
>>
>
> The patch will be useful only if the compatible string in the DT of your
> UART is "snps,dw-apb-uart". What is the compatible string for it?
>
In my case, compatible string is "ns16550a".
Thanks,
>
> Cheers,
>
> Thanks,
>> Bharat
>>
>> On Mon, Sep 25, 2017 at 11:38 PM, Oleksandr Tyshchenko <
>> olekstysh@gmail.com <mailto:olekstysh@gmail.com>> wrote:
>>
>> Hi, Bharat
>>
>> On Mon, Sep 25, 2017 at 8:40 PM, bharat gohil <ghl.bhrt@gmail.com
>> <mailto:ghl.bhrt@gmail.com>> wrote:
>>
>> >
>> >
>> > On 25-Sep-2017 6:59 PM, "Julien Grall" <julien.grall@arm.com
>> <mailto:julien.grall@arm.com>> wrote:
>> >
>> > Hi,
>> >
>> > I am using same setup.
>> > It just my guess because no response to key ctrl+a input.
>> >
>> > SoC has 8250 compitible UART.I will print character in receive
>> handler of
>> > UART in Xen. Do we have any other hook test this?
>>
>> Maybe you got stuck in the UART interrupt handler. Can you recheck?
>>
>> If so, can you take a look at the patch which has been posted
>> recently:
>> https://patchwork.kernel.org/patch/9959003/
>> <https://patchwork.kernel.org/patch/9959003/>
>>
>> >
>> > One more thing, is big-little supported in xen?
>> > How Xen distribute load among the CPUs or Xen only run in context
>> of the
>> > guest only?
>> > In my setup Dom0 use energy aware scheduler.
>> >
>> > Thanks,
>> > Bharat
>> >
>> >
>> > On 09/25/2017 01:53 PM, bharat gohil wrote:
>> >>
>> >> Hello Andrii,
>> >>
>> >> I tried but no success.
>> >> It looks, Xen is not running.
>> >
>> >
>> > I am a bit confused... on one of the previous e-mail you posted
>> log from
>> > Xen:
>> >
>> > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to
>> switch input to
>> > Xen)
>> >
>> > (XEN) Freed 272kB init memory.
>> >
>> > So unless you have a completely new setup, Xen is definitely
>> running.
>> > However, what may happen is the serial driver in Xen does not
>> receive input
>> > characters.
>> >
>> > One of the first test would be to check whether the driver
>> effectively
>> > receive characters.
>> >
>> > Cheers,
>> >
>> >>
>> >> Thanks,
>> >> Bharat
>> >>
>> >>
>> >> On Mon, Sep 25, 2017 at 5:45 PM, Andrii Anisov
>> <andrii_anisov@epam.com <mailto:andrii_anisov@epam.com>
>> >> <mailto:andrii_anisov@epam.com <mailto:andrii_anisov@epam.com>>>
>> wrote:
>> >>
>> >> Hello Bharat,
>> >>
>> >>
>> >> On 25.09.17 11:42, bharat gohil wrote:
>> >>
>> >> Hello Wilk,
>> >>
>> >> I had try Ctrl+a three times and 'd' but no dump on the
>> serial
>> >> console.
>> >>
>> >> Its a way to switch to XEN debug console. In case you are
>> using
>> >> minicom, you should press Ctrl+A six times, then you will
>> see the
>> >> line like following:
>> >> (XEN) *** Serial input -> Xen (type 'CTRL-a' three times
>> to
>> >> switch input to DOM0)
>> >>
>> >> Then you can press 'h' for seeing installed key handlers.
>> >>
>> >> But all of this requires XEN to be running somehow.
>> >>
>> >> --
>> >> *Andrii Anisov*
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Regards,
>> >> Bharat Gohil
>> >> Sr.Software Engineer
>> >> bharat.gohil@harman.com <mailto:bharat.gohil@harman.com>
>> <mailto:bharat.gohil@harman.com <mailto:bharat.gohil@harman.com>>
>> >> +919427054633 <tel:%2B919427054633>
>> >
>> >
>> > --
>> > Julien Grall
>> >
>> >
>>
>>
>>
>> --
>> Regards,
>>
>> Oleksandr Tyshchenko
>>
>>
>>
>>
>> --
>> Regards,
>> Bharat Gohil
>> Sr.Software Engineer
>> bharat.gohil@harman.com <mailto:bharat.gohil@harman.com>
>> +919427054633
>>
>
> --
> Julien Grall
>
--
Regards,
Bharat Gohil
Sr.Software Engineer
bharat.gohil@harman.com
+919427054633
[-- Attachment #1.2: Type: text/html, Size: 8298 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-10-03 7:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 14:21 ARM64:Porting xen to new hardware bharat gohil
2017-08-30 14:14 ` Oleksandr Tyshchenko
2017-08-30 14:30 ` bharat gohil
2017-08-31 11:13 ` bharat gohil
2017-08-31 11:58 ` Oleksandr Tyshchenko
2017-09-04 4:13 ` bharat gohil
2017-09-04 12:54 ` Oleksandr Tyshchenko
2017-09-06 7:01 ` bharat gohil
2017-09-06 10:19 ` Oleksandr Tyshchenko
2017-09-07 13:30 ` bharat gohil
2017-09-08 19:19 ` Oleksandr Tyshchenko
2017-09-18 14:46 ` Konrad Rzeszutek Wilk
2017-09-22 10:00 ` bharat gohil
2017-09-22 13:43 ` Konrad Rzeszutek Wilk
2017-09-25 8:42 ` bharat gohil
2017-09-25 12:15 ` Andrii Anisov
2017-09-25 12:53 ` bharat gohil
2017-09-25 13:29 ` Julien Grall
2017-09-25 17:40 ` bharat gohil
2017-09-25 18:08 ` Oleksandr Tyshchenko
2017-09-29 8:15 ` bharat gohil
2017-09-29 17:42 ` Julien Grall
2017-10-03 7:05 ` bharat gohil [this message]
2017-10-06 13:29 ` Julien Grall
2018-02-22 8:43 ` bharat gohil
2018-02-22 9:45 ` bharat gohil
2018-02-22 10:33 ` bharat gohil
2018-02-22 10:38 ` bharat gohil
2018-02-22 11:01 ` Andrii Anisov
2018-02-22 11:20 ` Julien Grall
2018-02-22 11:11 ` Andrii Anisov
2018-02-22 11:27 ` Julien Grall
2018-02-26 7:31 ` bharat gohil
2018-02-26 10:21 ` Julien Grall
2018-02-26 13:09 ` bharat gohil
2017-09-25 13:30 ` Andrii Anisov
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='CABdg74cugG=EyNOWKZ1SJrHcstOFTV5nnyRmqtz2bC08xtFXvw@mail.gmail.com' \
--to=ghl.bhrt@gmail.com \
--cc=andrii_anisov@epam.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=olekstysh@gmail.com \
--cc=sstabellini@kernel.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).