From: Julien Grall <julien.grall@linaro.org>
To: Vijay Kilari <vijay.kilari@gmail.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Prasun Kapoor <Prasun.Kapoor@caviumnetworks.com>,
Vijaya Kumar K <vijaya.kumar@caviumnetworks.com>,
xen-devel@lists.xen.org,
Stefano Stabellini <stefano.stabellini@citrix.com>
Subject: Re: [RFC PATCH] xen/arm: Add 4-level page table for stage 2 translation
Date: Mon, 05 May 2014 19:43:38 +0100 [thread overview]
Message-ID: <5367DBDA.4030706@linaro.org> (raw)
In-Reply-To: <CALicx6u405497bbgbaEzw2S6B6x0qbfAJH_EOAW6RQ+3ukBv-Q@mail.gmail.com>
Hi Vijay,
On 03/05/14 09:09, Vijay Kilari wrote:
> On Wed, Apr 30, 2014 at 6:09 PM, Julien Grall <julien.grall@linaro.org> wrote:
>> Hello Vijaya,
>>
>> On 04/30/2014 01:15 PM, vijay.kilari@gmail.com wrote:
>>> - first = __map_domain_page(p2m->first_level);
>>> - dump_pt_walk(first, addr);
>>> - unmap_domain_page(first);
>>> + lookup = __map_domain_page(p2m->lookup_level);
>>> + dump_pt_walk(lookup, addr);
>>
>> dump_pt_walk assume the table is the first level. I think you should
>> update dump_pt_walk to handle the zeroeth level.
>
> It was misguide by dump_hyp_walk(), which is passing zeroeth level
> to dump_pt_walk() for ARM64. Will update it
>
>>>
>>> -#define VADDR_BITS 32
>>> -#define VADDR_MASK (~0UL)
>>> -
>>
>> Why did you remove VADDR_{BITS,MASK}?
>
> It is not used at all. at least for ARM
From the commit message point of view, you are removing theses lines
without no reason.
IHMO, it should be part of another patch.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-05-05 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 12:15 [RFC PATCH] xen/arm: Add 4-level page table for stage 2 translation vijay.kilari
2014-04-30 12:39 ` Julien Grall
2014-05-02 16:12 ` Ian Campbell
2014-05-03 8:09 ` Vijay Kilari
2014-05-05 18:43 ` Julien Grall [this message]
2014-05-02 16:09 ` 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=5367DBDA.4030706@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=Prasun.Kapoor@caviumnetworks.com \
--cc=stefano.stabellini@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--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.