xen-changelog

[Top] [All Lists]

[Xen-changelog] Different dom_mem_op for non-VTI (at least until discuss

from [BitKeeper Bot]

[Permanent Link][Original]

To:	xen-changelog@xxxxxxxxxxxxxxxxxxx
Subject:	[Xen-changelog] Different dom_mem_op for non-VTI (at least until discussed)
From:	BitKeeper Bot <riel@xxxxxxxxxxx>
Date:	Tue, 14 Jun 2005 18:49:01 +0000
Delivery-date:	Sun, 19 Jun 2005 18:03:10 +0000
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-changelog-request@lists.xensource.com?subject=help>
List-id:	BK change log <xen-changelog.lists.xensource.com>
List-post:	<mailto:xen-changelog@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=unsubscribe>
Reply-to:	Xen Development List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Sender:	xen-changelog-bounces@xxxxxxxxxxxxxxxxxxx

ChangeSet 1.1709.1.8, 2005/06/14 12:49:01-06:00, djm@xxxxxxxxxxxxxxx

        Different dom_mem_op for non-VTI (at least until discussed)



 hypercall.c |    4 ++++
 1 files changed, 4 insertions(+)


diff -Nru a/xen/arch/ia64/hypercall.c b/xen/arch/ia64/hypercall.c
--- a/xen/arch/ia64/hypercall.c 2005-06-19 14:04:18 -04:00
+++ b/xen/arch/ia64/hypercall.c 2005-06-19 14:04:18 -04:00
@@ -126,8 +126,12 @@
                break;
 
            case __HYPERVISOR_dom_mem_op:
+#ifdef CONFIG_VTI
                regs->r8 = do_dom_mem_op(regs->r14, regs->r15, regs->r16, 
regs->r17, regs->r18); 
+#else
+               /* we don't handle reservations; just return success */
                regs->r8 = regs->r16;
+#endif
                break;
 
            case __HYPERVISOR_event_channel_op:

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-changelog] Different dom_mem_op for non-VTI (at least until discussed), BitKeeper Bot <=

Previous by Date:	[Xen-changelog] XEN/VTI utilizes a PMT table to describe physical->machine, BitKeeper Bot
Next by Date:	[Xen-changelog] ia64: Fix incorrect mapping bug; caused infrequent crashes, BitKeeper Bot
Previous by Thread:	[Xen-changelog] XEN/VTI utilizes a PMT table to describe physical->machine, BitKeeper Bot
Next by Thread:	[Xen-changelog] ia64: Fix incorrect mapping bug; caused infrequent crashes, BitKeeper Bot
Indexes:	[Date] [Thread] [Top] [All Lists]