From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
Shanker Donthineni <shankerd@codeaurora.org>
Cc: Julien Grall <julien.grall@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Philip Elcan <pelcan@codeaurora.org>,
Vikram Sethi <vikrams@codeaurora.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] xen: arm: zero EL2 pagetable pages before use
Date: Fri, 11 Mar 2016 13:24:57 +0000 [thread overview]
Message-ID: <56E2C729.9020607@citrix.com> (raw)
In-Reply-To: <56E2D28002000078000DB9B0@prv-mh.provo.novell.com>
On 11/03/16 13:13, Jan Beulich wrote:
>>>> On 11.03.16 at 13:56, <andrew.cooper3@citrix.com> wrote:
>> On 11/03/16 11:29, Jan Beulich wrote:
>>>>>> On 10.03.16 at 23:00, <shankerd@codeaurora.org> wrote:
>>>> @@ -771,6 +772,7 @@ void __init setup_frametable_mappings(paddr_t ps, paddr_t pe)
>>>> nr_second = frametable_size >> SECOND_SHIFT;
>>>> second_base = alloc_boot_pages(nr_second, 1);
>>>> second = mfn_to_virt(second_base);
>>>> + memset(second, 0, nr_second * PAGE_SIZE);
>>>> for ( i = 0; i < nr_second; i++ )
>>>> {
>>>> pte = mfn_to_xen_entry(second_base + i, WRITEALLOC);
>>> Along those lines here - use clear_page(), presumably by moving it
>>> into the loop.
>> This need only initialise the entries which are not filled by the loop,
>> which will only be the rounding size up to the next 2M or 32M boundary.
>>
>> Most of the content of 'second' is explicitly initialised, so zeroing it
>> all first is redundant.
> Well, I certainly don't know all the details of how this works on
> ARM, but the way I remember the original problem description
> (sent a few days ago) the problem was with bogus translations
> to be visible transiently. Of course all depends on whether the
> page tables that are being modified here are live ones, which
> I simply don't know.
Looking at the code here, second is hooked into the live pagetables
immediately after the loop. Therefore, bogus translations will only be
present for the untouched PTEs which make up the alignment space.
However, it is probably best to defer to the ARM maintainers.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-03-11 13:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 22:00 [PATCH] xen: arm: zero EL2 pagetable pages before use Shanker Donthineni
2016-03-11 11:29 ` Jan Beulich
2016-03-11 12:56 ` Andrew Cooper
2016-03-11 13:13 ` Jan Beulich
2016-03-11 13:24 ` Andrew Cooper [this message]
2016-03-12 16:03 ` Julien Grall
2016-03-14 17:18 ` Shanker Donthineni
2016-03-15 17:37 ` Julien Grall
2016-03-12 14:32 ` Julien Grall
2016-03-14 7:37 ` Julien Grall
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=56E2C729.9020607@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=julien.grall@citrix.com \
--cc=pelcan@codeaurora.org \
--cc=shankerd@codeaurora.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=vikrams@codeaurora.org \
--cc=xen-devel@lists.xenproject.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).