From: Paolo Bonzini <pbonzini@redhat.com>
To: Liviu Ionescu <ilg@livius.net>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <Qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Better Cortex-M support?
Date: Wed, 29 Oct 2014 16:31:20 +0100 [thread overview]
Message-ID: <54510848.3080004@redhat.com> (raw)
In-Reply-To: <90E1040E-DDA8-47BC-8F52-2CF803E6D4C8@livius.net>
On 10/29/2014 04:18 PM, Liviu Ionescu wrote:
>
> On 29 Oct 2014, at 17:11, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
>> On 10/28/2014 03:40 PM, Peter Maydell wrote:
>>> I think writes via gdb will be treated in the same way as
>>> writes by the CPU (ie interpreted as attempts to program
>>> the flash device). QEMU doesn't support a "debug access"
>>> abstraction.
>>
>> I think they should work right. See cpu_memory_rw_debug.
>
> I'm not sure I can follow you. do you mean there is a recent patch that fixed this?
>
> otherwise, according to my tests, when the GDB session is active, the semihosting output is no longer displayed in the qemu console.
That's due to usage of the breakpoint instruction, as Peter pointed out.
I mean that writes to ROM or flash via gdb should modify the ROM
directly, unlike writes by the CPU.
Paolo
next prev parent reply other threads:[~2014-10-29 15:31 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 10:43 [Qemu-devel] Better Cortex-M support? Liviu Ionescu
2014-10-28 12:22 ` Peter Maydell
2014-10-28 12:40 ` Liviu Ionescu
2014-10-28 12:45 ` Peter Maydell
2014-10-28 12:52 ` Liviu Ionescu
2014-10-28 12:57 ` Peter Maydell
2014-10-28 13:23 ` Liviu Ionescu
2014-10-28 13:45 ` Peter Maydell
2014-10-28 13:54 ` Liviu Ionescu
2014-10-28 14:18 ` Peter Maydell
2014-10-28 14:37 ` Liviu Ionescu
2014-10-28 14:40 ` Peter Maydell
2014-10-28 14:50 ` Liviu Ionescu
2014-10-28 14:59 ` Peter Maydell
2014-10-28 15:03 ` Peter Maydell
2014-10-28 15:22 ` Liviu Ionescu
2014-10-28 15:38 ` Peter Maydell
2014-10-28 16:38 ` Liviu Ionescu
2014-10-28 17:08 ` Peter Maydell
2014-10-29 7:17 ` Liviu Ionescu
2014-10-29 13:28 ` Christopher Covington
2014-10-29 14:48 ` Andreas Färber
2014-10-29 14:55 ` Peter Maydell
2014-10-29 15:11 ` Paolo Bonzini
2014-10-29 15:18 ` Liviu Ionescu
2014-10-29 15:31 ` Paolo Bonzini [this message]
2014-10-29 16:37 ` Liviu Ionescu
2014-10-29 18:13 ` Paolo Bonzini
2014-10-29 7:03 ` Liviu Ionescu
2014-10-29 10:31 ` Peter Maydell
2014-10-29 12:01 ` Liviu Ionescu
2014-11-04 12:05 ` Fabien Chouteau
2014-11-04 12:19 ` Alistair Francis
2014-11-11 21:56 ` Liviu Ionescu
2014-11-11 23:08 ` Peter Maydell
2014-11-12 12:50 ` Liviu Ionescu
2014-11-12 13:02 ` Peter Maydell
2014-11-12 13:43 ` Liviu Ionescu
2014-11-12 13:51 ` Peter Maydell
2014-11-12 14:23 ` Liviu Ionescu
2014-11-13 0:11 ` Alistair Francis
2014-11-13 7:48 ` Liviu Ionescu
2014-11-14 1:01 ` Alistair Francis
2014-11-14 7:32 ` Liviu Ionescu
2014-12-01 0:39 ` Alistair Francis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54510848.3080004@redhat.com \
--to=pbonzini@redhat.com \
--cc=Qemu-devel@nongnu.org \
--cc=ilg@livius.net \
--cc=peter.maydell@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).