From: Andi Kleen <ak@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v4 1/8] L1TFv4 1
Date: Thu, 10 May 2018 16:18:04 -0700 [thread overview]
Message-ID: <20180510231804.GJ13616@tassilo.jf.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1805110054570.2101@nanos.tec.linutronix.de>
> > -/* 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.
> > + */
> > +#define __PHYSICAL_MASK_SHIFT 52
> > #define __VIRTUAL_MASK_SHIFT 32
>
> Are you really sure that this does not have unwanted side effects in any
> (indirect) user of __PHYSICAL_MASK_SHIFT ? If yes, please indicate so in
> the changelog.
Yes I did an audit. Will indicate.
It's safe because these bits can never be set to non 0 because all PTEs
are created from unsigned long PFNs.
-Andi
next prev parent reply other threads:[~2018-05-10 23:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 21:25 [MODERATED] [PATCH v4 0/8] L1TFv4 0 ak
2018-05-09 21:25 ` [MODERATED] [PATCH v4 1/8] L1TFv4 1 ak
2018-05-10 23:00 ` Thomas Gleixner
2018-05-10 23:18 ` Andi Kleen [this message]
2018-05-09 21:25 ` [MODERATED] [PATCH v4 2/8] L1TFv4 4 ak
2018-05-09 21:25 ` [MODERATED] [PATCH v4 3/8] L1TFv4 6 ak
2018-05-10 23:15 ` Thomas Gleixner
2018-05-10 23:32 ` [MODERATED] " Andi Kleen
2018-05-10 23:41 ` Thomas Gleixner
2018-05-09 21:25 ` [MODERATED] [PATCH v4 4/8] L1TFv4 7 ak
2018-05-09 21:25 ` [MODERATED] [PATCH v4 5/8] L1TFv4 8 ak
2018-05-10 23:27 ` Thomas Gleixner
2018-05-09 21:25 ` [MODERATED] [PATCH v4 6/8] L1TFv4 3 ak
2018-05-10 22:52 ` Thomas Gleixner
2018-05-10 23:26 ` [MODERATED] " Andi Kleen
2018-05-10 23:46 ` Thomas Gleixner
2018-05-09 21:25 ` [MODERATED] [PATCH v4 7/8] L1TFv4 2 ak
2018-05-11 8:23 ` Thomas Gleixner
2018-05-11 8:24 ` Thomas Gleixner
2018-05-09 21:25 ` [MODERATED] [PATCH v4 8/8] L1TFv4 5 ak
2018-05-10 4:13 ` [MODERATED] " Andi Kleen
2018-05-09 21:54 ` [MODERATED] Re: [PATCH v4 0/8] L1TFv4 0 Andi Kleen
2018-05-10 6:47 ` [MODERATED] Re: ***UNCHECKED*** " Vlastimil Babka
2018-05-10 8:04 ` Michal Hocko
2018-05-10 16:07 ` Andi Kleen
2018-05-10 16:57 ` [MODERATED] " Borislav Petkov
2018-05-10 17:35 ` Andi Kleen
2018-05-10 22:11 ` Thomas Gleixner
2018-05-10 22:26 ` [MODERATED] " 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=20180510231804.GJ13616@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.