Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1583944 > unrolled thread
| Started by | Borislav Petkov <bp@alien8.de> |
|---|---|
| First post | 2017-02-18 19:20 +0100 |
| Last post | 2017-02-21 19:00 +0100 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [RFC PATCH v4 00/28] x86: Secure Memory Encryption (AMD) Borislav Petkov <bp@alien8.de> - 2017-02-18 19:20 +0100
Re: [RFC PATCH v4 00/28] x86: Secure Memory Encryption (AMD) Rik van Riel <riel@redhat.com> - 2017-02-21 18:50 +0100
Re: [RFC PATCH v4 00/28] x86: Secure Memory Encryption (AMD) Borislav Petkov <bp@alien8.de> - 2017-02-21 19:00 +0100
| From | Borislav Petkov <bp@alien8.de> |
|---|---|
| Date | 2017-02-18 19:20 +0100 |
| Subject | Re: [RFC PATCH v4 00/28] x86: Secure Memory Encryption (AMD) |
| Message-ID | <tchLY-5cw-9@gated-at.bofh.it> |
On Thu, Feb 16, 2017 at 09:41:59AM -0600, Tom Lendacky wrote:
> create mode 100644 Documentation/x86/amd-memory-encryption.txt
> create mode 100644 arch/x86/include/asm/mem_encrypt.h
> create mode 100644 arch/x86/kernel/mem_encrypt_boot.S
> create mode 100644 arch/x86/kernel/mem_encrypt_init.c
> create mode 100644 arch/x86/mm/mem_encrypt.c
I don't see anything standing in the way of merging those last two and
having a single:
arch/x86/kernel/mem_encrypt.c
with all functionality in there with ifdeffery around it so
that sme_encrypt_kernel() et all are still visible in the
!CONFIG_AMD_MEM_ENCRYPT case.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
[toc] | [next] | [standalone]
| From | Rik van Riel <riel@redhat.com> |
|---|---|
| Date | 2017-02-21 18:50 +0100 |
| Message-ID | <tdmJA-5Ph-13@gated-at.bofh.it> |
| In reply to | #1583944 |
[Multipart message — attachments visible in raw view] — view raw
On Sat, 2017-02-18 at 19:12 +0100, Borislav Petkov wrote: > On Thu, Feb 16, 2017 at 09:41:59AM -0600, Tom Lendacky wrote: > > > > create mode 100644 Documentation/x86/amd-memory-encryption.txt > > create mode 100644 arch/x86/include/asm/mem_encrypt.h > > create mode 100644 arch/x86/kernel/mem_encrypt_boot.S > > create mode 100644 arch/x86/kernel/mem_encrypt_init.c > > create mode 100644 arch/x86/mm/mem_encrypt.c > I don't see anything standing in the way of merging those last two > and > having a single: > > arch/x86/kernel/mem_encrypt.c Do we want that in kernel/ or in arch/x86/mm/ ? -- All rights reversed
[toc] | [prev] | [next] | [standalone]
| From | Borislav Petkov <bp@alien8.de> |
|---|---|
| Date | 2017-02-21 19:00 +0100 |
| Message-ID | <tdmTg-5SM-13@gated-at.bofh.it> |
| In reply to | #1585568 |
On Tue, Feb 21, 2017 at 12:42:45PM -0500, Rik van Riel wrote:
> Do we want that in kernel/ or in arch/x86/mm/ ?
If you'd ask me, I don't have a strong preference. It is a pile of
functionality which is part of the SME feature and as such, it is closer
to the CPU. So arch/x86/cpu/sme.c or so.
But then it is mm-related in a way as it is RAM encryption...
Meh, ask me something easier :-)
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web