xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: "Chris (Christopher) Brand" <chris.brand@broadcom.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 2/2 v2] xen: arm: Set all bits in mfn_to_xen_entry()
Date: Fri, 21 Aug 2015 16:45:33 -0700	[thread overview]
Message-ID: <55D7B81D.5080502@citrix.com> (raw)
In-Reply-To: <4EE5B48738DDED408878C97C8E050A8B1D7F40D2@SJEXCHMB05.corp.ad.broadcom.com>



On 21/08/2015 12:47, Chris (Christopher) Brand wrote:
> Hi Andrew,
>
>> On 21/08/15 00:33, Chris Brand wrote:
>>> Ensure that every bit has a specific value.
>>>
>>> Reported-by: Julien Grall <julien.grall@citrix.com>
>>> Signed-off-by: Chris Brand <chris.brand@broadcom.com>
>>> ---
>>> v2 adds comments on pxn and avail.
>>
>> This is no functional change, if the compiler is conforming to the C spec.
>>
>> The spec guarantees that structure initialisation like this causes unspecified
>> names to gain their default value.  As these are integer bitfields, the default
>> value is 0.
>>
>> What compiler is in use?  It would appear that it is buggy, or at least has
>> buggy scalar replacement optimisations.
>
> That's right. I'd forgotten about that. This was actually suggested by Julien in
> a review of another patch I sent. I haven't seen any problems this fixes.

I still think those patches are valid in order to know which value are 
set by default and what does it mean.

Regards,

-- 
Julien Grall

  reply	other threads:[~2015-08-21 23:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 23:33 [PATCH 0/2 v2] xen: arm: Ensure all PTE bits have a known value Chris Brand
2015-08-20 23:33 ` [PATCH 1/2 v2] xen: arm re-order assignments in mfn_to_xen_entry() Chris Brand
2015-09-01 15:51   ` Ian Campbell
2015-08-20 23:33 ` [PATCH 2/2 v2] xen: arm: Set all bits " Chris Brand
2015-08-21 13:39   ` Andrew Cooper
2015-08-21 19:47     ` Chris (Christopher) Brand
2015-08-21 23:45       ` Julien Grall [this message]
2015-09-01 15:50   ` 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=55D7B81D.5080502@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=chris.brand@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).