On 03/01/2017 10:22 AM, Jan Beulich wrote:
On 01.03.17 at 06:39, wrote:
On 02/28/2017 10:51 PM, Andrew Cooper wrote:
On 28/02/17 19:50, Oleksandr Andrushchenko wrote:
I have a use-case when I may need to call __vmap for kernel provided
IPAs (read MFNs)
which may not be PAGE_SIZE aligned etc.
>>> On 01.03.17 at 06:39, wrote:
> On 02/28/2017 10:51 PM, Andrew Cooper wrote:
>> On 28/02/17 19:50, Oleksandr Andrushchenko wrote:
>>> I have a use-case when I may need to call __vmap for kernel provided
>>> IPAs (read MFNs)
>>>
>>> which may not be PAGE_SIZE aligned etc.
>>>
>>> The question is
On 02/28/2017 10:51 PM, Andrew Cooper wrote:
On 28/02/17 19:50, Oleksandr Andrushchenko wrote:
Hi, all!
I have a use-case when I may need to call __vmap for kernel provided
IPAs (read MFNs)
which may not be PAGE_SIZE aligned etc.
The question is if it is safe to call __vmap multiple times for
On 28/02/17 19:50, Oleksandr Andrushchenko wrote:
> Hi, all!
>
> I have a use-case when I may need to call __vmap for kernel provided
> IPAs (read MFNs)
>
> which may not be PAGE_SIZE aligned etc.
>
> The question is if it is safe to call __vmap multiple times for
> different IPAs
>
> sharing the s
Hi, all!
I have a use-case when I may need to call __vmap for kernel provided
IPAs (read MFNs)
which may not be PAGE_SIZE aligned etc.
The question is if it is safe to call __vmap multiple times for
different IPAs
sharing the same page (mfn), e.g. map something like 6ca00 0080 and
6ca00 0
