linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@amacapital.net>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: Andy Lutomirski <luto@kernel.org>, Ingo Molnar <mingo@kernel.org>,
	Jan Beulich <JBeulich@suse.com>, X86 ML <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86_32, entry, selftests: Add a selftest for kernel entries from vm86 mode
Date: Mon, 1 Jun 2015 16:45:11 -0700	[thread overview]
Message-ID: <CALCETrUVy==nn6AFe3rgSQV+NmJ0eOGOg9NAFcLuzFKkZ7=DHA@mail.gmail.com> (raw)
In-Reply-To: <556CEA65.5090900@osg.samsung.com>

On Mon, Jun 1, 2015 at 4:27 PM, Shuah Khan <shuahkh@osg.samsung.com> wrote:
> On 06/01/2015 04:54 PM, Andy Lutomirski wrote:
>> On Mon, Jun 1, 2015 at 9:02 AM, Shuah Khan <shuahkh@osg.samsung.com> wrote:
>>> On 05/29/2015 03:58 PM, Andy Lutomirski wrote:
>>>> Test a couple of special cases in 32-bit kernels for entries from
>>>> vm86 mode.  This will OOPS both old kernels due to a bug and and
>>>> 4.1-rc5 due to a regression I introduced, and it should make sure
>>>> that the SYSENTER-from-vm86-mode hack in the kernel keeps working.
>>>>
>>>> Tests: 394838c96013 x86/asm/entry/32: Fix user_mode() misuses
>>>> Tests: 7ba554b5ac69 x86/asm/entry/32: Really make user_mode() work correctly for VM86 mode
>>>> Signed-off-by: Andy Lutomirski <luto@kernel.org>
>>>> ---
>>>>
>>>> Ingo, Shuah: I think this should go in through -tip.  (In general, I think
>>>> new x86 tests that don't have interesting interactions with the kselftest
>>>> infrastructure should go in through -tip, especially tests such as this one
>>>> that are related to recent regressions.)
>>>
>>> No problem going through tip. Could you please make sure
>>>
>>> "make kselftest" run from top level and
>>> tools/testing/selftests/kselftest_install.sh
>>>
>>> don't break?
>>
>> Both 'make kselftest -j12 TARGETS=x86' and
>> ../../../tools/testing/selftests/kselftest_install.sh work for me.
>> (The .. thing is annoying -- would it make sense to fix it to work
>> from the kernel tree root?)
>>
>
> What is annoying about it and how would it get solved by making it
> run from the kernel tree root?
>

I ran it from the kernel tree root and it told me to change my
directory.  I think it should have changed the directory itself :)

--Andy

  reply	other threads:[~2015-06-01 23:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29 21:58 [PATCH] x86_32, entry, selftests: Add a selftest for kernel entries from vm86 mode Andy Lutomirski
2015-06-01 16:02 ` Shuah Khan
2015-06-01 22:54   ` Andy Lutomirski
2015-06-01 23:27     ` Shuah Khan
2015-06-01 23:45       ` Andy Lutomirski [this message]
2015-06-01 23:58         ` Shuah Khan
2015-06-02  5:37 ` [tip:x86/urgent] x86/asm/entry/32, selftests: Add a selftest for kernel entries from VM86 mode tip-bot for Andy Lutomirski

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='CALCETrUVy==nn6AFe3rgSQV+NmJ0eOGOg9NAFcLuzFKkZ7=DHA@mail.gmail.com' \
    --to=luto@amacapital.net \
    --cc=JBeulich@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=shuahkh@osg.samsung.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;
as well as URLs for NNTP newsgroup(s).