All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH ltp v2 1/2] Add Intel umip(User Mode Instruction Prevention) basic function tests
Date: Thu, 8 Nov 2018 11:13:45 +0100	[thread overview]
Message-ID: <20181108101345.GA29767@rei> (raw)
In-Reply-To: <20181107132004.6dc7t36pxznb4xyb@xpf-desktop>

Hi!
> > Is there any other way how to find out UMIP has been enabled in kernel?
> > 
> > I would like to avoid maitaing code that tries to look for all possible
> > config locations if possible.
> > 
>   Could find "Activated the Intel User Mode Instruction Prevention (UMIP)
>   CPU feature" info in the head of dmesg, but afraid boot long time dmesg
>   head is covered... And no sysfs file for umip to check.
>   So could I add the info when cases failed???"possible due to
>   kconfig not set CONFIG_X86_INTEL_UMIP=y"?

I was looking into this yesterday and even talked to our kernel devs and
it seems that there is no other option than checking the .config to be
sure it was enabled.

So we may end up adding support for parsing the kernel config, it would
be probably useful in differents parts of LTP. But to make this happen
we should make it a library function and make sure it's accesible for C
testcases as well.

I can look into that and try to post a RFC patch later on, but it would
probably take more than week to get sorted out.

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2018-11-08 10:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01  1:49 [LTP] [PATCH ltp v2 1/2] Add Intel umip(User Mode Instruction Prevention) basic function tests Pengfei Xu
2018-11-01  1:49 ` [LTP] [PATCH ltp v2 2/2] Add umip(User Mode Instruction Prevention) test cases Pengfei Xu
2018-11-07  1:05 ` [LTP] [PATCH ltp v2 1/2] Add Intel umip(User Mode Instruction Prevention) basic function tests Xu, Pengfei
2018-11-07 10:15 ` Cyril Hrubis
2018-11-07 13:20   ` Pengfei Xu
2018-11-08 10:13     ` Cyril Hrubis [this message]
2018-11-08 10:51       ` Pengfei Xu

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=20181108101345.GA29767@rei \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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.