From: Michael Tokarev <mjt@tls.msk.ru>
To: Riku Voipio <riku.voipio@iki.fi>
Cc: qemu-trivial@nongnu.org, peter.maydell@linaro.org,
Hunter Laux <hunterlaux@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-trivial] [PATCH v2] Add support for the arm breakpoint syscall
Date: Wed, 25 Jun 2014 12:20:15 +0400 [thread overview]
Message-ID: <53AA863F.9000306@msgid.tls.msk.ru> (raw)
In-Reply-To: <20140624185420.GA23788@afflict.kos.to>
24.06.2014 22:54, Riku Voipio wrote:
> On Tue, Jun 24, 2014 at 07:58:36PM +0400, Michael Tokarev wrote:
>> 20.06.2014 15:13, Hunter Laux wrote:
>>> OABI arm used a software interrupt(0xef9f0001) for breakpoints.
>>> Since 2005 gdb has used the break instruction(0xe7f001f0) for EABI.
>>> Apparently Steel Bank Common Lisp still uses the swi instruction.
>
>> Applied to -trivial, despite the ugliness with the goto. Oh well.
>
> It was already in my yesterdays linux-user pull req ( which I need
> to resend with the name_to_handle_at/open_by_handle_at syscalls fixed ).
If it is the same patch, git should do the Right Thing when
pulling your branch, without causing conflicts.
You could notify me about you applying this patch to -linux-user
branch. I haven't noticed this patch in your pull req, -- I don't
always watch all pull requests.
Thanks,
/mjt
WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Riku Voipio <riku.voipio@iki.fi>
Cc: qemu-trivial@nongnu.org, peter.maydell@linaro.org,
Hunter Laux <hunterlaux@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH v2] Add support for the arm breakpoint syscall
Date: Wed, 25 Jun 2014 12:20:15 +0400 [thread overview]
Message-ID: <53AA863F.9000306@msgid.tls.msk.ru> (raw)
In-Reply-To: <20140624185420.GA23788@afflict.kos.to>
24.06.2014 22:54, Riku Voipio wrote:
> On Tue, Jun 24, 2014 at 07:58:36PM +0400, Michael Tokarev wrote:
>> 20.06.2014 15:13, Hunter Laux wrote:
>>> OABI arm used a software interrupt(0xef9f0001) for breakpoints.
>>> Since 2005 gdb has used the break instruction(0xe7f001f0) for EABI.
>>> Apparently Steel Bank Common Lisp still uses the swi instruction.
>
>> Applied to -trivial, despite the ugliness with the goto. Oh well.
>
> It was already in my yesterdays linux-user pull req ( which I need
> to resend with the name_to_handle_at/open_by_handle_at syscalls fixed ).
If it is the same patch, git should do the Right Thing when
pulling your branch, without causing conflicts.
You could notify me about you applying this patch to -linux-user
branch. I haven't noticed this patch in your pull req, -- I don't
always watch all pull requests.
Thanks,
/mjt
next prev parent reply other threads:[~2014-06-25 8:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 11:13 [Qemu-trivial] [PATCH v2] Add support for the arm breakpoint syscall Hunter Laux
2014-06-20 11:13 ` [Qemu-devel] " Hunter Laux
2014-06-20 11:16 ` [Qemu-trivial] " Peter Maydell
2014-06-20 11:16 ` [Qemu-devel] " Peter Maydell
2014-06-24 15:58 ` [Qemu-trivial] " Michael Tokarev
2014-06-24 15:58 ` [Qemu-devel] " Michael Tokarev
2014-06-24 18:54 ` Riku Voipio
2014-06-24 18:54 ` [Qemu-devel] " Riku Voipio
2014-06-25 8:20 ` Michael Tokarev [this message]
2014-06-25 8:20 ` Michael Tokarev
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=53AA863F.9000306@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=hunterlaux@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=riku.voipio@iki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.