From: Andi Kleen <ak@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH 1/8] L1TFv3 8
Date: Fri, 4 May 2018 07:07:30 -0700 [thread overview]
Message-ID: <20180504140730.GC75137@tassilo.jf.intel.com> (raw)
In-Reply-To: <20180504134217.GS4535@dhcp22.suse.cz>
On Fri, May 04, 2018 at 03:42:17PM +0200, speck for Michal Hocko wrote:
> On Thu 03-05-18 20:23:22, speck for Andi Kleen wrote:
> [...]
> > #ifdef CONFIG_X86_PAE
> > -/* 44=32+12, the limit we can fit into an unsigned long pfn */
> > -#define __PHYSICAL_MASK_SHIFT 44
> > +/*
> > + * This is beyond the 44 bit limit imposed by the 32bit long pfns,
> > + * but we need the full mask to make sure inverted PROT_NONE
> > + * entries have all the host bits set in a guest.
> > + * The real limit is still 44 bits.
>
> I cannot find where is that limit enforced.
I don't think there is an explicit check anywhere, but it would just silently
wrap everywhere PFNs are used.
But likely it would fail to allocate such a large mem_map in lowmem, so
I doubt it could ever happen.
-Andi
next prev parent reply other threads:[~2018-05-04 14:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 3:23 [MODERATED] [PATCH 0/8] L1TFv3 4 Andi Kleen
2018-05-04 3:23 ` [MODERATED] [PATCH 1/8] L1TFv3 8 Andi Kleen
2018-05-04 13:42 ` [MODERATED] " Michal Hocko
2018-05-04 14:07 ` Andi Kleen [this message]
2018-05-04 3:23 ` [MODERATED] [PATCH 2/8] L1TFv3 7 Andi Kleen
2018-05-07 11:45 ` [MODERATED] " Vlastimil Babka
2018-05-04 3:23 ` [MODERATED] [PATCH 3/8] L1TFv3 1 Andi Kleen
2018-05-04 3:55 ` [MODERATED] " Linus Torvalds
2018-05-04 13:42 ` Michal Hocko
2018-05-07 12:38 ` Vlastimil Babka
2018-05-07 13:41 ` Andi Kleen
2018-05-07 18:01 ` Thomas Gleixner
2018-05-07 18:21 ` [MODERATED] " Andi Kleen
2018-05-07 20:03 ` Thomas Gleixner
2018-05-04 3:23 ` [MODERATED] [PATCH 4/8] L1TFv3 6 Andi Kleen
2018-05-04 3:23 ` [MODERATED] [PATCH 5/8] L1TFv3 2 Andi Kleen
2018-05-04 3:23 ` [MODERATED] [PATCH 6/8] L1TFv3 0 Andi Kleen
2018-05-04 3:23 ` [MODERATED] [PATCH 7/8] L1TFv3 5 Andi Kleen
2018-05-04 13:43 ` [MODERATED] " Michal Hocko
2018-05-04 14:11 ` Andi Kleen
2018-05-04 14:21 ` Michal Hocko
2018-05-04 3:23 ` [MODERATED] [PATCH 8/8] L1TFv3 3 Andi Kleen
2018-05-04 14:19 ` [MODERATED] " Andi Kleen
2018-05-04 14:34 ` Michal Hocko
2018-05-04 15:53 ` Andi Kleen
2018-05-04 16:26 ` Michal Hocko
2018-05-04 22:15 ` Dave Hansen
2018-05-05 3:55 ` Andi Kleen
2018-05-04 3:54 ` [MODERATED] Re: [PATCH 0/8] L1TFv3 4 Andi Kleen
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=20180504140730.GC75137@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=speck@linutronix.de \
/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.