From: "Andreas Färber" <afaerber@suse.de>
To: liguang <lig.fnst@cn.fujitsu.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
imammedo@redhat.com, Jan Kiszka <jan.kiszka@siemens.com>,
ehabkost@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 1/3] target-i386:define name of breakpoint bit in dr7
Date: Fri, 11 Jan 2013 17:10:48 +0100 [thread overview]
Message-ID: <50F03988.3000603@suse.de> (raw)
In-Reply-To: <1355106144-30846-1-git-send-email-lig.fnst@cn.fujitsu.com>
Am 10.12.2012 03:22, schrieb liguang:
> Signed-off-by: liguang <lig.fnst@cn.fujitsu.com>
For a patch series consisting of more than 1 patch, please use a cover
letter (e.g., --cover-letter) that details the change history of the
versions. That also facilitates commenting on the series vs. a single patch.
> ---
> target-i386/cpu.h | 7 +++++++
> 1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/target-i386/cpu.h b/target-i386/cpu.h
> index 90ef1ff..29245d1 100644
> --- a/target-i386/cpu.h
> +++ b/target-i386/cpu.h
> @@ -231,6 +231,13 @@
> #define DR7_TYPE_SHIFT 16
> #define DR7_LEN_SHIFT 18
> #define DR7_FIXED_1 0x00000400
> +#define DR7_LOCAL_BP_MASK 0x55
> +#define DR7_MAX_BP 4
> +#define DR7_TYPE_BP_INST 0x0
> +#define DR7_TYPE_DATA_WR 0x1
> +#define DR7_TYPE_IO_RW 0x2
> +#define DR7_TYPE_DATA_RW 0x3
> +
>
> #define PG_PRESENT_BIT 0
> #define PG_RW_BIT 1
These defines are being introduced but not used in this patch yet. If
you were to replace, e.g., 4 -> DR7_MAX_BP in this patch instead of
patch 3/3, I would see a value in cherry-picking it. Assuming there is
agreement on that name, of course.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-01-11 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 2:22 [Qemu-devel] [PATCH v4 1/3] target-i386:define name of breakpoint bit in dr7 liguang
2012-12-10 2:22 ` [Qemu-devel] [PATCH v4 2/3] target-i386:define hw_{global, local}breakpoint_enabled function liguang
2013-01-11 16:16 ` Andreas Färber
2012-12-10 2:22 ` [Qemu-devel] [PATCH v4 3/3] target-i386:slightly refactor dr7 related function liguang
2013-01-11 16:30 ` Andreas Färber
2012-12-14 1:32 ` [Qemu-devel] [PATCH v4 1/3] target-i386:define name of breakpoint bit in dr7 li guang
2013-01-11 1:47 ` li guang
2013-01-11 16:00 ` Andreas Färber
2013-01-11 16:10 ` Andreas Färber [this message]
2013-01-14 2:39 ` li guang
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=50F03988.3000603@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).