qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: li guang <lig.fnst@cn.fujitsu.com>
To: ehabkost@redhat.com
Cc: imammedo@redhat.com, afaerber@suse.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 1/3] target-i386:define name of breakpoint bit in dr7
Date: Fri, 14 Dec 2012 09:32:59 +0800	[thread overview]
Message-ID: <1355448779.5552.1.camel@liguang.fnst.cn.fujitsu.com> (raw)
In-Reply-To: <1355106144-30846-1-git-send-email-lig.fnst@cn.fujitsu.com>

Hi, 

any comment on this version?

在 2012-12-10一的 10:22 +0800,liguang写道:
> Signed-off-by: liguang <lig.fnst@cn.fujitsu.com>
> ---
>  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

-- 
regards!
li guang

  parent reply	other threads:[~2012-12-14  1:35 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 ` li guang [this message]
2013-01-11  1:47 ` [Qemu-devel] [PATCH v4 1/3] target-i386:define name of breakpoint bit in dr7 li guang
2013-01-11 16:00   ` Andreas Färber
2013-01-11 16:10 ` Andreas Färber
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=1355448779.5552.1.camel@liguang.fnst.cn.fujitsu.com \
    --to=lig.fnst@cn.fujitsu.com \
    --cc=afaerber@suse.de \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --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).