Re: [PATCH 0/4] x86: enable User-Mode Instruction Prevention

On Fri, 2016-11-11 at 23:51 +0300, Stas Sergeev wrote: > 11.11.2016 07:14, Ricardo Neri пишет: > >> 10.11.2016 09:46, Ricardo Neri пишет: > >>> I took a closer look at the dosemu code. It appears that it does not > >>> purposely utilize SGDT to obtain the descriptor table while in vm86. It > >>>

Re: [PATCH 1/4] x86/cpufeature: Add User-Mode Instruction Prevention definitions

On Fri, 2016-11-11 at 11:22 +0100, Borislav Petkov wrote: > On Thu, Nov 10, 2016 at 08:08:07PM -0800, Ricardo Neri wrote: > > UMIP is enabled by setting a bit in CR4. If that bit is not supposed > > to be set, that could cause a #GP fault. > > Yeah, you do check CPUID first, AFAICT, so you should

Re: [PATCH 0/4] x86: enable User-Mode Instruction Prevention

11.11.2016 07:14, Ricardo Neri пишет: 10.11.2016 09:46, Ricardo Neri пишет: I took a closer look at the dosemu code. It appears that it does not purposely utilize SGDT to obtain the descriptor table while in vm86. It does use SGDT (in protected mode) to emulate certain functionality such as the

[PATCH v5 2/2] thinkpad_acpi: Add support for X1 Yoga (2016) Tablet Mode

For whatever reason, the X1 Yoga doesn't support the normal method of querying for tablet mode. Instead of providing the MHKG method under the hotkey handle, we're instead given the CMMD method under the EC handle. Values on this handle are either 0x1, laptop mode, or 0x6, tablet mode. Tested-by:

Re: [PATCH 1/4] x86/cpufeature: Add User-Mode Instruction Prevention definitions

On 11/10/2016 08:08 PM, Ricardo Neri wrote: > Thanks for the suggestions. Perhaps I can include these metrics in my > V2. On th other hand, Dave Hansen gave a good argument on potential > conflicts when, of instance running on an AMD CPU. UMIP is enabled by > setting a bit in CR4. If that bit is

Re: [RFC PATCH v3 10/20] Add support to access boot related data in the clear

On Wed, 2016-11-09 at 18:36 -0600, Tom Lendacky wrote: > Boot data (such as EFI related data) is not encrypted when the system > is booted and needs to be accessed unencrypted.  Add support to apply > the proper attributes to the EFI page tables and to the > early_memremap and memremap APIs to

Re: [RESEND PATCH v1 02/11] dt-bindings: hisi: Add Hisilicon HiP05/06/07 Sysctrl and Djtag dts bindings

On Friday 11 November 2016 05:23 PM, Mark Rutland wrote: On Fri, Nov 11, 2016 at 04:49:03PM +0530, Anurup M wrote: On Thursday 10 November 2016 10:53 PM, Mark Rutland wrote: On Thu, Nov 03, 2016 at 01:41:58AM -0400, Anurup M wrote: diff --git

Re: [RESEND PATCH v1 02/11] dt-bindings: hisi: Add Hisilicon HiP05/06/07 Sysctrl and Djtag dts bindings

On Fri, Nov 11, 2016 at 04:49:03PM +0530, Anurup M wrote: > On Thursday 10 November 2016 10:53 PM, Mark Rutland wrote: > >On Thu, Nov 03, 2016 at 01:41:58AM -0400, Anurup M wrote: > >>diff --git a/Documentation/devicetree/bindings/arm/hisilicon/hisilicon.txt >

Re: [RFC PATCH v3 03/20] x86: Add the Secure Memory Encryption cpu feature

On Wed, Nov 09, 2016 at 06:34:59PM -0600, Tom Lendacky wrote: > Update the cpu features to include identifying and reporting on the Here and for all other commit messages: s/cpu/CPU/g > Secure Memory Encryption feature. > ... -- Regards/Gruss, Boris. Good mailing practices for 400:

Re: [Ksummit-discuss] Including images on Sphinx documents

Am 11.11.2016 um 12:22 schrieb Jani Nikula : > On Thu, 10 Nov 2016, Jani Nikula wrote: >> On Thu, 10 Nov 2016, Markus Heiser wrote: >>> Could this POC persuade you, if so, I send a more elaborate RFC, >>> what

Re: [Ksummit-discuss] Including images on Sphinx documents

On Thu, 10 Nov 2016, Jani Nikula wrote: > On Thu, 10 Nov 2016, Markus Heiser wrote: >> Could this POC persuade you, if so, I send a more elaborate RFC, >> what do you think about? > > Sorry, I do not wish to be part of this. That was

Re: [PATCH 1/4] x86/cpufeature: Add User-Mode Instruction Prevention definitions

On Thu, Nov 10, 2016 at 08:08:07PM -0800, Ricardo Neri wrote: > UMIP is enabled by setting a bit in CR4. If that bit is not supposed > to be set, that could cause a #GP fault. Yeah, you do check CPUID first, AFAICT, so you should be ok... -- Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix

Re: [Ksummit-discuss] Including images on Sphinx documents

Em Wed, 09 Nov 2016 13:58:12 +0200 Jani Nikula escreveu: > On Wed, 09 Nov 2016, Markus Heiser wrote: > > Am 09.11.2016 um 12:16 schrieb Jani Nikula : > >>> So I vote for : > >>> > 1) copy (or symlink)