From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <ian.campbell@citrix.com>,
Vijay Kilari <vijay.kilari@gmail.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Prasun Kapoor <Prasun.Kapoor@caviumnetworks.com>,
Vijaya Kumar K <vijaya.kumar@caviumnetworks.com>,
Tim Deegan <tim@xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
manish.jaggi@caviumnetworks.com
Subject: Re: [PATCH v1] xen/arm: Do not allocate pte entries for MAP_SMALL_PAGES
Date: Tue, 03 Mar 2015 11:17:39 +0000 [thread overview]
Message-ID: <54F59853.4070109@linaro.org> (raw)
In-Reply-To: <1425378478.24959.71.camel@citrix.com>
Hi Ian,
On 03/03/2015 10:27, Ian Campbell wrote:
> On Tue, 2015-03-03 at 13:28 +0530, Vijay Kilari wrote:
>> On Tue, Feb 24, 2015 at 6:29 PM, Julien Grall <julien.grall@linaro.org> wrote:
>>> On 24/02/15 10:26, Ian Campbell wrote:
>>>> On Tue, 2015-02-24 at 09:38 +0000, Julien Grall wrote:
>>>>> Hi Ian,
>>>>>
>>>>> On 24/02/2015 09:31, Ian Campbell wrote:
>>>>>> On Wed, 2015-02-18 at 13:03 +0000, Julien Grall wrote:
>>>>>>>> + {
>>>>>>>> + pte = mfn_to_xen_entry(mfn, (ai & 0xffff));
>>>>>>>
>>>>>>> Please introduce a new macro for the mask.
>>>>>>
>>>>>> Better would be a pte_foo accessor, similar (if not identical) to x86's
>>>>>> pte_get_flags. So pte_get_flags(ai) or so.
>>>>>
>>>>> I'm not able to find a such function in x86. Did you intend to mean
>>>>> pte_flags_to_cacheattr?
>>>>
>>>> It's actually get_pte_flags.
>>>>
>>>>> In another side, using PTE_PRESENT would require to introduce a
>>>>> PAGE_AVAIL0 (or smth similar).
>>>>
>>>> Why?
>>>
>>> If we have only a bit PTE_PRESENT, how do you define MAP_SMALL_PAGES?
>>
>> MAP_SMALL_PAGES is already defined as WRITE_ALLOC which occupies lower 3 bits
>> what is need for PAGE_AVAIL0?
>>
>> Below definitions should suffice?
>
> I think so. You don't need the ()s around DEV_* and WRITE_ALLOC etc in
> the PAGE_* definitions.
I'm not sure to follow here. Do you think MAP_SMALL_PAGES should be
defined as WRITE_ALLOC?
> A comment on the format of the bit packing done here would also be
> useful e.g. "16: present\n2:0: pte attributes field" in a little block
> comment above this stuff, below the DEV_* stuff.
>
> PAGE_PRESENT might be more in keepign that PTE_PRESENT, since this isn't
> a PTE bit pattern.
Sounds good to me.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-03-03 11:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 12:56 [PATCH v1] xen/arm: Do not allocate pte entries for MAP_SMALL_PAGES vijay.kilari
2015-02-18 13:03 ` Julien Grall
2015-02-24 9:31 ` Ian Campbell
2015-02-24 9:38 ` Julien Grall
2015-02-24 10:17 ` Jan Beulich
2015-02-24 10:26 ` Ian Campbell
2015-02-24 12:59 ` Julien Grall
2015-02-24 13:13 ` Ian Campbell
2015-02-24 13:47 ` Julien Grall
2015-02-24 13:54 ` Jan Beulich
2015-03-03 7:58 ` Vijay Kilari
2015-03-03 10:27 ` Ian Campbell
2015-03-03 11:17 ` Julien Grall [this message]
2015-03-03 11:47 ` Ian Campbell
2015-03-03 11:51 ` Julien Grall
2015-03-03 11:57 ` Ian Campbell
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=54F59853.4070109@linaro.org \
--to=julien.grall@linaro.org \
--cc=Prasun.Kapoor@caviumnetworks.com \
--cc=ian.campbell@citrix.com \
--cc=manish.jaggi@caviumnetworks.com \
--cc=stefano.stabellini@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=vijay.kilari@gmail.com \
--cc=vijaya.kumar@caviumnetworks.com \
--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.