From: Corneliu ZUZU <czuzu@bitdefender.com>
To: xen-devel@lists.xen.org
Cc: Kevin Tian <kevin.tian@intel.com>,
Tamas K Lengyel <tamas@tklengyel.com>, Keir Fraser <keir@xen.org>,
Ian Campbell <ian.campbell@citrix.com>,
Razvan Cojocaru <rcojocaru@bitdefender.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: [PATCH 0/7] Vm-events: move monitor vm-events code to common code.
Date: Mon, 8 Feb 2016 19:06:41 +0200 [thread overview]
Message-ID: <56B8CB21.9020005@bitdefender.com> (raw)
In-Reply-To: <1454950682-9459-1-git-send-email-czuzu@bitdefender.com>
On 2/8/2016 6:57 PM, Corneliu ZUZU wrote:
> This patch series is an attempt to move (most) of the monitor vm-events code to
> the common-side.
>
> Patches summary:
>
> 1. Move xen/arch/arm/hvm.c to xen/arch/arm/hvm/hvm.c
>
> 2. Merge almost identical functions hvm_event_int3 + hvm_event_single_step ->
> hvm_event_software_breakpoint.
>
> 3. Add Kconfigs:
> HAS_VM_EVENT_WRITE_CTRLREG, HAS_VM_EVENT_SINGLESTEP,
> HAS_VM_EVENT_SOFTWARE_BREAKPOINT, HAS_VM_EVENT_GUEST_REQUEST
> and move monitor_domctl to common-side. Used the Kconfigs to selectively
> activate implemented monitor vm-events code for each architecture.
>
> 4. Some file renames. Read (*) below.
>
> 5. Move hvm_event_traps, hvm_event_cr, hvm_event_guest_request,
> hvm_event_software_breakpoint functions to common-side.
> (note: arch_hvm_event_fill_regs on ARM-side will be implemented in a separate
> patch)
>
> 6. Some file renames, plus some minor fixes. Read (*) below.
>
> 7. Move monitor bitfield members from struct arch_domain to struct domain.
> Moved bits: single-step, software-breakpoint and guest-request.
> (note: write_ctrlreg_* were left on the arch-side, since control-registers
> number can vary across architectures)
>
> (*) was only necessary to avoid git seeing a file as being modified, rather than
> moved (would have made the diff unnecessarily bulky).
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>
Somehow git send-email managed to malform the introductory message.
Corrections made, read above instead :)
prev parent reply other threads:[~2016-02-08 17:06 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 16:57 [PATCH 0/7] Vm-events: move monitor vm-events code to common code Corneliu ZUZU
2016-02-08 16:57 ` [PATCH 1/7] arm: move arch/arm/hvm.c to arch/arm/hvm/hvm.c Corneliu ZUZU
2016-02-08 17:04 ` Andrew Cooper
2016-02-08 17:12 ` Corneliu ZUZU
2016-02-08 17:14 ` Andrew Cooper
2016-02-09 11:03 ` Stefano Stabellini
2016-02-09 11:28 ` Corneliu ZUZU
2016-02-09 11:55 ` Jan Beulich
2016-02-09 12:22 ` Stefano Stabellini
2016-02-09 12:32 ` Corneliu ZUZU
2016-02-09 17:40 ` Tamas K Lengyel
2016-02-09 19:19 ` Corneliu ZUZU
2016-02-08 16:57 ` [PATCH 2/7] x86: hvm events: merge 2 functions into 1 Corneliu ZUZU
2016-02-08 17:15 ` Andrew Cooper
2016-02-08 17:30 ` Tamas K Lengyel
2016-02-08 17:49 ` Corneliu ZUZU
2016-02-08 18:17 ` Tamas K Lengyel
2016-02-08 18:45 ` Corneliu ZUZU
2016-02-09 11:19 ` Jan Beulich
2016-02-09 11:52 ` Corneliu ZUZU
2016-02-09 12:12 ` Jan Beulich
2016-02-09 12:24 ` Corneliu ZUZU
2016-02-08 16:57 ` [PATCH 3/7] xen/vm-events: Move monitor_domctl to common-side Corneliu ZUZU
2016-02-08 18:15 ` Tamas K Lengyel
2016-02-08 18:43 ` Corneliu ZUZU
2016-02-08 18:50 ` Tamas K Lengyel
2016-02-08 16:57 ` [PATCH 4/7] Rename monitor_x86.c to monitor.c and monitor_arch.h to monitor.h Corneliu ZUZU
2016-02-08 18:18 ` Tamas K Lengyel
2016-02-08 18:55 ` Corneliu ZUZU
2016-02-08 16:58 ` [PATCH 5/7] xen/vm-events: Move hvm_event_* functions to common-side Corneliu ZUZU
2016-02-08 16:58 ` [PATCH 6/7] Rename event_x86.c to event.c and event_arch.h to event.h + minor fixes Corneliu ZUZU
2016-02-08 16:58 ` [PATCH 7/7] arch.monitor: move bits to common (arch_domain to domain) Corneliu ZUZU
2016-02-08 18:29 ` Tamas K Lengyel
2016-02-09 7:14 ` Corneliu ZUZU
2016-02-08 17:06 ` Corneliu ZUZU [this message]
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=56B8CB21.9020005@bitdefender.com \
--to=czuzu@bitdefender.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=rcojocaru@bitdefender.com \
--cc=stefano.stabellini@citrix.com \
--cc=tamas@tklengyel.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.