From: Alexandru Isaila <aisaila@bitdefender.com>
To: xen-devel@lists.xen.org
Cc: jun.nakajima@intel.com, kevin.tian@intel.com,
sstabellini@kernel.org, wei.liu2@citrix.com,
suravee.suthikulpanit@amd.com, george.dunlap@eu.citrix.com,
andrew.cooper3@citrix.com, tim@xen.org, paul.durrant@citrix.com,
jbeulich@suse.com, boris.ostrovsky@oracle.com,
ian.jackson@eu.citrix.com
Subject: [PATCH v4 0/3] Various XSA followups
Date: Wed, 20 Sep 2017 12:22:30 +0300 [thread overview]
Message-ID: <1505899353-13554-1-git-send-email-aisaila@bitdefender.com> (raw)
XSA-219 was discovered while trying to implement the bugfix in patch 3.
Andrew Cooper (3):
[RFC] x86/hvm: Rename enum hvm_copy_result to hvm_translation_result
x86/hvm: Break out __hvm_copy()'s translation logic
x86/hvm: Implement hvmemul_write() using real mappings
Alexandru Isaila (2):
x86/hvm: Break out __hvm_copy()'s translation logic
x86/hvm: Implement hvmemul_write() using real mappings
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2017-09-20 9:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 9:22 Alexandru Isaila [this message]
2017-09-20 9:22 ` [PATCH v4 1/3] x86/hvm: Rename enum hvm_copy_result to hvm_translation_result Alexandru Isaila
2017-09-20 9:44 ` Jan Beulich
2017-09-20 12:29 ` Ping: " Jan Beulich
2017-09-20 13:01 ` Boris Ostrovsky
2017-09-20 9:22 ` [PATCH v4 2/3] x86/hvm: Break out __hvm_copy()'s translation logic Alexandru Isaila
2017-09-20 9:22 ` [PATCH v4 3/3] x86/hvm: Implement hvmemul_write() using real mappings Alexandru Isaila
2017-09-20 9:30 ` Paul Durrant
2017-09-20 12:24 ` Jan Beulich
2017-09-20 12:38 ` Alexandru Stefan ISAILA
2017-09-20 14:37 ` Paul Durrant
2017-09-25 8:00 ` Alexandru Stefan ISAILA
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=1505899353-13554-1-git-send-email-aisaila@bitdefender.com \
--to=aisaila@bitdefender.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=paul.durrant@citrix.com \
--cc=sstabellini@kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.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.