From: Alex Williamson <alex.williamson@hp.com>
To: Keir Fraser <keir@xensource.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
xen-ia64-devel <xen-ia64-devel@lists.xensource.com>
Subject: Please pull xen-ia64-unstable.hg
Date: Tue, 24 Apr 2007 10:57:15 -0600 [thread overview]
Message-ID: <1177433835.14349.41.camel@bling> (raw)
Hi Keir,
We've got one patch in the tree that we'd like to try to get into
3.0.5. Please pull:
http://xenbits.xensource.com/ext/xen-ia64-unstable.hg
and if you don't plan another sweep of xen-unstable, please import the
patch below into http://xenbits.xensource.com/xen-3.0.5-testing.hg
Thanks,
Alex
# HG changeset patch
# User Alex Williamson <alex.williamson@hp.com>
# Date 1177427244 21600
# Node ID ef5da9ca01711045a9206fcbc884bf11508dde45
# Parent 039daabebad5d3c69fb9497693e8e3fd4fee00c9
[IA64] Fix ptc.g race
If one vcpu is executing ptc.g, while the other vcpu is executing itc,
the VHPT(VTLB) entry which should be purged may unexpectedly survive.
Then issue happens.
Signed-off-by: Anthony Xu <anthony.xu@intel.com>
diff -r 039daabebad5 -r ef5da9ca0171 xen/arch/ia64/vmx/vtlb.c
--- a/xen/arch/ia64/vmx/vtlb.c Fri Apr 13 16:07:48 2007 +0100
+++ b/xen/arch/ia64/vmx/vtlb.c Tue Apr 24 09:07:24 2007 -0600
@@ -168,6 +168,7 @@ static void vmx_vhpt_insert(thash_cb_t *
else{
cch = __alloc_chain(hcb);
}
+ local_irq_disable();
*cch = *head;
head->page_flags=pte;
head->itir = rr.ps << 2;
@@ -175,6 +176,7 @@ static void vmx_vhpt_insert(thash_cb_t *
head->next = cch;
head->len = cch->len+1;
cch->len = 0;
+ local_irq_enable();
return;
}
@@ -424,14 +426,14 @@ void vtlb_insert(VCPU *v, u64 pte, u64 i
else {
cch = __alloc_chain(hcb);
}
- *cch = *hash_table;
- hash_table->page_flags = pte;
- hash_table->itir=itir;
- hash_table->etag=tag;
+ cch->page_flags = pte;
+ cch->itir = itir;
+ cch->etag = tag;
+ cch->next = hash_table->next;
+ wmb();
hash_table->next = cch;
- hash_table->len = cch->len + 1;
- cch->len = 0;
- return ;
+ hash_table->len += 1;
+ return;
}
next reply other threads:[~2007-04-24 16:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 16:57 Alex Williamson [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-17 15:01 Please pull xen-ia64-unstable.hg Alex Williamson
2007-05-21 20:36 ` Alex Williamson
2007-04-13 15:01 Alex Williamson
2007-04-12 17:44 Alex Williamson
2007-04-11 14:23 Alex Williamson
2007-04-09 20:41 Alex Williamson
2007-04-06 16:50 Alex Williamson
2007-04-03 19:46 Alex Williamson
2007-03-27 21:21 Alex Williamson
2007-03-28 2:34 ` Isaku Yamahata
2007-03-22 16:46 Alex Williamson
2007-02-22 18:12 Alex Williamson
2007-02-07 19:18 Alex Williamson
2007-01-18 5:59 please " Alex Williamson
2006-12-08 20:36 Alex Williamson
2006-12-09 13:47 ` Keir Fraser
2006-12-14 17:28 ` Alex Williamson
2006-11-14 22:54 Alex Williamson
2006-10-25 22:47 Alex Williamson
2006-09-10 22:17 Alex Williamson
2006-09-12 18:54 ` Alex Williamson
2006-08-29 15:47 Alex Williamson
2006-08-09 16:57 Alex Williamson
2006-07-27 18:09 Alex Williamson
2006-07-28 9:53 ` Keir Fraser
2006-07-28 12:26 ` Alex Williamson
2006-06-28 21:32 Alex Williamson
2006-06-16 16:57 Alex Williamson
2006-05-31 22:44 Alex Williamson
2006-05-22 21:32 Alex Williamson
2006-04-26 19:54 Alex Williamson
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=1177433835.14349.41.camel@bling \
--to=alex.williamson@hp.com \
--cc=keir@xensource.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-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 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.