From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>,
Jailhouse <jailhouse-dev@googlegroups.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Philippe Mathieu-Daudé" <philippe@mathieu-daude.net>,
"Alistair Francis" <alistair23@gmail.com>
Subject: Re: [Qemu-devel] Call for GSoC & Outreachy 2018 mentors & project ideas
Date: Wed, 21 Feb 2018 11:08:02 +0000 [thread overview]
Message-ID: <CAJSP0QVNp-wAG4foPaK+XhAeFTa1iaBtqNKSLBhKOwQHPcXJug@mail.gmail.com> (raw)
In-Reply-To: <030fbb91-837b-9817-dc87-28dade530cf3@redhat.com>
On Tue, Feb 20, 2018 at 11:13 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 20/02/2018 11:36, Stefan Hajnoczi wrote:
>> === Multi-CPU cluster support for GDB server in QEMU ===
>>
>> There are many examples in modern computing where multiple CPU
>> clusters are grouped together in a single SoC. This is common in the
>> ARM world especially. There are numerous examples such as ARM's
>> big.LITTLE implementations and Xilinx's 4xA53s and 2xR5s on the ZynqMP
>> SoC. The goal of this task is to add support to the GDB server to
>> allow users to debug across these clusters.
>>
>> This is another step towards single binary QEMU as well.
>>
>> Detailed description of the project.
>>
>> Xilinx has an out of tree implementation that can be used as a
>> starting point. Work will need to be done on top of this to prepare it
>> for upstream submission and to ensure the implementation is more
>> generic.
>>
>> This will mostly involve extending GDB server to tell GDB about
>> different architectures and then allow the user to swap between them.
>>
>> The Xilinx implementation can be seen here:
>> https://github.com/Xilinx/qemu/blob/master/gdbstub.c
>> There has been some steps in preparing the work to go upstream, which
>> can be seen here:
>> https://github.com/Xilinx/qemu/tree/mainline/alistair/gdb
>
> I agree this is interesting.
Thanks! I have added it to the wiki:
https://wiki.qemu.org/Google_Summer_of_Code_2018#Multi-CPU_cluster_support_for_GDB_server_in_QEMU
Stefan
next prev parent reply other threads:[~2018-02-21 11:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 20:23 [Qemu-devel] Call for GSoC & Outreachy 2018 mentors & project ideas Stefan Hajnoczi
2018-01-09 21:45 ` Alistair Francis
2018-01-10 1:58 ` Fam Zheng
2018-01-10 12:52 ` Stefan Hajnoczi
2018-01-11 23:25 ` Alistair Francis
2018-01-15 12:59 ` Stefan Hajnoczi
2018-02-14 19:00 ` Alistair Francis
2018-02-20 10:36 ` Stefan Hajnoczi
2018-02-20 11:13 ` Paolo Bonzini
2018-02-21 1:19 ` Alistair Francis
2018-02-21 11:08 ` Stefan Hajnoczi [this message]
2018-02-27 23:54 ` Philippe Mathieu-Daudé
2018-03-05 9:11 ` Stefan Hajnoczi
2018-01-18 16:49 ` David Hildenbrand
2018-01-24 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=CAJSP0QVNp-wAG4foPaK+XhAeFTa1iaBtqNKSLBhKOwQHPcXJug@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=alistair23@gmail.com \
--cc=f4bug@amsat.org \
--cc=jailhouse-dev@googlegroups.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philippe@mathieu-daude.net \
--cc=qemu-devel@nongnu.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).