On 3/22/21 2:22 PM, Doug Anderson wrote:
Hi,
On Mon, Mar 22, 2021 at 11:19 AM Arnd Bergmann wrote:
On Mon, Mar 22, 2021 at 6:07 PM Doug Anderson wrote:
On Mon, Mar 22, 2021 at 9:43 AM Arnd Bergmann wrote:
-#define v1printk(a...) do { \
- if (verbose) \
-
oks better to stop carrying this code in
the kernel and integrate the code into the out-of-tree driver
instead.
Because it has no in tree users, it absolutely makes the most
sense to purge this function.
Acked-by: Jason Wessel
The long term trajectory for the kernel looks likely to include
effort
We'll have to fix them at some point.
Acked-by: Jason Wessel
Cheers,
Jason.
On 2/26/19 1:16 PM, Gustavo A. R. Silva wrote:
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warnings:
kernel/debug
On 09/28/2018 07:57 AM, Michael Ellerman wrote:
Christophe LEROY writes:
Le 27/09/2018 à 13:09, Michael Ellerman a écrit :
Christophe LEROY writes:
Le 26/09/2018 à 13:11, Daniel Thompson a écrit :
The Fixes: and now your Reviewed-by: appear automatically in patchwork
On 09/28/2018 07:57 AM, Michael Ellerman wrote:
Christophe LEROY writes:
Le 27/09/2018 à 13:09, Michael Ellerman a écrit :
Christophe LEROY writes:
Le 26/09/2018 à 13:11, Daniel Thompson a écrit :
The Fixes: and now your Reviewed-by: appear automatically in patchwork
Linus,
Please pull the kgdb tree.
Summary of changes:
* Fix 2032 time access issues and new compiler warnings
* minor regression test cleanup
* formatting fixes for end user use of kdb
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb.git
tags/for_linus-4.16
Thanks,
Jason.
Linus,
Please pull the kgdb tree.
Summary of changes:
* Fix 2032 time access issues and new compiler warnings
* minor regression test cleanup
* formatting fixes for end user use of kdb
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb.git
tags/for_linus-4.16
Thanks,
Jason.
table+i+1,
+ memmove(kdb_name_table+i, kdb_name_table+i+1,
sizeof(kdb_name_table[0]) *
(ARRAY_SIZE(kdb_name_table)-i-1));
}
That is good by me. Many thanks! Added to queue.
Reviewed-by: Jason Wessel &
i+1,
+ memmove(kdb_name_table+i, kdb_name_table+i+1,
sizeof(kdb_name_table[0]) *
(ARRAY_SIZE(kdb_name_table)-i-1));
}
That is good by me. Many thanks! Added to queue.
Reviewed-by: Jason Wessel
Jason.
On 01/30/2018 07:35 AM, Arnd Bergmann wrote:
On Mon, Jan 29, 2018 at 3:22 AM, Baolin Wang wrote:
The kdb code will print the monotonic time by ktime_get_ts(), but
the ktime_get_ts() will be protected by a sequence lock, that will
introduce one deadlock risk if the lock
On 01/30/2018 07:35 AM, Arnd Bergmann wrote:
On Mon, Jan 29, 2018 at 3:22 AM, Baolin Wang wrote:
The kdb code will print the monotonic time by ktime_get_ts(), but
the ktime_get_ts() will be protected by a sequence lock, that will
introduce one deadlock risk if the lock was already held in the
is only interested in the second field, we can use the
ktime_get_seconds() to get the monotonic time without a lock,
moreover we can remove the 'struct timespec', which is not y2038
safe.
Signed-off-by: Baolin Wang <baolin.w...@linaro.org>
Acked-by: Jason Wessel <jason.wes...@wind
is only interested in the second field, we can use the
ktime_get_seconds() to get the monotonic time without a lock,
moreover we can remove the 'struct timespec', which is not y2038
safe.
Signed-off-by: Baolin Wang
Acked-by: Jason Wessel
Thanks. Added to the kgdb-next branch for the next
On 01/25/2018 05:38 AM, Daniel Thompson wrote:
On Thu, Jan 25, 2018 at 05:18:54PM +0800, Baolin Wang wrote:
On 25 January 2018 at 16:55, Arnd Bergmann wrote:
On Thu, Jan 25, 2018 at 9:05 AM, Baolin Wang wrote:
@@ -2554,7 +2554,7 @@ static int
On 01/25/2018 05:38 AM, Daniel Thompson wrote:
On Thu, Jan 25, 2018 at 05:18:54PM +0800, Baolin Wang wrote:
On 25 January 2018 at 16:55, Arnd Bergmann wrote:
On Thu, Jan 25, 2018 at 9:05 AM, Baolin Wang wrote:
@@ -2554,7 +2554,7 @@ static int kdb_summary(int argc, const char **argv)
On 12/12/2017 06:10 AM, Daniel Thompson wrote:
kgdbts includes a couple of different "thrashing" style tests that
may have long runtimes (especially on simulated platforms) and which
run asynchronously. This is uncomfortable for interactive use and
makes setting timeouts tricky for automatic
On 12/12/2017 06:10 AM, Daniel Thompson wrote:
kgdbts includes a couple of different "thrashing" style tests that
may have long runtimes (especially on simulated platforms) and which
run asynchronously. This is uncomfortable for interactive use and
makes setting timeouts tricky for automatic
...@infradead.org>
Cc: Daniel Thompson <daniel.thomp...@linaro.org>
Cc: Jason Wessel <jason.wes...@windriver.com>
Cc: kgdb-bugrep...@lists.sourceforge.net
---
kernel/debug/kdb/kdb_main.c | 11 +++
1 file changed, 11 insertions(+)
--- lnx-415-rc1.orig/kernel/debug/kdb
including the newline character. This
causes the ending single-quote mark to be printed on the next line
by itself, so just change the ending newline character to a null
character (end of string) so that it won't be "printed."
Signed-off-by: Randy Dunlap
Cc: Daniel Thompson
Cc: Jason Wes
On 12/06/2017 06:52 PM, Randy Dunlap wrote:
On 12/06/2017 02:33 PM, Jason Wessel wrote:
L:kgdb-bugrep...@lists.sourceforge.net
T:git git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb.git
I would urge you to move to a different mailing list server.
No argument here
On 12/06/2017 06:52 PM, Randy Dunlap wrote:
On 12/06/2017 02:33 PM, Jason Wessel wrote:
L:kgdb-bugrep...@lists.sourceforge.net
T:git git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb.git
I would urge you to move to a different mailing list server.
No argument here
On 12/05/2017 10:42 AM, Randy Dunlap wrote:
On 12/05/2017 06:55 AM, Daniel Thompson wrote:
On 05/12/17 14:37, Jason Wessel wrote:
I have a series of 50+ patches for kgdb/kdb/usb which have never been
published. I am not saying that we actually need any of those patches, but it
would be nice
On 12/05/2017 10:42 AM, Randy Dunlap wrote:
On 12/05/2017 06:55 AM, Daniel Thompson wrote:
On 05/12/17 14:37, Jason Wessel wrote:
I have a series of 50+ patches for kgdb/kdb/usb which have never been
published. I am not saying that we actually need any of those patches, but it
would be nice
Daniel Thompson (1):
kdb: Fix handling of kallsyms_symbol_next() return value
Jason Wessel (1):
kgdb/kdb/debug_core: Add co-maintainer Daniel Thompson
MAINTAINERS | 1 +
kernel/debug/kdb/kdb_io.c | 2 +-
2 files changed
Daniel Thompson (1):
kdb: Fix handling of kallsyms_symbol_next() return value
Jason Wessel (1):
kgdb/kdb/debug_core: Add co-maintainer Daniel Thompson
MAINTAINERS | 1 +
kernel/debug/kdb/kdb_io.c | 2 +-
2 files changed
pposed to be unreachable, we also add a WARN_ON().
Reported-by: Dan Carpenter <dan.carpen...@oracle.com>
Signed-off-by: Daniel Thompson <daniel.thomp...@linaro.org>
Cc: linux-stable <sta...@vger.kernel.org>
Signed-off-by: Jason Wessel <jason.wes...@windriver.com>
---
kernel/deb
a WARN_ON().
Reported-by: Dan Carpenter
Signed-off-by: Daniel Thompson
Cc: linux-stable
Signed-off-by: Jason Wessel
---
kernel/debug/kdb/kdb_io.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/debug/kdb/kdb_io.c b/kernel/debug/kdb/kdb_io.c
index e74be38..ed5d349
Signed-off-by: Jason Wessel <jason.wes...@windriver.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 2811a21..74be63b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7659,6 +7659,7 @@ F:security/keys/
KGDB / KDB /debug_c
Signed-off-by: Jason Wessel
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 2811a21..74be63b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7659,6 +7659,7 @@ F:security/keys/
KGDB / KDB /debug_core
M: Jason Wessel
+M
ded a comment
about the __ktime_get_real_seconds() not taking the lock because it was done
that way in other places in the header file.
===
extern time64_t ktime_get_real_seconds(void);
+/* does not take xtime_lock */
+extern time64_t __ktime_get_real_seconds(void);
===
Acked-by: Jason Wes
ded a comment
about the __ktime_get_real_seconds() not taking the lock because it was done
that way in other places in the header file.
===
extern time64_t ktime_get_real_seconds(void);
+/* does not take xtime_lock */
+extern time64_t __ktime_get_real_seconds(void);
===
Acked-by: Jason Wes
On 10/13/2017 03:26 AM, Daniel Thompson wrote:
On 12/10/17 23:40, Andrew Morton wrote:
On Thu, 12 Oct 2017 16:06:11 +0200 Arnd Bergmann wrote:
kdb is the only user of the __current_kernel_time() interface, which is
not y2038 safe and should be removed at some point.
The kdb
On 10/13/2017 03:26 AM, Daniel Thompson wrote:
On 12/10/17 23:40, Andrew Morton wrote:
On Thu, 12 Oct 2017 16:06:11 +0200 Arnd Bergmann wrote:
kdb is the only user of the __current_kernel_time() interface, which is
not y2038 safe and should be removed at some point.
The kdb code also goes
On 12/05/2017 08:09 AM, Lee Jones wrote:
On Tue, 05 Dec 2017, Daniel Thompson wrote:
... with many, many thanks for Jason for all his hard work.
Cc: Jason Wessel <jason.wes...@windriver.com>
Signed-off-by: Daniel Thompson <daniel.thomp...@linaro.org>
---
Notes:
Over the yea
On 12/05/2017 08:09 AM, Lee Jones wrote:
On Tue, 05 Dec 2017, Daniel Thompson wrote:
... with many, many thanks for Jason for all his hard work.
Cc: Jason Wessel
Signed-off-by: Daniel Thompson
---
Notes:
Over the years Jason has become increasingly hard to get hold off
and I
On 11/17/2016 01:16 PM, Brian Norris wrote:
Hi,
I've been poking around KGDB, and I noticed that the KDB 'ftdump'
command (to dump ftrace logs) produces warnings like this:
(gdb) monitor ftdump
Dumping ftrace buffer:
BUG: sleeping function called from invalid context at mm/slab.h:359
On 11/17/2016 01:16 PM, Brian Norris wrote:
Hi,
I've been poking around KGDB, and I noticed that the KDB 'ftdump'
command (to dump ftrace logs) produces warnings like this:
(gdb) monitor ftdump
Dumping ftrace buffer:
BUG: sleeping function called from invalid context at mm/slab.h:359
On 09/15/2016 11:32 PM, AKASHI Takahiro wrote:
@@ -176,18 +183,14 @@ int kgdb_arch_handle_exception(int exception_vector, int
signo,
* over and over again.
*/
kgdb_arch_update_addr(linux_regs, remcom_in_buffer);
-
On 09/15/2016 11:32 PM, AKASHI Takahiro wrote:
@@ -176,18 +183,14 @@ int kgdb_arch_handle_exception(int exception_vector, int
signo,
* over and over again.
*/
kgdb_arch_update_addr(linux_regs, remcom_in_buffer);
-
On 09/16/2016 02:45 AM, Will Deacon wrote:
On Fri, Sep 16, 2016 at 01:32:19PM +0900, AKASHI Takahiro wrote:
On Thu, Sep 15, 2016 at 08:04:57AM -0500, Jason Wessel wrote:
I added the patch to kgdb-next after fixing up the context since it no
longer applied to the mainline (
https
On 09/16/2016 02:45 AM, Will Deacon wrote:
On Fri, Sep 16, 2016 at 01:32:19PM +0900, AKASHI Takahiro wrote:
On Thu, Sep 15, 2016 at 08:04:57AM -0500, Jason Wessel wrote:
I added the patch to kgdb-next after fixing up the context since it no
longer applied to the mainline (
https
On 04/20/2015 08:13 PM, AKASHI Takahiro wrote:
Jason,
Could you please review my patch below?
See also arm64 maintainer's comment:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/313712.html
Thanks,
-Takahiro AKASHI
I tried to verify kgdb in vanilla kernel on fast model,
On 04/20/2015 08:13 PM, AKASHI Takahiro wrote:
Jason,
Could you please review my patch below?
See also arm64 maintainer's comment:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/313712.html
Thanks,
-Takahiro AKASHI
I tried to verify kgdb in vanilla kernel on fast model,
On 09/15/2016 05:41 AM, Daniel Thompson wrote:
On 15/09/16 08:56, AKASHI Takahiro wrote:
On Wed, Sep 14, 2016 at 03:58:51PM +0100, Will Deacon wrote:
Hi Akashi,
On Tue, Apr 21, 2015 at 02:13:13AM +0100, AKASHI Takahiro wrote:
Could you please review my patch below?
See also arm64
On 09/15/2016 05:41 AM, Daniel Thompson wrote:
On 15/09/16 08:56, AKASHI Takahiro wrote:
On Wed, Sep 14, 2016 at 03:58:51PM +0100, Will Deacon wrote:
Hi Akashi,
On Tue, Apr 21, 2015 at 02:13:13AM +0100, AKASHI Takahiro wrote:
Could you please review my patch below?
See also arm64
On 03/08/2016 11:16 PM, Stephen Rothwell wrote:
Hi Jason,
I noticed that the kgdb tree
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb.git branch
kgdb-next
has not been updated since March 2015. I am going to remove it from
linux-next tomorrow unless I hear that it may be
On 03/08/2016 11:16 PM, Stephen Rothwell wrote:
Hi Jason,
I noticed that the kgdb tree
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb.git branch
kgdb-next
has not been updated since March 2015. I am going to remove it from
linux-next tomorrow unless I hear that it may be
reference to `vc_cons'
kgdboc.o is built when KGDB_SERIAL_CONSOLE is set. So make
KGDB_SERIAL_CONSOLE depend on HW_CONSOLE which includes those symbols.
Acked-by: Jason Wessel <jason.wes...@windriver.com>
I'll put this in the kgdb-next branch and submit it to the upstream, unless it
reference to `vc_cons'
kgdboc.o is built when KGDB_SERIAL_CONSOLE is set. So make
KGDB_SERIAL_CONSOLE depend on HW_CONSOLE which includes those symbols.
Acked-by: Jason Wessel
I'll put this in the kgdb-next branch and submit it to the upstream, unless it
gets merged in another queue.
Thanks
w there is a problem. :-)
Acked-by: Jason Wessel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
. :-)
Acked-by: Jason Wessel jason.wes...@windriver.com
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On 03/02/2015 08:13 AM, Daniel Thompson wrote:
> kallsyms_symbol_next() returns a boolean (true on success). Currently
> kdb_read() tests the return value with an inequality that
> unconditionally evaluates to true.
>
> This is fixed in the obvious way and, since the conditional branch is
>
On 03/02/2015 08:13 AM, Daniel Thompson wrote:
kallsyms_symbol_next() returns a boolean (true on success). Currently
kdb_read() tests the return value with an inequality that
unconditionally evaluates to true.
This is fixed in the obvious way and, since the conditional branch is
supposed to
for kdb_getstr's prompt argument
Jason Wessel (1):
kdb: Fix off by one error in kdb_cpu()
Jay Lan (1):
kdb: fix incorrect counts in KDB summary command output
Rajaneesh Acharya (1):
kgdb, docs: Fix pdfdocs build errors
Documentation/DocBook/kgdb.tmpl | 6 +++---
include/linux/kdb.h
for kdb_getstr's prompt argument
Jason Wessel (1):
kdb: Fix off by one error in kdb_cpu()
Jay Lan (1):
kdb: fix incorrect counts in KDB summary command output
Rajaneesh Acharya (1):
kgdb, docs: Fix para pdfdocs build errors
Documentation/DocBook/kgdb.tmpl | 6 +++---
include
Linus,
Please pull the kgdb tree bug fixes.
These have been around since 3.17 and in kgdb-next for the last 9
weeks and some will go back to -stable.
Summary of changes:
KGDB/KDB fixes and cleanups
Cleanups
kdb: Remove unused command flags, repeat flags and KDB_REPEAT_NONE
Fixes
Linus,
Please pull the kgdb tree bug fixes.
These have been around since 3.17 and in kgdb-next for the last 9
weeks and some will go back to -stable.
Summary of changes:
KGDB/KDB fixes and cleanups
Cleanups
kdb: Remove unused command flags, repeat flags and KDB_REPEAT_NONE
Fixes
On 01/06/2015 03:21 PM, Andrew Morton wrote:
> On Tue, 06 Jan 2015 10:57:42 -0800 Joe Perches wrote:
>
>> On Tue, 2015-01-06 at 18:54 +, Daniel Thompson wrote:
>>> Hi Jason
>>>
>>> I'm trying to figure out what to do with my long-outstanding kgdb/kdb
>>> patches in preparation for the 3.20
On 01/06/2015 03:21 PM, Andrew Morton wrote:
On Tue, 06 Jan 2015 10:57:42 -0800 Joe Perches j...@perches.com wrote:
On Tue, 2015-01-06 at 18:54 +, Daniel Thompson wrote:
Hi Jason
I'm trying to figure out what to do with my long-outstanding kgdb/kdb
patches in preparation for the 3.20
On 07/11/2014 06:33 AM, Daniel Thompson wrote:
> This patchset implements restricted modes for the KDB debugger. It is a
> continuation of previous work of Anton Vorontsov. There are no
> outstanding review comments for this patchset.
>
> It provides a means for the root user to choose the set of
On 07/11/2014 06:33 AM, Daniel Thompson wrote:
This patchset implements restricted modes for the KDB debugger. It is a
continuation of previous work of Anton Vorontsov. There are no
outstanding review comments for this patchset.
It provides a means for the root user to choose the set of kdb
On 07/01/2014 09:16 AM, Daniel Thompson wrote:
> Currently if an active CPU fails to respond to a roundup request the
> CPU that requested the roundup will become stuck. This needlessly
> reduces the robustness of the debugger.
>
> This patch introduces a timeout allowing the system state to be
On 07/01/2014 09:16 AM, Daniel Thompson wrote:
Currently if an active CPU fails to respond to a roundup request the
CPU that requested the roundup will become stuck. This needlessly
reduces the robustness of the debugger.
This patch introduces a timeout allowing the system state to be
On 06/12/2014 01:48 PM, Fabian Frederick wrote:
> -Convert printk( to pr_foo()
> -Add pr_fmt
> -Coalesce formats
>
> Cc: Jason Wessel
> Cc: Andrew Morton
> Signed-off-by: Fabian Frederick
Thanks.
I looked through all the bits to make sure there were no cases were we
r
On 06/12/2014 01:48 PM, Fabian Frederick wrote:
-Convert printk( to pr_foo()
-Add pr_fmt
-Coalesce formats
Cc: Jason Wessel jason.wes...@windriver.com
Cc: Andrew Morton a...@linux-foundation.org
Signed-off-by: Fabian Frederick f...@skynet.be
Thanks.
I looked through all the bits to make
On 05/14/2014 09:55 AM, Daniel Thompson wrote:
> The behaviour of the UART poll_put_char infrastructure is inconsistent
> with respect to linefeed conversions. This in turn leads to difficulty
> using kdb on serial ports that are not also consoles
> (e.g. console=ttyAMA0,115200
On 05/14/2014 09:55 AM, Daniel Thompson wrote:
The behaviour of the UART poll_put_char infrastructure is inconsistent
with respect to linefeed conversions. This in turn leads to difficulty
using kdb on serial ports that are not also consoles
(e.g. console=ttyAMA0,115200 kgdboc=ttyAMA1,115200).
eviewed-by: Dimitri Sivanich
> Reviewed-by: Hedi Berriche
One problem that I pointed out before and then you can add
Acked-by: Jason Wessel
> ---
> include/linux/kdb.h |1 +
> include/linux/kgdb.h|1 +
> kernel/debug/debug_core.c | 30
h...@sgi.com
One problem that I pointed out before and then you can add
Acked-by: Jason Wessel jason.wes...@windriver.com
---
include/linux/kdb.h |1 +
include/linux/kgdb.h|1 +
kernel/debug/debug_core.c | 30 +-
kernel
On 09/05/2013 05:50 PM, Mike Travis wrote:
> This patch adds a new "KDB_REASON" code (KDB_REASON_SYSTEM_NMI). This
> is purely cosmetic to distinguish it from the other various reasons that
> NMI may occur and are usually after an error occurred. Also the dumping
> of registers is not done to
On 09/05/2013 05:50 PM, Mike Travis wrote:
> This patch adds a kgdb_nmicallin() interface that can be used by
> external NMI handlers to call the KGDB/KDB handler. The primary need
> for this is for those types of NMI interrupts where all the CPUs
> have already received the NMI signal.
On 09/05/2013 05:50 PM, Mike Travis wrote:
This patch adds a kgdb_nmicallin() interface that can be used by
external NMI handlers to call the KGDB/KDB handler. The primary need
for this is for those types of NMI interrupts where all the CPUs
have already received the NMI signal. Therefore no
On 09/05/2013 05:50 PM, Mike Travis wrote:
This patch adds a new KDB_REASON code (KDB_REASON_SYSTEM_NMI). This
is purely cosmetic to distinguish it from the other various reasons that
NMI may occur and are usually after an error occurred. Also the dumping
of registers is not done to more
Commit-ID: 8f76fcd902e3b3a7d6f6c695cc8bc053579eb179
Gitweb: http://git.kernel.org/tip/8f76fcd902e3b3a7d6f6c695cc8bc053579eb179
Author: Jason Wessel
AuthorDate: Mon, 15 Jul 2013 15:27:53 -0500
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 7 Aug 2013 17:35:41 -0300
perf machine
Commit-ID: 8f76fcd902e3b3a7d6f6c695cc8bc053579eb179
Gitweb: http://git.kernel.org/tip/8f76fcd902e3b3a7d6f6c695cc8bc053579eb179
Author: Jason Wessel jason.wes...@windriver.com
AuthorDate: Mon, 15 Jul 2013 15:27:53 -0500
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Wed
kvm report that has no guest symbols
resolved.
This patch changes the failure to locate kernel modules to be
non-fatal.
Signed-off-by: Jason Wessel
---
tools/perf/util/machine.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/tools/perf/util/machine.c b/tools/perf/util
kvm report that has no guest symbols
resolved.
This patch changes the failure to locate kernel modules to be
non-fatal.
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
tools/perf/util/machine.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/tools/perf/util
On 04/09/2013 08:06 AM, Sedat Dilek wrote:
> config DEBUG_RODATA
> bool "Write protect kernel read-only data structures"
> - default y
> depends on DEBUG_KERNEL
> + default n if KGDB
> + default y
> ---help---
> Mark the kernel read-only data as
On 04/09/2013 08:06 AM, Sedat Dilek wrote:
config DEBUG_RODATA
bool Write protect kernel read-only data structures
- default y
depends on DEBUG_KERNEL
+ default n if KGDB
+ default y
---help---
Mark the kernel read-only data as write-protected in the
On 03/25/2013 01:50 PM, Mike Travis wrote:
> Currently the default for the # of lines displayed by the KDB pager
> is 24. This does not allow all of the lines for the entry messages,
> reg dump and process trace. Increase it to something more reasonable.
>
Unfortunately this is something that
On 03/25/2013 01:50 PM, Mike Travis wrote:
> The KDB 'btc' (backtrace cpus) command ignores the 'quit' reply
> to the 'more>' prompt. This is quite annoying when you have a
> large number of processors and thousands of lines are being
> printed. This fixes that problem.
>
Merged to kgdb-next
On 03/25/2013 01:50 PM, Mike Travis wrote:
The KDB 'btc' (backtrace cpus) command ignores the 'quit' reply
to the 'more' prompt. This is quite annoying when you have a
large number of processors and thousands of lines are being
printed. This fixes that problem.
Merged to kgdb-next and
On 03/25/2013 01:50 PM, Mike Travis wrote:
Currently the default for the # of lines displayed by the KDB pager
is 24. This does not allow all of the lines for the entry messages,
reg dump and process trace. Increase it to something more reasonable.
Unfortunately this is something that
On 03/11/2013 09:09 AM, Steven Rostedt wrote:
> This is Jason's code.
>
> Jason, please give an Ack or Nack.
>
> Thanks,
>
> -- Steve
>
>
> On Mon, 2013-03-11 at 15:13 +0800, zhangwei(Jovi) wrote:
>> trace_empty is checking in while-loop, so the previous checking
>> is totally redundant, and more
On 03/11/2013 09:09 AM, Steven Rostedt wrote:
This is Jason's code.
Jason, please give an Ack or Nack.
Thanks,
-- Steve
On Mon, 2013-03-11 at 15:13 +0800, zhangwei(Jovi) wrote:
trace_empty is checking in while-loop, so the previous checking
is totally redundant, and more worse, the
and CROSS_CURSES_INC solves the issue and allowing
compiling and linking against the right headers and libraries.
Signed-off-by: Jason Wessel
cc: Michal Marek
cc: linux-kbu...@vger.kernel.org
---
scripts/kconfig/lxdialog/check-lxdialog.sh |8
1 file changed, 8 insertions(+)
diff --git a/scripts
and CROSS_CURSES_INC solves the issue and allowing
compiling and linking against the right headers and libraries.
Signed-off-by: Jason Wessel jason.wes...@windriver.com
cc: Michal Marek mma...@suse.cz
cc: linux-kbu...@vger.kernel.org
---
scripts/kconfig/lxdialog/check-lxdialog.sh |8
1 file changed
ppc64 support for kgdbts
Add missing kconfig option from original kdb port for dealing with
catastrophic kernel crashes such that you can reboot automatically
on continue from kdb
Jason Wessel (4):
kdb: Fix
ppc64 support for kgdbts
Add missing kconfig option from original kdb port for dealing with
catastrophic kernel crashes such that you can reboot automatically
on continue from kdb
Jason Wessel (4):
kdb: Fix
On 01/14/2013 11:26 AM, Cong Ding wrote:
> the variable backup_current_thread_info isn't freed before existing the
> function.
>
> Signed-off-by: Cong Ding
> ---
> arch/powerpc/kernel/kgdb.c |5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git
On 01/14/2013 11:26 AM, Cong Ding wrote:
the variable backup_current_thread_info isn't freed before existing the
function.
Signed-off-by: Cong Ding ding...@gmail.com
---
arch/powerpc/kernel/kgdb.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git
On 01/18/2013 07:31 AM, Vineet Gupta wrote:
> On Friday 18 January 2013 06:45 PM, Jason Wessel wrote:
>> On 01/18/2013 06:25 AM, Vineet Gupta wrote:
>>> From: Mischa Jonker
>>>
>>> Signed-off-by: Mischa Jonker
>>> Signed-off-by: Vineet Gupta
&g
On 01/18/2013 06:25 AM, Vineet Gupta wrote:
> From: Mischa Jonker
>
> Signed-off-by: Mischa Jonker
> Signed-off-by: Vineet Gupta
> Cc: Jason Wessel
Acked-by: Jason Wessel
> ---
> arch/arc/Kconfig|3 +-
> arch/arc/include/asm/kgdb.h | 61
On 01/18/2013 06:25 AM, Vineet Gupta wrote:
From: Mischa Jonker mjon...@synopsys.com
Signed-off-by: Mischa Jonker mjon...@synopsys.com
Signed-off-by: Vineet Gupta vgu...@synopsys.com
Cc: Jason Wessel jason.wes...@windriver.com
Acked-by: Jason Wessel jason.wes...@windriver.com
---
arch
On 01/18/2013 07:31 AM, Vineet Gupta wrote:
On Friday 18 January 2013 06:45 PM, Jason Wessel wrote:
On 01/18/2013 06:25 AM, Vineet Gupta wrote:
From: Mischa Jonker mjon...@synopsys.com
Signed-off-by: Mischa Jonker mjon...@synopsys.com
Signed-off-by: Vineet Gupta vgu...@synopsys.com
Cc
On 10/23/2012 03:01 PM, Kees Cook wrote:
> This config item has not carried much meaning for a while now and is
> almost always enabled by default. As agreed during the Linux kernel
> summit, remove it.
>
Works for me.
Acked-by: Jason Wessel
Cheers,
Jason.
--
To unsubscribe fr
On 10/23/2012 03:01 PM, Kees Cook wrote:
This config item has not carried much meaning for a while now and is
almost always enabled by default. As agreed during the Linux kernel
summit, remove it.
Works for me.
Acked-by: Jason Wessel jason.wes...@windriver.com
Cheers,
Jason
Allow kgdboc=kdb to setup kdb on the vga console
Arnd Bergmann (1):
tty/console: fix warnings in drivers/tty/serial/kgdboc.c
Jason Wessel (6):
kgdb: Add module event hooks
mips,kgdb: fix recursive page fault
Allow kgdboc=kdb to setup kdb on the vga console
Arnd Bergmann (1):
tty/console: fix warnings in drivers/tty/serial/kgdboc.c
Jason Wessel (6):
kgdb: Add module event hooks
mips,kgdb: fix recursive page fault
s/tty/serial/kgdboc.c:293:3: warning: statement with no effect
> [-Wunused-value]
Thanks Arnd!
I'll put this in kgdb-next for the upcoming merge window, unless Greg pulls it
into his queue first.
Acked-by: Jason Wessel
Cheers,
Jason.
--
To unsubscribe from this list: send the line "unsubs
1 - 100 of 317 matches
Mail list logo