From: Oleksandr Tyshchenko <olekstysh@gmail.com>
To: Julien Grall <julien@xen.org>
Cc: Oleksandr Andrushchenko <andr2000@gmail.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Elliott Mitchell <ehem+xen@m5p.com>,
xen-devel <xen-devel@lists.xenproject.org>,
"Roger Pau Monn??" <royger@freebsd.org>,
Mitchell Horne <mhorne@freebsd.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Artem Mygaiev <Artem_Mygaiev@epam.com>,
Anastasiia Lukianenko <Anastasiia_Lukianenko@epam.com>
Subject: Re: Uses of /hypervisor memory range (was: FreeBSD/Xen/ARM issues)
Date: Thu, 22 Jul 2021 23:41:31 +0300 [thread overview]
Message-ID: <CAPD2p-=KdztPCa1z=7oLFYxDroWvkVqo3XsV2f4dA0kO4SuwTA@mail.gmail.com> (raw)
In-Reply-To: <b9247885-8fc0-3a74-8f86-740997b4453e@xen.org>
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
On Sat, Jul 3, 2021 at 8:18 PM Julien Grall <julien@xen.org> wrote:
>
>
> On 18/06/2021 13:19, Oleksandr Andrushchenko wrote:
> > Hi, all!
>
> Hi,
>
Hello Julien, all.
[sorry for the possible format issues]
I am sorry to jump into the conversation too late.
>
> Sorry for the late reply.
>
> > What do we need in order to move on on this?
>
> The next steps would be
> 1) Write a PoC to confirm the approach is feasible
> 2) Write a design document
>
> Unfortunately, I will not have time to work on it any time soon. Is it
> something you plan to work on?
>
I am working on this PoC on Xen on Arm right now taking into the account
the details that we initially discussed on the IRC, unfortunately, I had to
postpone this activity several times due to the limited bandwidth,
but this time, I hope, I will be able to finish this PoC without
interruption) I will try to share Xen+Linux changes in a week, so we will
able to discuss them.
>
> Cheers,
>
> --
> Julien Grall
>
>
--
Regards,
Oleksandr Tyshchenko
[-- Attachment #2: Type: text/html, Size: 2249 bytes --]
prev parent reply other threads:[~2021-07-22 20:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YIhSbkfShjN/gMCe@Air-de-Roger>
[not found] ` <YIndyh0sRqcmcMim@mattapan.m5p.com>
[not found] ` <YIptpndhk6MOJFod@Air-de-Roger>
[not found] ` <YItwHirnih6iUtRS@mattapan.m5p.com>
[not found] ` <YIu80FNQHKS3+jVN@Air-de-Roger>
[not found] ` <YJDcDjjgCsQUdsZ7@mattapan.m5p.com>
[not found] ` <YJURGaqAVBSYnMRf@Air-de-Roger>
[not found] ` <YJYem5CW/97k/e5A@mattapan.m5p.com>
[not found] ` <YJs/YAgB8molh7e5@mattapan.m5p.com>
[not found] ` <54427968-9b13-36e6-0001-27fb49f85635@xen.org>
2021-05-14 2:42 ` Uses of /hypervisor memory range (was: FreeBSD/Xen/ARM issues) Elliott Mitchell
2021-05-14 8:32 ` Julien Grall
2021-05-14 10:07 ` Roger Pau Monné
2021-05-15 1:18 ` Elliott Mitchell
2021-05-15 10:08 ` Julien Grall
2021-05-19 23:25 ` Stefano Stabellini
2021-05-20 9:51 ` Julien Grall
2021-05-20 16:21 ` Stefano Stabellini
2021-06-18 12:19 ` Oleksandr Andrushchenko
2021-07-03 17:17 ` Julien Grall
2021-07-22 20:41 ` Oleksandr Tyshchenko [this message]
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='CAPD2p-=KdztPCa1z=7oLFYxDroWvkVqo3XsV2f4dA0kO4SuwTA@mail.gmail.com' \
--to=olekstysh@gmail.com \
--cc=Anastasiia_Lukianenko@epam.com \
--cc=Artem_Mygaiev@epam.com \
--cc=andr2000@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=ehem+xen@m5p.com \
--cc=julien@xen.org \
--cc=mhorne@freebsd.org \
--cc=royger@freebsd.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).