From: Julien Grall <julien.grall@arm.com>
To: Andrii Anisov <andrii.anisov@gmail.com>,
Stefano Stabellini <sstabellini@kernel.org>
Cc: "LOPEZ, FUENTES NACARINO Jairo Eduardo" <jairo@ruri.waseda.jp>,
xen-devel@lists.xen.org
Subject: Re: RT Xen on ARM - R-Car series
Date: Fri, 1 Feb 2019 11:06:28 +0000 [thread overview]
Message-ID: <9a86cf3c-8b08-c167-1070-06e97ac54169@arm.com> (raw)
In-Reply-To: <59125e8b-729b-f16d-e873-fffe6458f463@gmail.com>
On 2/1/19 10:35 AM, Andrii Anisov wrote:
> Hello,
Hi,
>
> On 01.02.19 12:12, Julien Grall wrote:
>> This is actually a shared page, the page is allocated by the domain
>> and shared with Xen. So what do you mean?
>
> I'm curious if it can be allocated on hypervisor side.
There are very limited case where the hypervisor is allocating memory to
share with the guest. In general, we want to account the memory to the
guest, so the best way is to let the guest provide the buffer.
In that case this will not help because the hypercall is taking a
virtual address (not a guest virtual frame, nor guest physical frame!).
So the buffer can span across the page-boundary or even have the mapping
changed.
We can possibly add a restriction on the mapping not changing (pending
investigation). But I think requesting the address to be page-aligned is
going to be hard because the runstate is not filling a page.
For instance, Linux is using a per-cpu variable for that. I am not
entirely sure whether it promise the structure will never cross a
page-boundary.
>
>> That's not a link but a Message-ID. You can either use your favorite
>> client for looking the e-mail
>
> It only works if you have it in the current mailbox, I guess.
That's correct.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-02-01 11:06 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACrvCsaeHuwzZzUQTzNYF7fqmgQWNJUVOQZv9D0MnYrXjqzZtQ@mail.gmail.com>
2018-12-22 12:21 ` RT Xen on ARM - R-Car series Andrii Anisov
2018-12-25 16:07 ` LOPEZ, FUENTES NACARINO Jairo Eduardo
2018-12-27 11:07 ` Andrii Anisov
2018-12-28 15:22 ` LOPEZ, FUENTES NACARINO Jairo Eduardo
2018-12-28 8:28 ` Andrii Anisov
2018-12-28 8:32 ` Andrii Anisov
2018-12-28 8:39 ` Andrii Anisov
2019-01-04 9:09 ` LOPEZ, FUENTES NACARINO Jairo Eduardo
2019-01-08 17:04 ` LOPEZ, FUENTES NACARINO Jairo Eduardo
2019-01-11 20:12 ` LOPEZ, FUENTES NACARINO Jairo Eduardo
2019-01-14 8:42 ` Andrii Anisov
2019-01-16 7:53 ` Andrii Anisov
2019-01-21 18:04 ` LOPEZ, FUENTES NACARINO Jairo Eduardo
[not found] ` <CACrvCsZB-tps6=Vr=1Phf5oo5eUReabMLJzkbO3d2hmNLDOxww@mail.gmail.com>
[not found] ` <7e217489-2c1a-c35f-d51f-0969654aa8cc@gmail.com>
[not found] ` <CACrvCsaYJ-zGkZwfdV7BXDABW8u_EDQetU3pq+2otRGXWTXagw@mail.gmail.com>
[not found] ` <4d078801-b804-06e7-ad5c-8032b1dbaa84@gmail.com>
2019-01-28 17:20 ` LOPEZ, FUENTES NACARINO Jairo Eduardo
2019-01-28 8:25 ` Andrii Anisov
2019-01-29 15:30 ` LOPEZ, FUENTES NACARINO Jairo Eduardo
2019-01-29 13:29 ` Andrii Anisov
2019-01-30 20:23 ` LOPEZ, FUENTES NACARINO Jairo Eduardo
2019-01-30 12:12 ` Julien Grall
2019-01-31 11:22 ` Andrii Anisov
2019-01-31 11:37 ` Julien Grall
2019-01-31 12:00 ` Andrii Anisov
2019-01-31 12:20 ` Julien Grall
2019-01-31 21:56 ` Stefano Stabellini
2019-01-31 23:14 ` Julien Grall
2019-02-01 10:02 ` Andrii Anisov
2019-02-01 10:12 ` Julien Grall
2019-02-01 10:35 ` Andrii Anisov
2019-02-01 11:06 ` Julien Grall [this message]
2019-02-01 16:53 ` Roger Pau Monné
2019-02-01 17:40 ` Julien Grall
2019-02-04 10:28 ` Andrii Anisov
2019-02-04 11:21 ` Julien Grall
2019-02-04 14:46 ` Andrii Anisov
2019-02-04 15:05 ` Julien Grall
2019-02-04 12:53 ` Roger Pau Monné
2019-02-04 21:58 ` Julien Grall
2019-02-05 8:40 ` Andrii Anisov
2019-02-05 9:45 ` Roger Pau Monné
2019-02-05 9:54 ` Andrii Anisov
2019-02-05 10:10 ` Roger Pau Monné
2019-02-06 20:20 ` Andrii Anisov
2019-02-06 21:03 ` Stefano Stabellini
2019-02-07 9:42 ` Andrii Anisov
2019-02-07 10:35 ` Roger Pau Monné
2019-02-07 10:59 ` Julien Grall
2019-02-12 18:21 ` Andrii Anisov
2019-02-12 19:21 ` Julien Grall
2019-02-14 14:18 ` Andrii Anisov
2019-02-14 17:29 ` Julien Grall
2019-02-15 11:30 ` Andrii Anisov
2019-02-15 17:13 ` Julien Grall
2019-02-15 17:41 ` Andrii Anisov
2019-02-16 8:42 ` Julien Grall
2019-02-12 18:21 ` Andrii Anisov
2019-02-14 16:29 ` Roger Pau Monné
2019-02-15 15:21 ` Andrii Anisov
2019-02-15 16:31 ` Julien Grall
2019-02-15 17:30 ` Andrii Anisov
2019-02-15 18:36 ` Julien Grall
2019-02-14 17:08 ` Julien Grall
2019-02-05 9:26 ` Roger Pau Monné
2019-02-01 10:07 ` Andrii Anisov
2019-02-01 10:16 ` Julien Grall
2019-02-01 10:35 ` Andrii Anisov
2019-02-01 10:51 ` Julien Grall
2019-02-01 18:00 ` Stefano Stabellini
2019-02-04 10:32 ` Andrii Anisov
2019-02-04 11:36 ` Julien Grall
2019-02-04 15:19 ` Andrii Anisov
2019-02-04 22:06 ` Julien Grall
2019-02-05 9:01 ` Andrii Anisov
2019-02-05 19:18 ` Stefano Stabellini
2019-02-07 10:53 ` Andrii Anisov
[not found] ` <CACrvCsbkFG=3To83qi7xxmtmgC_9PKvuLz73edhiaV7TsJAZqQ@mail.gmail.com>
2019-01-31 12:24 ` Julien Grall
2019-01-16 20:46 ` Andrii Anisov
2019-01-16 7:40 ` Andrii Anisov
2019-01-17 2:08 ` LOPEZ, FUENTES NACARINO Jairo Eduardo
2018-12-28 17:35 ` LOPEZ, FUENTES NACARINO Jairo Eduardo
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=9a86cf3c-8b08-c167-1070-06e97ac54169@arm.com \
--to=julien.grall@arm.com \
--cc=andrii.anisov@gmail.com \
--cc=jairo@ruri.waseda.jp \
--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 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.