qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, kwolf@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] coroutine: add x86 specific coroutine backend
Date: Mon, 11 Mar 2019 13:35:04 +0100	[thread overview]
Message-ID: <20190311123507.24867-1-pbonzini@redhat.com> (raw)

This is in preparation for CET support for x86.

I know this is very late, but if possible I'd like to have this in 4.0
as an experimental backend.

Paolo Bonzini (3):
  qemugdb: fix licensing
  qemugdb: allow adding support for other coroutine backends
  coroutine: add x86 specific coroutine backend

 configure                             |   8 +
 scripts/qemu-gdb.py                   |   7 +-
 scripts/qemugdb/coroutine.py          | 114 +++++---------
 scripts/qemugdb/coroutine_ucontext.py |  69 +++++++++
 scripts/qemugdb/coroutine_x86.py      |  21 +++
 scripts/qemugdb/mtree.py              |   7 +-
 scripts/qemugdb/tcg.py                |   7 +-
 util/coroutine-x86.c                  | 212 ++++++++++++++++++++++++++
 8 files changed, 350 insertions(+), 95 deletions(-)
 create mode 100644 scripts/qemugdb/coroutine_ucontext.py
 create mode 100644 scripts/qemugdb/coroutine_x86.py
 create mode 100644 util/coroutine-x86.c

-- 
2.20.1

             reply	other threads:[~2019-03-11 12:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11 12:35 Paolo Bonzini [this message]
2019-03-11 12:35 ` [Qemu-devel] [PATCH 1/3] qemugdb: fix licensing Paolo Bonzini
2019-03-11 12:35 ` [Qemu-devel] [PATCH 2/3] qemugdb: allow adding support for other coroutine backends Paolo Bonzini
2019-03-11 12:35 ` [Qemu-devel] [PATCH 3/3] coroutine: add x86 specific coroutine backend Paolo Bonzini
2019-03-11 12:51 ` [Qemu-devel] [PATCH 0/2] " no-reply

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=20190311123507.24867-1-pbonzini@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).