[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH V3 1/3] xen/mem_access: Support for memory-content hiding
- To: "Lengyel, Tamas" <tlengyel@xxxxxxxxxxx>
- From: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>
- Date: Tue, 7 Jul 2015 11:10:49 +0300
- Cc: Jun Nakajima <jun.nakajima@xxxxxxxxx>, Wei Liu <wei.liu2@xxxxxxxxxx>, kevin.tian@xxxxxxxxx, keir@xxxxxxx, Ian Campbell <ian.campbell@xxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>, George Dunlap <george.dunlap@xxxxxxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, eddie.dong@xxxxxxxxx, Xen-devel <xen-devel@xxxxxxxxxxxxx>, Aravind.Gopalakrishnan@xxxxxxx, Jan Beulich <jbeulich@xxxxxxxx>, suravee.suthikulpanit@xxxxxxx, boris.ostrovsky@xxxxxxxxxx, Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
- Comment: DomainKeys? See http://domainkeys.sourceforge.net/
- Delivery-date: Tue, 07 Jul 2015 08:10:30 +0000
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=bitdefender.com; b=Zhvv7akzJid3y+tFRqtc7jnj4xKxM3gQPfZo8Kou0mLDkY5mXhpvmMD9g6YSmnA5GxKl8s/k/VttiTUDJBJxQ8mkvGVxYBBTTjAoo1Ip+ixEZTAB92ss2H0cYTSAaEQj76ZvJd473J8yZPV5cydhcJBHZ94wYkuZbP+ajWOexaMreW3qr64ZCpiuUSKxUxH37kCaNpmzdlYbDn9GVMkkB+YKxMQCfqV63BuvT699fuA5atzqLXWxnwT0fze+p0sCtHY6raZmQRWfO/UxCXRxwkGNPjH1ioKrZyr8/fbNqFgOmBdOPhhOfstRU/fSnnyXus3PTJ+q0jY1kSxKBchAsQ==; h=Received:Received:Received:Received:Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-BitDefender-Scanner:X-BitDefender-Spam:X-BitDefender-SpamStamp:X-BitDefender-CF-Stamp;
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
On 07/06/2015 09:30 PM, Lengyel, Tamas wrote:
> If you'd prefer that I do some ground work for the future (i.e. rename
> MEM_ACCESS constants, etc.), please let me know.
>
>
> Yeap, that sounds reasonable to me.
Any objections to this renaming?
151 #define MEM_ACCESS_EMULATE_NOWRITE (1 << 7)
152 /*
153 * Data is being sent back to the hypervisor in the event response,
to be
154 * returned by the read function when emulating an instruction.
155 * This flag is only useful when combined with MEM_ACCESS_EMULATE or
156 * MEM_ACCESS_EMULATE_NOWRITE.
157 * The flag has been defined here because it is used with mem_access
158 * events, and so should not accidentaly overwrite one of the above.
159 */
160 #define VM_EVENT_FLAG_SET_EMUL_READ_DATA (1 << 8)
Are there any other small changes you'd like to see in this patch?
Thanks,
Razvan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
