From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Jan Kiszka" <jan.kiszka@siemens.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
lig.fnst@cn.fujitsu.com
Subject: [Qemu-devel] [PATCH qom-cpu v6 0/4] target-i386: Clean up DR7 breakpoint handling
Date: Tue, 15 Jan 2013 09:29:54 +0100 [thread overview]
Message-ID: <1358238598-31451-1-git-send-email-afaerber@suse.de> (raw)
Hello Guang,
Are you okay with this version?
Regards,
Andreas
v5 -> v6:
* Fix bisectability by deferring use of hw_{local,global}_breakpoint_enabled().
* Reword the commit messages for clarity.
* Squash more constant usage into first patch.
* Reorder DATA_RW and DATA_WR to match original switch cases.
* Untangle introduction of breakpoint helper functions from goto/if refactorings.
* Make hw_breakpoint_enabled() return bool.
* Keep IO_RW in place for patch readability.
* Keep reg variable name for patch readability.
* Move {bp,wp}_match inside loop to clarify scope and to avoid double false init.
* Make check_hw_breakpoints() return bool, change force_dr6_update arg to bool.
changes v4->v5:
- fix some not well formated changes.
- split functional and non-functional changes for cherry-picking
suggested by Andreas Färber <afaerber@suse.de>
changes v3->v4:
- fix wrong logic of hw_{global,local}_breakpoint_enabled usage
suggested by Peter Maydell <peter.maydell@linaro.org>
changes v2->v3:
- split hw_breakpoint_enabled into hw_{global,local}_breakpoint_enabled
changes v1->v2:
- add _TYPE_ to the name of dr7 bit field
- fix some coding styles
suggested by Peter Maydell <peter.maydell@linaro.org>
Cc: liguang <lig.fnst@cn.fujitsu.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Peter Maydell <peter.maydell@linaro.org>
liguang (4):
target-i386: Define DR7 bit field constants
target-i386: Introduce hw_{local,global}_breakpoint_enabled()
target-i386: Avoid goto in hw_breakpoint_insert()
target-i386: Use switch in check_hw_breakpoints()
target-i386/cpu.h | 23 ++++++++++--
target-i386/helper.c | 87 +++++++++++++++++++++++++++++----------------
target-i386/machine.c | 5 +--
target-i386/misc_helper.c | 6 ++--
target-i386/seg_helper.c | 9 ++---
5 Dateien geändert, 88 Zeilen hinzugefügt(+), 42 Zeilen entfernt(-)
--
1.7.10.4
next reply other threads:[~2013-01-15 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 8:29 Andreas Färber [this message]
2013-01-15 8:29 ` [Qemu-devel] [PATCH qom-cpu v6 1/4] target-i386: Define DR7 bit field constants Andreas Färber
2013-01-15 8:29 ` [Qemu-devel] [PATCH qom-cpu v6 2/4] target-i386: Introduce hw_{local, global}_breakpoint_enabled() Andreas Färber
2013-01-15 8:29 ` [Qemu-devel] [PATCH qom-cpu v6 3/4] target-i386: Avoid goto in hw_breakpoint_insert() Andreas Färber
2013-01-15 8:29 ` [Qemu-devel] [PATCH qom-cpu v6 4/4] target-i386: Use switch in check_hw_breakpoints() Andreas Färber
2013-01-15 8:49 ` [Qemu-devel] [PATCH qom-cpu v6 0/4] target-i386: Clean up DR7 breakpoint handling li guang
2013-01-15 9:18 ` Andreas Färber
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=1358238598-31451-1-git-send-email-afaerber@suse.de \
--to=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=lig.fnst@cn.fujitsu.com \
--cc=peter.maydell@linaro.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).