All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: "Chris (Christopher) Brand" <chris.brand@broadcom.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: "stefano.stabellini@citrix.com" <stefano.stabellini@citrix.com>,
	"Ian Campbell (ian.campbell@citrix.com)"
	<ian.campbell@citrix.com>
Subject: Re: [PATCH 2/2] xen: arm: Set all bits in mfn_to_xen_entry()
Date: Mon, 17 Aug 2015 12:03:30 -0700	[thread overview]
Message-ID: <55D23002.3040005@citrix.com> (raw)
In-Reply-To: <4EE5B48738DDED408878C97C8E050A8B1D7F02CF@SJEXCHMB05.corp.ad.broadcom.com>



On 17/08/2015 11:58, Chris (Christopher) Brand wrote:
> Hi Julien,
>
> Thanks for the review.
>
>>> +            .pxn = 0,
>>
>> I would add a comment to explain that this bit is reserved for PL2 stage
>> 1 page table.
>
> Will do.
>
>>> +            .avail = 0,
>>
>> I don't think this one is necessary. avail is not used by the hardware neither
>> Xen.
>
> "grep -rF pt.avail xen" gives 7 matches in xen/arch/arm/mm.c, so it is used by
> Xen (I'll fully admit that I didn't dig in to the "how and why" of its use).

Hmmm right. Sorry I haven't check the Xen code for that.

It's used for domheap mapping to know how many times it has been referenced.

>
>> what about *t fields (pxnt, xnt, apt,...)?
>
> I figured that as we're setting table to 0, these are ignored, and any code setting
> table to 1 should then set them. I can obviously easily set them here (I guess all
> to zero would make sense) if you think it's worthwhile ...

It was just an open question. :) I'm not sure what we should do with them.

Regards,

-- 
Julien Grall

      reply	other threads:[~2015-08-17 19:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14 21:42 [PATCH 2/2] xen: arm: Set all bits in mfn_to_xen_entry() Chris (Christopher) Brand
2015-08-17 18:49 ` Julien Grall
2015-08-17 18:58   ` Chris (Christopher) Brand
2015-08-17 19:03     ` Julien Grall [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=55D23002.3040005@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=chris.brand@broadcom.com \
    --cc=ian.campbell@citrix.com \
    --cc=stefano.stabellini@citrix.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.