From: Andres Lagar-Cavilla <andres@lagarcavilla.org>
To: xen-devel@lists.xensource.com
Cc: andres@gridcentric.ca, keir.xen@gmail.com, tim@xen.org,
olaf@aepfle.de, adin@gridcentric.ca
Subject: [PATCH 3 of 4] Make the prototype of p2m_mem_access_resume consistent
Date: Mon, 14 Nov 2011 16:58:33 -0500 [thread overview]
Message-ID: <106296812c3f8981d4b6.1321307913@xdev.gridcentric.ca> (raw)
In-Reply-To: <patchbomb.1321307910@xdev.gridcentric.ca>
xen/arch/x86/mm/mem_access.c | 3 +--
xen/arch/x86/mm/p2m.c | 3 +--
xen/include/asm-x86/p2m.h | 2 +-
3 files changed, 3 insertions(+), 5 deletions(-)
Signed-off-by: Adin Scannell <adin@scannell.ca>
Signed-off-by: Keir Fraser <keir@xen.org>
Signed-off-by: Andres Lagar-Cavilla <andres@lagarcavilla.org>
diff -r b3cdfb5b76d0 -r 106296812c3f xen/arch/x86/mm/mem_access.c
--- a/xen/arch/x86/mm/mem_access.c
+++ b/xen/arch/x86/mm/mem_access.c
@@ -29,13 +29,12 @@ int mem_access_domctl(struct domain *d,
XEN_GUEST_HANDLE(void) u_domctl)
{
int rc;
- struct p2m_domain *p2m = p2m_get_hostp2m(d);
switch( mec->op )
{
case XEN_DOMCTL_MEM_EVENT_OP_ACCESS_RESUME:
{
- p2m_mem_access_resume(p2m);
+ p2m_mem_access_resume(d);
rc = 0;
}
break;
diff -r b3cdfb5b76d0 -r 106296812c3f xen/arch/x86/mm/p2m.c
--- a/xen/arch/x86/mm/p2m.c
+++ b/xen/arch/x86/mm/p2m.c
@@ -1150,9 +1150,8 @@ void p2m_mem_access_check(unsigned long
/* VCPU paused */
}
-void p2m_mem_access_resume(struct p2m_domain *p2m)
+void p2m_mem_access_resume(struct domain *d)
{
- struct domain *d = p2m->domain;
mem_event_response_t rsp;
/* Pull all responses off the ring */
diff -r b3cdfb5b76d0 -r 106296812c3f xen/include/asm-x86/p2m.h
--- a/xen/include/asm-x86/p2m.h
+++ b/xen/include/asm-x86/p2m.h
@@ -493,7 +493,7 @@ static inline void p2m_mem_paging_popula
void p2m_mem_access_check(unsigned long gpa, bool_t gla_valid, unsigned long gla,
bool_t access_r, bool_t access_w, bool_t access_x);
/* Resumes the running of the VCPU, restarting the last instruction */
-void p2m_mem_access_resume(struct p2m_domain *p2m);
+void p2m_mem_access_resume(struct domain *d);
/* Set access type for a region of pfns.
* If start_pfn == -1ul, sets the default access type */
next prev parent reply other threads:[~2011-11-14 21:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 21:58 [PATCH 0 of 4] Mem event handling improvements Andres Lagar-Cavilla
2011-11-14 21:58 ` [PATCH 1 of 4] Improve ring management for memory events Andres Lagar-Cavilla
2011-11-23 18:35 ` Olaf Hering
2011-11-23 18:52 ` Andres Lagar-Cavilla
2011-11-23 18:57 ` Olaf Hering
2011-11-24 18:54 ` Andres Lagar-Cavilla
2011-11-24 19:23 ` Olaf Hering
2011-11-24 19:35 ` Andres Lagar-Cavilla
2011-11-14 21:58 ` [PATCH 2 of 4] Create a generic callback mechanism for Xen-bound event channels Andres Lagar-Cavilla
2011-11-14 21:58 ` Andres Lagar-Cavilla [this message]
2011-11-14 21:58 ` [PATCH 4 of 4] Allow memevent responses to be signaled via the event channel Andres Lagar-Cavilla
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=106296812c3f8981d4b6.1321307913@xdev.gridcentric.ca \
--to=andres@lagarcavilla.org \
--cc=adin@gridcentric.ca \
--cc=andres@gridcentric.ca \
--cc=keir.xen@gmail.com \
--cc=olaf@aepfle.de \
--cc=tim@xen.org \
--cc=xen-devel@lists.xensource.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 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).