From: Tamas K Lengyel <tamas.lengyel@zentific.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Tim Deegan <tim@xen.org>, "Tian, Kevin" <kevin.tian@intel.com>,
wei.liu2@citrix.com, Ian Campbell <Ian.Campbell@citrix.com>,
Razvan Cojocaru <rcojocaru@bitdefender.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
"Dong, Eddie" <eddie.dong@intel.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Steven Maresca <steve@zentific.com>,
Andres Lagar-Cavilla <andres@lagarcavilla.org>,
Jun Nakajima <jun.nakajima@intel.com>,
rshriram@cs.ubc.ca, Keir Fraser <keir@xen.org>,
Daniel De Graaf <dgdegra@tycho.nsa.gov>,
yanghy@cn.fujitsu.com
Subject: Re: [RFC PATCH V3 01/12] xen/mem_event: Cleanup of mem_event structures
Date: Thu, 5 Feb 2015 13:12:24 +0100 [thread overview]
Message-ID: <CAErYnsjpgApTeAzQmGETA=k67RX3Dk_RZX6r5u1e7OLFzmfj=w@mail.gmail.com> (raw)
In-Reply-To: <54D0A03C020000780005C426@mail.emea.novell.com>
On Tue, Feb 3, 2015 at 10:17 AM, Jan Beulich <JBeulich@suse.com> wrote:
>>>> On 02.02.15 at 18:19, <Ian.Campbell@citrix.com> wrote:
>> On Thu, 2015-01-29 at 22:46 +0100, Tamas K Lengyel wrote:
>>> + union {
>>> + struct mem_event_paging_data mem_paging;
>>> + struct mem_event_sharing_data mem_sharing;
>>> + struct mem_event_mem_access_data mem_access;
>>> + struct mem_event_mov_to_cr_data mov_to_cr;
>>> + struct mem_event_mov_to_msr_data mov_to_msr;
>>> + struct mem_event_software_breakpoint_data software_breakpoint;
>>> + struct mem_event_singlestep_data singlestep;
>>> + } data;
>>
>> We typically call these unions "u" but that's up to the hypervisor guys
>> really.
>
> And yes, I agree we should be consistent with things like this.
>
> Jan
Ack.
next prev parent reply other threads:[~2015-02-05 12:12 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 21:46 [RFC PATCH V3 00/12] xen: Clean-up of mem_event subsystem Tamas K Lengyel
2015-01-29 21:46 ` [RFC PATCH V3 01/12] xen/mem_event: Cleanup of mem_event structures Tamas K Lengyel
2015-02-02 17:19 ` Ian Campbell
2015-02-03 9:17 ` Jan Beulich
2015-02-05 12:12 ` Tamas K Lengyel [this message]
2015-02-05 12:13 ` Tamas K Lengyel
2015-02-03 15:32 ` Jan Beulich
2015-01-29 21:46 ` [RFC PATCH V3 02/12] xen/mem_event: Rename the mem_event ring from 'access' to 'monitor' Tamas K Lengyel
2015-02-02 17:22 ` Ian Campbell
2015-02-03 15:37 ` Jan Beulich
2015-02-05 14:24 ` Tamas K Lengyel
2015-01-29 21:46 ` [RFC PATCH V3 03/12] xen/mem_paging: Convert mem_event_op to mem_paging_op Tamas K Lengyel
2015-02-02 17:23 ` Ian Campbell
2015-02-03 15:41 ` Jan Beulich
2015-01-29 21:46 ` [RFC PATCH V3 04/12] xen/mem_access: Merge mem_event sanity check into mem_access check Tamas K Lengyel
2015-01-29 21:46 ` [RFC PATCH V3 05/12] xen: Introduce vm_event Tamas K Lengyel
2015-01-30 17:25 ` Daniel De Graaf
2015-01-31 13:24 ` Tamas K Lengyel
2015-02-02 19:35 ` Daniel De Graaf
2015-02-06 14:04 ` Tamas K Lengyel
2015-02-02 17:27 ` Ian Campbell
2015-02-03 15:54 ` Jan Beulich
2015-02-06 13:54 ` Tamas K Lengyel
2015-02-06 13:58 ` Andrew Cooper
2015-02-06 14:01 ` Tamas K Lengyel
2015-01-29 21:46 ` [RFC PATCH V3 06/12] xen: migrate mem_event to vm_event Tamas K Lengyel
2015-02-02 17:27 ` Ian Campbell
2015-02-03 16:22 ` Jan Beulich
2015-01-29 21:46 ` [RFC PATCH V3 07/12] xen: Remove mem_event Tamas K Lengyel
2015-01-30 17:25 ` Daniel De Graaf
2015-02-02 17:29 ` Ian Campbell
2015-02-03 16:26 ` Jan Beulich
2015-02-06 12:54 ` Tamas K Lengyel
2015-02-06 14:18 ` Jan Beulich
2015-02-06 16:13 ` Tamas K Lengyel
2015-01-29 21:46 ` [RFC PATCH V3 08/12] tools/tests: Clean-up tools/tests/xen-access Tamas K Lengyel
2015-02-02 17:30 ` Ian Campbell
2015-01-29 21:46 ` [RFC PATCH V3 09/12] x86/hvm: factor out and rename vm_event related functions into separate file Tamas K Lengyel
2015-02-04 5:54 ` Tian, Kevin
2015-02-04 9:14 ` Jan Beulich
2015-01-29 21:46 ` [RFC PATCH V3 10/12] xen: Introduce monitor_op domctl Tamas K Lengyel
2015-01-30 7:58 ` Razvan Cojocaru
2015-01-30 10:38 ` Tamas K Lengyel
2015-01-30 11:07 ` Razvan Cojocaru
2015-01-30 11:15 ` Tamas K Lengyel
2015-01-30 11:24 ` Tamas K Lengyel
2015-01-30 11:33 ` Razvan Cojocaru
2015-01-30 11:45 ` Tamas K Lengyel
2015-01-30 12:24 ` Razvan Cojocaru
2015-01-30 12:36 ` Tamas K Lengyel
2015-02-02 17:32 ` Ian Campbell
2015-02-04 5:57 ` Tian, Kevin
2015-02-04 9:34 ` Jan Beulich
2015-02-05 14:15 ` Tamas K Lengyel
2015-02-09 18:45 ` Tamas K Lengyel
2015-01-29 21:46 ` [RFC PATCH V3 11/12] xen/vm_event: Decouple vm_event and mem_access Tamas K Lengyel
2015-02-04 9:47 ` Jan Beulich
2015-02-06 13:10 ` Tamas K Lengyel
2015-02-06 14:20 ` Jan Beulich
2015-02-06 16:12 ` Tamas K Lengyel
2015-01-29 21:46 ` [RFC PATCH V3 12/12] xen/vm_event: Check for VM_EVENT_FLAG_DUMMY only in Debug builds Tamas K Lengyel
2015-02-04 5:59 ` Tian, Kevin
2015-02-06 13:20 ` Tamas K Lengyel
2015-02-04 9:49 ` Jan Beulich
2015-02-06 13:22 ` Tamas K Lengyel
2015-02-02 17:33 ` [RFC PATCH V3 00/12] xen: Clean-up of mem_event subsystem Ian Campbell
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='CAErYnsjpgApTeAzQmGETA=k67RX3Dk_RZX6r5u1e7OLFzmfj=w@mail.gmail.com' \
--to=tamas.lengyel@zentific.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andres@lagarcavilla.org \
--cc=dgdegra@tycho.nsa.gov \
--cc=eddie.dong@intel.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=rcojocaru@bitdefender.com \
--cc=rshriram@cs.ubc.ca \
--cc=stefano.stabellini@eu.citrix.com \
--cc=steve@zentific.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yanghy@cn.fujitsu.com \
/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.