[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230403111020.3136-1-kirill.shutemov@linux.intel.com>
Date: Mon, 3 Apr 2023 14:10:18 +0300
From: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
To: Dave Hansen <dave.hansen@...ux.intel.com>,
Andy Lutomirski <luto@...nel.org>,
Peter Zijlstra <peterz@...radead.org>
Cc: x86@...nel.org, Kostya Serebryany <kcc@...gle.com>,
Andrey Ryabinin <ryabinin.a.a@...il.com>,
Andrey Konovalov <andreyknvl@...il.com>,
Alexander Potapenko <glider@...gle.com>,
Taras Madan <tarasmadan@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
"H . J . Lu" <hjl.tools@...il.com>,
Andi Kleen <ak@...ux.intel.com>,
Rick Edgecombe <rick.p.edgecombe@...el.com>,
Bharata B Rao <bharata@....com>,
Jacob Pan <jacob.jun.pan@...ux.intel.com>,
Ashok Raj <ashok.raj@...el.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
Subject: [PATCH 0/2] Couple of trivial fixes for LAM vs. SVA interaction
- Do not allow to set FORCE_TAGGED_SVA bit for other process;
- Use EINVAL instead of EINTR for LAM enabling failure due to SVA;
Kirill A. Shutemov (2):
x86/mm/iommu/sva: Fix error code for LAM enabling failure due to SVA
x86/mm/iommu/sva: Do not allow to set FORCE_TAGGED_SVA bit from
outside
arch/x86/kernel/process_64.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
--
2.39.2
Powered by blists - more mailing lists