[v2] Make the dcache (code/stack cache) handle line reading errors better
Commit Message
On 05/21/2014 07:51 AM, Metzger, Markus T wrote:
>> -----Original Message-----
>> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
>> owner@sourceware.org] On Behalf Of Pedro Alves
>> Sent: Tuesday, May 20, 2014 7:15 PM
>
>> 8<---------------
>> From: Pedro Alves <palves@redhat.com>
>> Date: Tue, 20 May 2014 12:26:01 +0100
>> Subject: [PATCH] Make the dcache (code/stack cache) handle line reading
>> errors
>> better.
>>
>> The dcache (code/stack cache) is supposed to be transparent, but it's
>> actually not in one case. dcache tries to read chunks (cache lines)
>> at a time off of the target. This may end up trying to read
>> unaccessible or unavailable memory. Currently the caller an xfer error
>
> 'gets' is missing.
Thanks, fixed. I've fixed a couple typos in the test .c file as well.
>
>> in this case. But if the specific bits of memory the caller actually
>> wanted are available and accessible, then the caller should get the
>> memory it wanted, not an error.
>
>
>> + Copyright 2012-2014 Free Software Foundation, Inc.
>
> Why 2012-?
Because the file was originally copied from
gdb.base/find-unmapped.c and it still retains bits under
2012-2014 copyright.
>
>
>> +void *first_mapped_page;
>> +void *first_unmapped_page;
>> +void *last_mapped_page;
>> +void *last_unmapped_page;
>
> The _unmapped_page variants seem not to be used.
Ah, they were needed in an earlier version. Thanks, removed.
>
>
>> + /* Disassembling 0s should behave on all targets. */
>> + memset (p, 0, pg_count * pg_size);
>
> Shouldn't be necessary. The pages are supposed to be zero-initialized.
Indeed, removed. (find-unmapped.c also has it)
>
>
>> +# Test that dcache behaves correctly when reading a cache line fails.
>> +
>> +standard_testfile
>> +
>> +if { [prepare_for_testing "failed to prepare" ${testfile}] } {
>
> And I always thought you had to supply $srcfile, as well. Can
> prepare_for_testing derive the source name from the executable name
> and some path magic?
Yeah:
# Prepares for testing, by calling build_executable, and then clean_restart.
# Please refer to build_executable for parameter description.
proc prepare_for_testing { testname executable {sources ""} {options {debug}}} {
if {[build_executable $testname $executable $sources $options] == -1} {
return -1
}
{sources ""} is how one specifies optional arguments. "" is the default
in this case. And then:
# Build executable named EXECUTABLE, from SOURCES. If SOURCES are not
# provided, uses $EXECUTABLE.c. The TESTNAME paramer is the name of test
# to pass to untested, if something is wrong. OPTIONS are passed
# to gdb_compile directly.
proc build_executable { testname executable {sources ""} {options {debug}} } {
if {[llength $sources]==0} {
set sources ${executable}.c
}
Hmm, for standard_testfile tests, looks like we could even
make $testname and $executable be optional arguments.
>
>
>> +proc disassemble { what } {
>> + global hex gdb_prompt
>> +
>> + set cmd "disassemble $what"
>> + gdb_test_multiple $cmd $cmd {
>> + -re "Cannot access memory.*$gdb_prompt $" {
>> + fail $cmd
>> + }
>> + -re "End of assembler dump\.\r\n$gdb_prompt $" {
>> + pass $cmd
>> + }
>
> Wouldn't simply checking for "End of assembler dump\.\r\n" suffice?
Yeah. I was just being explicit, but indeed there's no need.
I've now switched to just use gdb_test.
> Wouldn't it even be more robust as it would catch all kinds of errors?
Nope, gdb_test_multiple issues a FAIL if none of the passed in patterns
match. And it wouldn't normally timeout internally gdb_test_multiple's
issues a FAIL if it sees:
-re "\r\n$gdb_prompt $" {
...
fail "$message"
...
}
Below's v2. Let me know how it looks.
8<----------------
>From f433bc8ad604afa15421c10a7387503257eb9754 Mon Sep 17 00:00:00 2001
From: Pedro Alves <palves@redhat.com>
Date: Tue, 20 May 2014 12:26:01 +0100
Subject: [PATCH] Make the dcache (code/stack cache) handle line reading errors
better
The dcache (code/stack cache) is supposed to be transparent, but it's
actually not in one case. dcache tries to read chunks (cache lines)
at a time off of the target. This may end up trying to read
unaccessible or unavailable memory. Currently the caller gets an xfer
error in this case. But if the specific bits of memory the caller
actually wanted are available and accessible, then the caller should
get the memory it wanted, not an error.
gdb/
2014-05-21 Pedro Alves <palves@redhat.com>
* dcache.c (dcache_read_memory_partial): If reading the cache line
fails, fallback to reading just the memory the caller wanted.
gdb/testsuite/
2014-05-21 Pedro Alves <palves@redhat.com>
* gdb.base/dcache-line-read-error.c: New.
* gdb.base/dcache-line-read-error.exp: New.
---
gdb/dcache.c | 7 +-
gdb/testsuite/gdb.base/dcache-line-read-error.c | 107 ++++++++++++++++++++++
gdb/testsuite/gdb.base/dcache-line-read-error.exp | 68 ++++++++++++++
3 files changed, 180 insertions(+), 2 deletions(-)
create mode 100644 gdb/testsuite/gdb.base/dcache-line-read-error.c
create mode 100644 gdb/testsuite/gdb.base/dcache-line-read-error.exp
Comments
> -----Original Message-----
> From: Pedro Alves [mailto:palves@redhat.com]
> Sent: Wednesday, May 21, 2014 11:45 AM
> To: Metzger, Markus T
> Below's v2. Let me know how it looks.
Looks good to me.
Thanks,
Markus.
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
On 05/21/2014 12:28 PM, Metzger, Markus T wrote:
>> -----Original Message-----
>> From: Pedro Alves [mailto:palves@redhat.com]
>> Sent: Wednesday, May 21, 2014 11:45 AM
>> To: Metzger, Markus T
>
>
>> Below's v2. Let me know how it looks.
>
> Looks good to me.
Great, now pushed.
Thanks,
@@ -497,8 +497,11 @@ dcache_read_memory_partial (struct target_ops *ops, DCACHE *dcache,
if (i == 0)
{
- /* FIXME: We lose the real error status. */
- return TARGET_XFER_E_IO;
+ /* Even though reading the whole line failed, we may be able to
+ read a piece starting where the caller wanted. */
+ return ops->to_xfer_partial (ops, TARGET_OBJECT_MEMORY, NULL,
+ myaddr, NULL, memaddr, len,
+ xfered_len);
}
else
{
new file mode 100644
@@ -0,0 +1,107 @@
+/* This testcase is part of GDB, the GNU debugger.
+
+ Copyright 2012-2014 Free Software Foundation, Inc.
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 3 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see <http://www.gnu.org/licenses/>. */
+
+#include <stdlib.h>
+#include <stdio.h>
+#include <sys/mman.h>
+#include <unistd.h>
+#include <string.h>
+
+size_t pg_size;
+void *first_mapped_page;
+void *last_mapped_page;
+
+void
+breakpt (void)
+{
+ /* Nothing. */
+}
+
+int
+main (void)
+{
+ void *p;
+ int pg_count;
+ size_t i;
+
+ /* Map 6 contiguous pages, and then unmap all second first, and
+ second last.
+
+ From GDB we will disassemble each of the _mapped_ pages, with a
+ code-cache (dcache) line size bigger than the page size (twice
+ bigger). This makes GDB try to read one page before the mapped
+ page once, and the page after another time. GDB should give no
+ error in either case.
+
+ That is, depending on where the kernel aligns the pages, we get
+ either:
+
+ .---.---.---.---.---.---.
+ | U | M | U | U | M | U |
+ '---'---'---'---'---'---.
+ | | | | <- line alignment
+ ^^^^^^^ ^^^^^^^
+ | |
+ + line1 + line2
+
+ Or:
+
+ .---.---.---.---.---.---.
+ | U | M | U | U | M | U |
+ '---'---'---'---'---'---.
+ | | | <- line alignment
+ ^^^^^^^ ^^^^^^^
+ | |
+ line1 + + line2
+
+ Note we really want to test that dcache behaves correctly when
+ reading a cache line fails. We're just using unmapped memory as
+ proxy for any kind of error. */
+
+ pg_size = getpagesize ();
+ pg_count = 6;
+
+ p = mmap (0, pg_count * pg_size, PROT_READ|PROT_WRITE,
+ MAP_ANONYMOUS|MAP_PRIVATE, -1, 0);
+ if (p == MAP_FAILED)
+ {
+ perror ("mmap");
+ return EXIT_FAILURE;
+ }
+
+ /* Leave memory zero-initialized. Disassembling 0s should behave on
+ all targets. */
+
+ for (i = 0; i < pg_count; i++)
+ {
+ if (i == 1 || i == 4)
+ continue;
+
+ if (munmap (p + (i * pg_size), pg_size) == -1)
+ {
+ perror ("munmap");
+ return EXIT_FAILURE;
+ }
+ }
+
+ first_mapped_page = p + 1 * pg_size;;
+ last_mapped_page = p + 4 * pg_size;
+
+ breakpt ();
+
+ return EXIT_SUCCESS;
+}
new file mode 100644
@@ -0,0 +1,68 @@
+# Copyright 2014 Free Software Foundation, Inc.
+
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program. If not, see <http://www.gnu.org/licenses/>.
+
+# Test that dcache behaves correctly when reading a cache line fails.
+
+standard_testfile
+
+if { [prepare_for_testing "failed to prepare" ${testfile}] } {
+ return -1
+}
+
+if ![runto breakpt] {
+ return -1
+}
+
+# Issue the "delete mem" command. This makes GDB ignore the
+# target-provided list, if any.
+
+proc delete_mem {} {
+ global gdb_prompt
+
+ set test "delete mem"
+ gdb_test_multiple $test $test {
+ -re "Delete all memory regions.*y or n.*$" {
+ send_gdb "y\n"
+ exp_continue
+ }
+ -re "$gdb_prompt $" {
+ pass $test
+ }
+ }
+}
+
+# Make the dcache line size bigger than the pagesize.
+set pagesize [get_integer_valueof "pg_size" -1]
+set linesize [expr $pagesize * 2]
+
+gdb_test_no_output "set dcache line-size $linesize" \
+ "set dcache line size to twice the pagesize"
+
+gdb_test "info dcache" \
+ "Dcache 4096 lines of $linesize bytes each.\r\nNo data cache available."
+
+# Make sure dcache doesn't automatically skip unmapped regions.
+delete_mem
+
+gdb_test "info mem" \
+ "Using user-defined memory regions.\r\nThere are no memory regions defined\."
+
+# Given the line size is bigger than the page size, we have
+# alternating mapped and unmapped pages, these make dcache fail to
+# fill in the cache line. GDB used to have a bug where that failure
+# would end up as user-visible error. The range being disassembled is
+# wholly available, so GDB should succeed.
+gdb_test "disassemble first_mapped_page, +10" "End of assembler dump\."
+gdb_test "disassemble last_mapped_page, +10" "End of assembler dump\."