Skip to main content

Browse the archive

Revision 5f630401f9e98bd062733b5bbef096dbf2158066 authored by Tiejun Chen on 22 August 2012, 16:10:20 UTC, committed by Benjamin Herrenschmidt on 24 August 2012, 10:26:06 UTC 
powerpc/kgdb: Restore current_thread_info properly
 
For powerpc BooKE and e200, singlestep is handled on the critical/dbg
exception stack. This causes current_thread_info() to fail for kgdb
internal, so previously We work around this issue by copying
the thread_info from the kernel stack before calling kgdb_handle_exception,
and copying it back afterwards.

But actually we don't do this properly. We should backup current_thread_info
then restore that when exit.

Signed-off-by: Tiejun Chen <tiejun.chen@windriver.com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
1 parent 949616c
Raw File
gfs2.h 
/*
 * Copyright (C) Sistina Software, Inc.  1997-2003 All rights reserved.
 * Copyright (C) 2004-2006 Red Hat, Inc.  All rights reserved.
 *
 * This copyrighted material is made available to anyone wishing to use,
 * modify, copy, or redistribute it subject to the terms and conditions
 * of the GNU General Public License version 2.
 */

#ifndef __GFS2_DOT_H__
#define __GFS2_DOT_H__

enum {
	NO_CREATE = 0,
	CREATE = 1,
};

enum {
	NO_FORCE = 0,
	FORCE = 1,
};

#define GFS2_FAST_NAME_SIZE 8

#endif /* __GFS2_DOT_H__ */
back to top