From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Zachary Amsden <zach@vmware.com>
Cc: Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] Bugfix for VMI paravirt ops
Date: Thu, 05 Apr 2007 17:52:17 -0700 [thread overview]
Message-ID: <461599C1.50002@goop.org> (raw)
In-Reply-To: <4615982A.1070700@vmware.com>
Zachary Amsden wrote:
> Yes, thought about several solutions, and this seems the best. But it
> requires a new paravirt-op.
Not with the power of multiplexing. Something like this, perhaps?
J
diff -r 5be4a5ff8e6b arch/i386/mm/highmem.c
--- a/arch/i386/mm/highmem.c Thu Apr 05 17:04:04 2007 -0700
+++ b/arch/i386/mm/highmem.c Thu Apr 05 17:50:46 2007 -0700
@@ -42,6 +42,8 @@ void *kmap_atomic_prot(struct page *page
vaddr = __fix_to_virt(FIX_KMAP_BEGIN + idx);
set_pte(kmap_pte-idx, mk_pte(page, prot));
+
+ arch_flush_lazy_mmu_mode();
return (void*) vaddr;
}
diff -r 5be4a5ff8e6b include/asm-generic/pgtable.h
--- a/include/asm-generic/pgtable.h Thu Apr 05 17:04:04 2007 -0700
+++ b/include/asm-generic/pgtable.h Thu Apr 05 17:50:46 2007 -0700
@@ -180,6 +180,7 @@ static inline void ptep_set_wrprotect(st
#ifndef __HAVE_ARCH_ENTER_LAZY_MMU_MODE
#define arch_enter_lazy_mmu_mode() do {} while (0)
#define arch_leave_lazy_mmu_mode() do {} while (0)
+#define arch_flush_lazy_mmu_mode() do {} while (0)
#endif
/*
@@ -193,6 +194,7 @@ static inline void ptep_set_wrprotect(st
#ifndef __HAVE_ARCH_ENTER_LAZY_CPU_MODE
#define arch_enter_lazy_cpu_mode() do {} while (0)
#define arch_leave_lazy_cpu_mode() do {} while (0)
+#define arch_flush_lazy_cpu_mode() do {} while (0)
#endif
/*
diff -r 5be4a5ff8e6b include/asm-i386/paravirt.h
--- a/include/asm-i386/paravirt.h Thu Apr 05 17:04:04 2007 -0700
+++ b/include/asm-i386/paravirt.h Thu Apr 05 17:50:46 2007 -0700
@@ -27,9 +27,10 @@ struct desc_struct;
/* Lazy mode for batching updates / context switch */
enum paravirt_lazy_mode {
- PARAVIRT_LAZY_NONE = 0,
- PARAVIRT_LAZY_MMU = 1,
- PARAVIRT_LAZY_CPU = 2,
+ PARAVIRT_LAZY_NONE = 0, /* exit lazy mode */
+ PARAVIRT_LAZY_MMU = 1, /* lazy mmu updates */
+ PARAVIRT_LAZY_CPU = 2, /* lazy cpu state updates */
+ PARAVIRT_LAZY_FLUSH = 3, /* flush pending changes, if any */
};
struct paravirt_ops
@@ -1044,6 +1045,10 @@ static inline void arch_leave_lazy_cpu_m
{
PVOP_VCALL1(set_lazy_mode, PARAVIRT_LAZY_NONE);
}
+static inline void arch_flush_lazy_cpu_mode(void)
+{
+ PVOP_VCALL1(set_lazy_mode, PARAVIRT_LAZY_FLUSH);
+}
#define __HAVE_ARCH_ENTER_LAZY_MMU_MODE
static inline void arch_enter_lazy_mmu_mode(void)
@@ -1053,6 +1058,10 @@ static inline void arch_leave_lazy_mmu_m
static inline void arch_leave_lazy_mmu_mode(void)
{
PVOP_VCALL1(set_lazy_mode, PARAVIRT_LAZY_NONE);
+}
+static inline void arch_flush_lazy_mmu_mode(void)
+{
+ PVOP_VCALL1(set_lazy_mode, PARAVIRT_LAZY_FLUSH);
}
void _paravirt_nop(void);
next prev parent reply other threads:[~2007-04-06 0:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 23:29 [PATCH] Bugfix for VMI paravirt ops Zachary Amsden
2007-04-05 23:34 ` Zachary Amsden
2007-04-05 23:55 ` Andrew Morton
2007-04-05 23:54 ` Andi Kleen
2007-04-06 0:01 ` Zachary Amsden
2007-04-06 0:08 ` Jeremy Fitzhardinge
2007-04-06 0:09 ` Zachary Amsden
2007-04-06 0:14 ` Jeremy Fitzhardinge
2007-04-06 0:20 ` Zachary Amsden
2007-04-06 0:33 ` Jeremy Fitzhardinge
2007-04-06 0:45 ` Zachary Amsden
2007-04-06 0:52 ` Jeremy Fitzhardinge [this message]
2007-04-06 0:54 ` Zachary Amsden
2007-04-06 1:31 ` Jeremy Fitzhardinge
2007-04-06 1:32 ` Zachary Amsden
2007-04-06 1:36 ` Jeremy Fitzhardinge
2007-04-06 1:42 ` Zachary Amsden
2007-04-06 1:19 ` Zachary Amsden
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=461599C1.50002@goop.org \
--to=jeremy@goop.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=zach@vmware.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