qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: [Qemu-devel] [PATCH v2 0/9] target-i386: Implement debug extensions
Date: Fri, 16 Oct 2015 13:23:30 -0300	[thread overview]
Message-ID: <1445012619-23772-1-git-send-email-ehabkost@redhat.com> (raw)

Updated version of the series submitted by Richard Henderson.

With the additional changes, the kvm-unit-tests debug extensions test case
written by Paolo passes all tests except ICEBP.

Changes v1 -> v2:
* Patch 2/9: Included fix from Paolo to make sure dr7 is updated
  after hw_breakpoint_remove() call and before hw_breakpoint_insert()
  call
* New patch (3/9): Ensure bit 10 on DR7 is never cleared
* Patch 6/9: Rebase on top of new version of patch 2/9
* New patch (8/9): Ensure always-1 bits on DR6 can't be cleared
* New patch (9/9): Add DE to TCG_FEATURES

Eduardo Habkost (3):
  target-i386: Ensure bit 10 on DR7 is never cleared
  target-i386: Ensure always-1 bits on DR6 can't be cleared
  target-i386: Add DE to TCG_FEATURES

Richard Henderson (6):
  target-i386: Introduce cpu_x86_update_dr7
  target-i386: Re-introduce optimal breakpoint removal
  target-i386: Move hw_*breakpoint_* functions
  target-i386: Optimize setting dr[0-3]
  target-i386: Handle I/O breakpoints
  target-i386: Check CR4[DE] for processing DR4/DR5

 target-i386/bpt_helper.c | 223 ++++++++++++++++++++++++++++++++++++++---------
 target-i386/cpu.c        |   2 +-
 target-i386/cpu.h        |  35 ++------
 target-i386/helper.h     |   4 +-
 target-i386/machine.c    |   8 +-
 target-i386/seg_helper.c |   8 +-
 target-i386/translate.c  |  30 +++++--
 7 files changed, 224 insertions(+), 86 deletions(-)

-- 
2.1.0

             reply	other threads:[~2015-10-16 16:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 16:23 Eduardo Habkost [this message]
2015-10-16 16:23 ` [Qemu-devel] [PATCH v2 1/9] target-i386: Introduce cpu_x86_update_dr7 Eduardo Habkost
2015-10-16 16:23 ` [Qemu-devel] [PATCH v2 2/9] target-i386: Re-introduce optimal breakpoint removal Eduardo Habkost
2015-10-16 16:23 ` [Qemu-devel] [PATCH v2 3/9] target-i386: Ensure bit 10 on DR7 is never cleared Eduardo Habkost
2015-10-18 22:58   ` Richard Henderson
2015-10-16 16:23 ` [Qemu-devel] [PATCH v2 4/9] target-i386: Move hw_*breakpoint_* functions Eduardo Habkost
2015-10-16 16:23 ` [Qemu-devel] [PATCH v2 5/9] target-i386: Optimize setting dr[0-3] Eduardo Habkost
2015-10-16 16:23 ` [Qemu-devel] [PATCH v2 6/9] target-i386: Handle I/O breakpoints Eduardo Habkost
2015-10-19 17:30   ` Eduardo Habkost
2015-10-19 17:46     ` Richard Henderson
2015-10-19 17:57       ` Eduardo Habkost
2015-10-20 12:04         ` Paolo Bonzini
2015-10-16 16:23 ` [Qemu-devel] [PATCH v2 7/9] target-i386: Check CR4[DE] for processing DR4/DR5 Eduardo Habkost
2015-10-16 16:23 ` [Qemu-devel] [PATCH v2 8/9] target-i386: Ensure always-1 bits on DR6 can't be cleared Eduardo Habkost
2015-10-18 23:05   ` Richard Henderson
2015-10-16 16:23 ` [Qemu-devel] [PATCH v2 9/9] target-i386: Add DE to TCG_FEATURES Eduardo Habkost
2015-10-18 23:06   ` Richard Henderson

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=1445012619-23772-1-git-send-email-ehabkost@redhat.com \
    --to=ehabkost@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).