linux-toradex.git/drivers/lguest/x86, branch v3.19.3

x86, asmlinkage, lguest: Pass in globals into assembler statement

2013-11-07T01:43:05+00:00

Tell the compiler that the inline assembler statement
references lguest_entry.

This fixes compile problems with LTO where the variable
and the assembler code may end up in different files.

Cc: x86@kernel.org
Cc: rusty@rustcorp.com.au
Signed-off-by: Andi Kleen 
Signed-off-by: Rusty Russell

x86, flags: Rename X86_EFLAGS_BIT1 to X86_EFLAGS_FIXED

2013-06-25T23:25:32+00:00

Bit 1 in the x86 EFLAGS is always set.  Name the macro something that
actually tries to explain what it is all about, rather than being a
tautology.

Signed-off-by: H. Peter Anvin 
Cc: Rusty Russell 
Cc: Gleb Natapov 
Cc: Paolo Bonzini 
Link: http://lkml.kernel.org/n/tip-f10rx5vjjm6tfnt8o1wseb3v@git.kernel.org

lguest: assume Switcher text is a single page.

2013-04-22T06:01:36+00:00

ie. SHARED_SWITCHER_PAGES == 1.  It is well under a page, and it's a
minor simplification: it's nice to have *one* simplification in a
patch series!

Signed-off-by: Rusty Russell

lguest: prepare to make SWITCHER_ADDR a variable.

2013-04-22T06:01:33+00:00

We currently use the whole top PGD entry for the switcher, but that's
hitting the fixmap in some configurations (mainly, large NR_CPUS).
Introduce a variable, currently set to the constant.

Signed-off-by: Rusty Russell

lguest, x86: handle guest TS bit for lazy/non-lazy fpu host models

2012-09-18T22:52:09+00:00

Instead of using unlazy_fpu() check if user_has_fpu() and set/clear
the host TS bits so that the lguest works fine with both the
lazy/non-lazy FPU host models with minimal changes.

Signed-off-by: Suresh Siddha 
Link: http://lkml.kernel.org/r/1345842782-24175-6-git-send-email-suresh.b.siddha@intel.com
Cc: Rusty Russell 
Signed-off-by: H. Peter Anvin

x86: Fix rflags in FAKE_STACK_FRAME

2011-12-06T09:02:38+00:00

The x86_64 kernel pushes the fake kernel stack in
arch/x86/kernel/entry_64.S:FAKE_STACK_FRAME, and
rflags register in it does not conform to the specification.

Although Intel's manual[1] says bit 1 of it shall be set to 1,
this bit is cleared to 0 on pushing the fake stack.

[1] Intel(R) 64 and IA-32 Architectures Software Developer's Manual
    Vol.1 3-21 Figure 3-8. EFLAGS Register

If it is not on purpose, it is better to be fixed, because
it can lead some tools misunderstanding the stack frame. For example,
"crash" utility[2] actually detects it and warns you like
below:

       RIP: ffffffff8005dfa2  RSP: ffff8104ce0c7f58  RFLAGS: 00000200
       [...]

       bt: WARNING: possibly bogus exception frame

Signed-off-by: Seiichi Ikarashi 
Tested-by: Masayoshi MIZUMA 
Cc: Jan Beulich 
Cc: Frederic Weisbecker 
Cc: Linus Torvalds 
Signed-off-by: Ingo Molnar

lguest: Fix in/out emulation

2011-07-22T05:09:51+00:00

We were blatting too much of the register.  Linux didn't care, but in
theory it might.

Reported-by: Jonas Maebe 
Signed-off-by: Rusty Russell

lguest: update comments

2011-07-22T05:09:50+00:00

Also removes a long-unused #define and an extraneous semicolon.

Signed-off-by: Rusty Russell

lguest: don't rewrite vmcall instructions

2011-07-22T05:09:49+00:00

Now we no longer use vmcall, we don't need to rewrite it in the Guest.

Signed-off-by: Rusty Russell

lguest: compile fixes

2011-01-20T11:07:29+00:00

arch/x86/lguest/boot.c: In function ‘lguest_init_IRQ’:
arch/x86/lguest/boot.c:824: error: macro "__this_cpu_write" requires 2 arguments, but only 1 given
arch/x86/lguest/boot.c:824: error: ‘__this_cpu_write’ undeclared (first use in this function)
arch/x86/lguest/boot.c:824: error: (Each undeclared identifier is reported only once
arch/x86/lguest/boot.c:824: error: for each function it appears in.)

drivers/lguest/x86/core.c: In function ‘copy_in_guest_info’:
drivers/lguest/x86/core.c:94: error: lvalue required as left operand of assignment

Signed-off-by: Rusty Russell