From: Alexander Potapenko <glider@google.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"the arch/x86 maintainers" <x86@kernel.org>,
Kostya Serebryany <kcc@google.com>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
"H . J . Lu" <hjl.tools@gmail.com>,
Andi Kleen <ak@linux.intel.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv4 OPTIONAL 8/8] x86/mm: Extend LAM to support to LAM_U48
Date: Thu, 30 Jun 2022 12:06:47 +0200 [thread overview]
Message-ID: <CAG_fn=VFOFjYmT5o3jLe+qKo4A1qp8N0=USeyzbb-hcdYChK6Q@mail.gmail.com> (raw)
In-Reply-To: <20220622162230.83474-9-kirill.shutemov@linux.intel.com>
On Wed, Jun 22, 2022 at 6:23 PM Kirill A. Shutemov
<kirill.shutemov@linux.intel.com> wrote:
>
> LAM_U48 allows to encode 15 bits of tags into address.
>
> LAM_U48 steals bits above 47-bit for tags and makes it impossible for
> userspace to use full address space on 5-level paging machine.
>
> Make these features mutually exclusive: whichever gets enabled first
> blocks the other one.
>
> Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> @@ -206,11 +209,15 @@ const char *arch_vma_name(struct vm_area_struct *vma)
> * the failure of such a fixed mapping request, so the restriction is not
> * applied.
> */
> -bool mmap_address_hint_valid(unsigned long addr, unsigned long len)
> +bool mmap_address_hint_valid(struct mm_struct *mm,
> + unsigned long addr, unsigned long len)
Please make sure to reflect the newly added parameter in the doc comment.
This may also apply to other patches in the series.
--
Alexander Potapenko
Software Engineer
Google Germany GmbH
Erika-Mann-Straße, 33
80636 München
Geschäftsführer: Paul Manicle, Liana Sebastian
Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Diese E-Mail ist vertraulich. Falls Sie diese fälschlicherweise
erhalten haben sollten, leiten Sie diese bitte nicht an jemand anderes
weiter, löschen Sie alle Kopien und Anhänge davon und lassen Sie mich
bitte wissen, dass die E-Mail an die falsche Person gesendet wurde.
This e-mail is confidential. If you received this communication by
mistake, please don't forward it to anyone else, please erase all
copies and attachments, and please let me know that it has gone to the
wrong person.
prev parent reply other threads:[~2022-06-30 10:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 16:22 [PATCHv4 0/8] Linear Address Masking enabling Kirill A. Shutemov
2022-06-22 16:22 ` [PATCHv4 1/8] x86/mm: Fix CR3_ADDR_MASK Kirill A. Shutemov
2022-06-22 16:22 ` [PATCHv4 2/8] x86: CPUID and CR3/CR4 flags for Linear Address Masking Kirill A. Shutemov
2022-06-22 16:22 ` [PATCHv4 3/8] mm: Pass down mm_struct to untagged_addr() Kirill A. Shutemov
2022-07-05 15:42 ` Alexander Potapenko
2022-07-06 23:13 ` Kirill A. Shutemov
2022-07-07 8:56 ` Alexander Potapenko
2022-07-07 11:58 ` Kirill A. Shutemov
2022-06-22 16:22 ` [PATCHv4 4/8] x86/mm: Handle LAM on context switch Kirill A. Shutemov
2022-06-30 8:36 ` Alexander Potapenko
2022-06-22 16:22 ` [PATCHv4 5/8] x86/uaccess: Provide untagged_addr() and remove tags before address check Kirill A. Shutemov
2022-06-22 16:22 ` [PATCHv4 6/8] x86/mm: Provide ARCH_GET_UNTAG_MASK and ARCH_ENABLE_TAGGED_ADDR Kirill A. Shutemov
2022-07-12 13:12 ` Alexander Potapenko
2022-07-12 17:14 ` Kirill A. Shutemov
2022-07-14 14:28 ` Alexander Potapenko
2022-07-14 18:12 ` Kirill A. Shutemov
2022-06-22 16:22 ` [PATCHv4 7/8] x86: Expose untagging mask in /proc/$PID/arch_status Kirill A. Shutemov
2022-06-22 16:22 ` [PATCHv4 OPTIONAL 8/8] x86/mm: Extend LAM to support to LAM_U48 Kirill A. Shutemov
2022-06-30 10:06 ` Alexander Potapenko [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='CAG_fn=VFOFjYmT5o3jLe+qKo4A1qp8N0=USeyzbb-hcdYChK6Q@mail.gmail.com' \
--to=glider@google.com \
--cc=ak@linux.intel.com \
--cc=andreyknvl@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=dvyukov@google.com \
--cc=hjl.tools@gmail.com \
--cc=kcc@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=ryabinin.a.a@gmail.com \
--cc=x86@kernel.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