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

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

lguest: Use this_cpu_ops

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

Use this_cpu_ops in a couple of places in lguest.

Signed-off-by: Christoph Lameter 
Signed-off-by: Rusty Russell

lguest: workaround cmpxchg8b_emu by ignoring cli in the guest.

2010-04-14T12:13:54+00:00

It's only used by cmpxchg8b_emu (see db677ffa5f5a for the gory
details), and fixing that to be paravirt aware would be more work than
simply ignoring it (and AFAICT only help lguest).  This makes lguest
work on machines which have cmpxchg8b, for kernels compiled for older
processors.

(We can't emulate it properly: the popf which expects to restore interrupts
does not trap).

Signed-off-by: Rusty Russell 
Cc: Jeremy Fitzhardinge 
Cc: virtualization@lists.osdl.org

percpu: make misc percpu symbols unique

2009-10-29T13:34:14+00:00

This patch updates misc percpu related symbols such that percpu
symbols are unique and don't clash with local symbols.  This serves
two purposes of decreasing the possibility of global percpu symbol
collision and allowing dropping per_cpu__ prefix from percpu symbols.

* drivers/crypto/padlock-aes.c: s/last_cword/paes_last_cword/

* drivers/lguest/x86/core.c: s/last_cpu/lg_last_cpu/

* drivers/s390/net/netiucv.c: rename the variable used in a macro to
  avoid clashing with percpu symbol

* arch/mn10300/kernel/kprobes.c: replace current_ prefix with cur_ for
  static variables.  Please note that percpu symbol current_kprobe
  can't be changed as it's used by generic code.

Partly based on Rusty Russell's "alloc_percpu: rename percpu vars
which cause name clashes" patch.

Signed-off-by: Tejun Heo 
Reviewed-by: Christoph Lameter 
Cc: Rusty Russell 
Cc: Herbert Xu 
Cc: Chuck Ebbert 
Cc: David Howells 
Cc: Koichi Yasutake 
Cc: Ananth N Mavinakayanahalli 
Cc: Anil S Keshavamurthy 
Cc: David S. Miller 
Cc: Masami Hiramatsu 
Cc: Martin Schwidefsky 
Cc: Heiko Carstens 
Cc: linux390@de.ibm.com

lguest: update commentry

2009-07-30T06:33:46+00:00

Every so often, after code shuffles, I need to go through and unbitrot
the Lguest Journey (see drivers/lguest/README).  Since we now use RCU in
a simple form in one place I took the opportunity to expand that explanation.

Signed-off-by: Rusty Russell 
Cc: Ingo Molnar 
Cc: Paul McKenney

lguest: fix comment style

2009-07-30T06:33:45+00:00

I don't really notice it (except to begrudge the extra vertical
space), but Ingo does.  And he pointed out that one excuse of lguest
is as a teaching tool, it should set a good example.

Signed-off-by: Rusty Russell 
Cc: Ingo Molnar