| To: | dean gaudet <dean@xxxxxxxxxx> |
|---|---|
| Subject: | [xfs-masters] Re: Interaction between Xen and XFS: stray RW mappings |
| From: | Nick Piggin <nickpiggin@xxxxxxxxxxxx> |
| Date: | Mon, 22 Oct 2007 14:39:21 +1000 |
| Cc: | Jeremy Fitzhardinge <jeremy@xxxxxxxx>, David Chinner <dgc@xxxxxxx>, xfs@xxxxxxxxxxx, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Mark Williamson <mark.williamson@xxxxxxxxxxxx>, Morten Bøgeskov <xen-users@xxxxxxxxxxxxxxxxxx>, xfs-masters@xxxxxxxxxxx |
| Domainkey-signature: | a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au; h=Received:X-YMail-OSG:From:To:Subject:Date:User-Agent:Cc:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id; b=POTxb7XtXDXVXF5OmqUaS+Q1uOttvO41sgih9zniHHooeCWFQMsgSADrNWCNRPI88dsI3jP6SGwLTW/vnD0Ew6PEuj9OAGMl8amKO1442F45WUIO/MKXpftUB4345IfbCxPcL0iuGF4rXemigiub9Y74dAXXFk8nv23FPNILyo0= ; |
| In-reply-to: | <alpine.DEB.0.9999.0710212128180.2320@twinlark.arctic.org> |
| References: | <470FA7C3.90404@goop.org> <471C1A61.1010001@goop.org> <alpine.DEB.0.9999.0710212128180.2320@twinlark.arctic.org> |
| Reply-to: | xfs-masters@xxxxxxxxxxx |
| Sender: | xfs-masters-bounce@xxxxxxxxxxx |
| User-agent: | KMail/1.9.5 |
On Monday 22 October 2007 14:28, dean gaudet wrote: > On Sun, 21 Oct 2007, Jeremy Fitzhardinge wrote: > > dean gaudet wrote: > > > On Mon, 15 Oct 2007, Nick Piggin wrote: > > >> Yes, as Dave said, vmap (more specifically: vunmap) is very expensive > > >> because it generally has to invalidate TLBs on all CPUs. > > > > > > why is that? ignoring 32-bit archs we have heaps of address space > > > available... couldn't the kernel just burn address space and delay > > > global TLB invalidate by some relatively long time (say 1 second)? > > > > Yes, that's precisely the problem. xfs does delay the unmap, leaving > > stray mappings, which upsets Xen. > > sounds like a bug in xen to me :) You could call it a bug I think. I don't know much about Xen though, whether or not it expects to be able to run an arbitrary OS kernel. Presumably, the hypervisor _could_ write protect and trap writes to *all* page table page mappings. |
| Previous by Date: | [xfs-masters] Re: Interaction between Xen and XFS: stray RW mappings, dean gaudet |
|---|---|
| Next by Date: | [xfs-masters] Re: Interaction between Xen and XFS: stray RW mappings, Andi Kleen |
| Previous by Thread: | [xfs-masters] Re: Interaction between Xen and XFS: stray RW mappings, dean gaudet |
| Next by Thread: | [xfs-masters] Re: Interaction between Xen and XFS: stray RW mappings, Jeremy Fitzhardinge |
| Indexes: | [Date] [Thread] [Top] [All Lists] |