On 28.06.2010, at 06:39, Matt Evans wrote:
Howdy Alex!
Alexander Graf wrote:
We will soon start and replace instructions from the text section with
other, paravirtualized versions. To ease the readability of those patches
I split out the generic looping and magic page mapping code out.
On Monday 28 June 2010 11:56:08 Avi Kivity wrote:
On 06/28/2010 06:36 AM, Sheng Yang wrote:
Some guest device driver may leverage the Non-Snoop I/O, and explicitly
WBINVD or CLFLUSH to a RAM space. Since migration may occur before WBINVD
or
CLFLUSH, we need to maintain data consistency
On 06/28/2010 09:42 AM, Sheng Yang wrote:
+static void wbinvd_ipi(void *garbage)
+{
+ wbinvd();
+}
Like Jan mentioned, this is quite heavy. What about a clflush() loop
instead? That may take more time, but at least it's preemptible. Of
course, it isn't preemptible in an IPI.
On Monday 28 June 2010 14:56:38 Avi Kivity wrote:
On 06/28/2010 09:42 AM, Sheng Yang wrote:
+static void wbinvd_ipi(void *garbage)
+{
+ wbinvd();
+}
Like Jan mentioned, this is quite heavy. What about a clflush() loop
instead? That may take more time, but at least it's
On 06/28/2010 09:56 AM, Sheng Yang wrote:
On Monday 28 June 2010 14:56:38 Avi Kivity wrote:
On 06/28/2010 09:42 AM, Sheng Yang wrote:
+static void wbinvd_ipi(void *garbage)
+{
+ wbinvd();
+}
Like Jan mentioned, this is quite heavy. What about a clflush() loop
Avi Kivity wrote:
On 06/28/2010 09:42 AM, Sheng Yang wrote:
+static void wbinvd_ipi(void *garbage)
+{
+ wbinvd();
+}
Like Jan mentioned, this is quite heavy. What about a clflush()
loop instead? That may take more time, but at least it's
preemptible. Of course, it isn't preemptible
On Sun Jun 27 around 19:33:52 EST 2010 Alexander Graf wrote:
Am 27.06.2010 um 10:14 schrieb Avi Kivity avi at redhat.com:
On 06/26/2010 02:25 AM, Alexander Graf wrote:
+
+PPC hypercalls
+==
+
+The only viable ways to reliably get from guest context to host
On Monday 28 June 2010 15:08:56 Avi Kivity wrote:
On 06/28/2010 09:56 AM, Sheng Yang wrote:
On Monday 28 June 2010 14:56:38 Avi Kivity wrote:
On 06/28/2010 09:42 AM, Sheng Yang wrote:
+static void wbinvd_ipi(void *garbage)
+{
+ wbinvd();
+}
Like Jan mentioned, this is quite
This function allow user send qmp command with parameters.
e.g. balloon value=1073741824
Also log command to debug.
Signed-off-by: Feng Yang fy...@redhat.com
---
client/tests/kvm/kvm_monitor.py | 32
1 files changed, 24 insertions(+), 8 deletions(-)
diff
On 28.06.2010, at 09:18, Milton Miller wrote:
On Sun Jun 27 around 19:33:52 EST 2010 Alexander Graf wrote:
Am 27.06.2010 um 10:14 schrieb Avi Kivity avi at redhat.com:
On 06/26/2010 02:25 AM, Alexander Graf wrote:
+
+PPC hypercalls
+==
+
+The only viable ways to reliably
On 06/28/2010 10:41 AM, Sheng Yang wrote:
Hm, the manual says (regarding clflush):
Invalidates the cache line that contains the linear address specified
with the source
operand from all levels of the processor cache hierarchy (data and
instruction). The
invalidation is broadcast
(2010/06/27 16:32), Avi Kivity wrote:
On 06/25/2010 10:25 PM, Alexander Graf wrote:
On 23.06.2010, at 08:01, Takuya Yoshikawa wrote:
kvm_get_dirty_log() is a helper function for
kvm_vm_ioctl_get_dirty_log() which
is currently used by ia64 and ppc and the following is what it is doing:
-
On 06/28/2010 10:49 AM, Alexander Graf wrote:
I don't believe we support the kernel actually doing a syscall to itself
anymore, at least on powerpc. The callers call the underlying system
call function, or kernel_thread.
That said, I would suggest we allocate a syscall number for this, as it
On 06/28/2010 09:33 AM, Alexander Graf wrote:
Could you do something similar in module_finalize() to patch loaded modules'
.text sections?
I could, but do we need it? I objdump -d | grep'ed all my modules and didn't
find any need to do so.
You mean even kvm.ko doesn't use
On 28.06.2010, at 10:15, Avi Kivity wrote:
On 06/28/2010 09:33 AM, Alexander Graf wrote:
Could you do something similar in module_finalize() to patch loaded
modules' .text sections?
I could, but do we need it? I objdump -d | grep'ed all my modules and didn't
find any need to do
On 06/26/2010 02:16 AM, Alexander Graf wrote:
Currently the shadow paging code keeps an array of entries it knows about.
Whenever the guest invalidates an entry, we loop through that entry,
trying to invalidate matching parts.
While this is a really simple implementation, it is probably the
On 06/28/2010 11:21 AM, Alexander Graf wrote:
The other alternative I'd see is to reuse an instruction that is not sc. We could for
example pull the mfpvr trick again, but pass a different magic value in the register this
time that tells the hypervisor this is a hypercall.
Or we could
On 06/28/2010 11:23 AM, Alexander Graf wrote:
You mean even kvm.ko doesn't use privileged instructions?
It does, but I don't think it's worth speeding those up. There are only a
couple. Most of the privileged instructions in PPC KVM are statically compiled
into the kernel because we
Some guest device driver may leverage the Non-Snoop I/O, and explicitly
WBINVD or CLFLUSH to a RAM space. Since migration may occur before WBINVD or
CLFLUSH, we need to maintain data consistency either by:
1: flushing cache (wbinvd) when the guest is scheduled out if there is no
wbinvd exit, or
2:
Dong, Eddie wrote:
Avi Kivity wrote:
On 06/28/2010 10:30 AM, Dong, Eddie wrote:
Several milliseconds of non-responsiveness may not be acceptable for
some applications. So I think queue_work_on() and a clflush loop is
better than an IPI and wbinvd.
Probably we should make it configurable.
On 28.06.2010, at 10:28, Avi Kivity wrote:
On 06/26/2010 02:16 AM, Alexander Graf wrote:
Currently the shadow paging code keeps an array of entries it knows about.
Whenever the guest invalidates an entry, we loop through that entry,
trying to invalidate matching parts.
While this is a
On 06/28/2010 11:55 AM, Alexander Graf wrote:
+
+static inline u64 kvmppc_mmu_hash_pte(u64 eaddr) {
+ return hash_64(eaddr PTE_SIZE, HPTEG_HASH_BITS_PTE);
+}
+
+static inline u64 kvmppc_mmu_hash_vpte(u64 vpage) {
+ return hash_64(vpage 0xfULL, HPTEG_HASH_BITS_VPTE);
+}
On 06/27/2010 10:59 AM, Xiao Guangrong wrote:
Xiao Guangrong wrote:
- /*
-* Optimization: for pte sync, if spte was writable the hash
-* lookup is unnecessary (and expensive). Write protection
-* is responsibility of
On 06/28/2010 10:45 AM, Feng Yang wrote:
This function allow user send qmp command with parameters.
e.g. balloon value=1073741824
Also log command to debug.
Signed-off-by: Feng Yang fy...@redhat.com
---
client/tests/kvm/kvm_monitor.py | 32
1 files
Am 28.06.2010 um 11:12 schrieb Avi Kivity a...@redhat.com:
On 06/28/2010 11:55 AM, Alexander Graf wrote:
+
+static inline u64 kvmppc_mmu_hash_pte(u64 eaddr) {
+return hash_64(eaddr PTE_SIZE, HPTEG_HASH_BITS_PTE);
+}
+
+static inline u64 kvmppc_mmu_hash_vpte(u64 vpage) {
+return
nOn 06/28/2010 11:42 AM, Sheng Yang wrote:
Some guest device driver may leverage the Non-Snoop I/O, and explicitly
WBINVD or CLFLUSH to a RAM space. Since migration may occur before WBINVD or
CLFLUSH, we need to maintain data consistency either by:
1: flushing cache (wbinvd) when the guest is
On Mon, Jun 28, 2010 at 12:27:22PM +0300, Avi Kivity wrote:
nOn 06/28/2010 11:42 AM, Sheng Yang wrote:
Some guest device driver may leverage the Non-Snoop I/O, and explicitly
WBINVD or CLFLUSH to a RAM space. Since migration may occur before WBINVD or
CLFLUSH, we need to maintain data
On 06/28/2010 12:27 PM, Alexander Graf wrote:
Am I looking at old code?
Apparently. Check book3s_mmu_*.c
I don't have that pattern.
(another difference is using struct hlist_head instead of list_head,
which I recommend since it saves space)
Hrm. I thought about this quite a bit
On 06/28/2010 12:31 PM, Gleb Natapov wrote:
On Mon, Jun 28, 2010 at 12:27:22PM +0300, Avi Kivity wrote:
nOn 06/28/2010 11:42 AM, Sheng Yang wrote:
Some guest device driver may leverage the Non-Snoop I/O, and explicitly
WBINVD or CLFLUSH to a RAM space. Since migration may occur
On 06/28/2010 11:14 AM, Takuya Yoshikawa wrote:
Best to revert these patches and re-apply when fixed.
Please revert. Sincerely sorry.
I'll fix as soon as possible and re-submit when test on PPC gets OK.
No problem, regressions happen all the time. Lucky Alex caught it so
quickly.
--
On 06/25/2010 03:05 PM, Xiao Guangrong wrote:
In no-direct mapping, we mark sp is 'direct' when we mapping the
guest's larger page, but its access is encoded form upper page-struct
entire not include the last mapping, it will cause access conflict.
For example, have this mapping:
[W]
- Michael Goldish mgold...@redhat.com wrote:
From: Michael Goldish mgold...@redhat.com
To: Feng Yang fy...@redhat.com
Cc: autot...@test.kernel.org, kvm@vger.kernel.org
Sent: Monday, June 28, 2010 5:18:29 PM GMT +08:00 Beijing / Chongqing / Hong
Kong / Urumqi
Subject: Re: [Autotest]
Avi Kivity wrote:
for_each_gfn_indirect_valid_sp(vcpu-kvm, s, gfn, node) {
+if (!can_unsync)
+return 1;
+
What if the page is already unsync? We don't need write protection in
this case.
Avi,
The reason is when we sync children sps, we write-protected
On 06/25/2010 03:06 PM, Xiao Guangrong wrote:
Consider using small page to fit guest's large page mapping:
If the mapping is writable but the dirty flag is not set, we will find
the read-only direct sp and setup the mapping, then if the write #PF
occur, we will mark this mapping writable in the
Avi Kivity wrote:
Looks good, but please split the cleanup from the fix (we'll want to
backport the fix but not the cleanup).
OK, will do it
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On 06/25/2010 03:06 PM, Xiao Guangrong wrote:
After remove a rmap, we should flush all vcpu's tlb
Signed-off-by: Xiao Guangrongxiaoguangr...@cn.fujitsu.com
---
arch/x86/kvm/mmu.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
Avi Kivity wrote:
On 06/28/2010 12:27 PM, Alexander Graf wrote:
Am I looking at old code?
Apparently. Check book3s_mmu_*.c
I don't have that pattern.
It's in this patch.
+static void invalidate_pte(struct kvm_vcpu *vcpu, struct hpte_cache *pte)
+{
+ dprintk_mmu(KVM: Flushing SPT:
-Original Message-
From: Herbert Xu [mailto:herb...@gondor.apana.org.au]
Sent: Sunday, June 27, 2010 2:15 PM
To: Dong, Eddie
Cc: Xin, Xiaohui; Stephen Hemminger; net...@vger.kernel.org;
kvm@vger.kernel.org;
linux-ker...@vger.kernel.org; m...@redhat.com; mi...@elte.hu;
On 06/28/2010 12:55 PM, Alexander Graf wrote:
Avi Kivity wrote:
On 06/28/2010 12:27 PM, Alexander Graf wrote:
Am I looking at old code?
Apparently. Check book3s_mmu_*.c
I don't have that pattern.
It's in this patch.
Yes. Silly me.
+static void
On Mon, Jun 28, 2010 at 05:56:07PM +0800, Xin, Xiaohui wrote:
-Original Message-
From: Herbert Xu [mailto:herb...@gondor.apana.org.au]
Sent: Sunday, June 27, 2010 2:15 PM
To: Dong, Eddie
Cc: Xin, Xiaohui; Stephen Hemminger; net...@vger.kernel.org;
kvm@vger.kernel.org;
Avi Kivity wrote:
Instead of adding a new bit, can you encode the protection in the direct
sp's access bits? So we'll have one sp for read-only or
writeable-but-not-dirty small pages, and another sp for
writeable-and-dirty small pages.
It looks like it can't solve all problems, it fix
Userspace virtio server has the following hack
so guests rely on it, and we have to replicate it, too:
Use port number to detect incoming IPv4 DHCP response packets,
and fill in the checksum for these.
The issue we are solving is that on linux guests, some apps
that use recvmsg with AF_PACKET
On 06/28/2010 01:02 PM, Xiao Guangrong wrote:
Avi Kivity wrote:
Instead of adding a new bit, can you encode the protection in the direct
sp's access bits? So we'll have one sp for read-only or
writeable-but-not-dirty small pages, and another sp for
writeable-and-dirty small pages.
On 06/25/2010 03:06 PM, Xiao Guangrong wrote:
Introduce mmu_topup_memory_cache_atomic(), it support topup memory
cache in atomic context
Can instead preallocate enough for all prefetches, isn't it simpler?
--
error compiling committee.c: too many arguments to function
--
To unsubscribe
On 06/28/2010 12:40 PM, Xiao Guangrong wrote:
Avi Kivity wrote:
for_each_gfn_indirect_valid_sp(vcpu-kvm, s, gfn, node) {
+if (!can_unsync)
+return 1;
+
What if the page is already unsync? We don't need write protection in
this case.
Avi,
The
On Fri, Jun 25, 2010 at 08:07:06PM +0800, Xiao Guangrong wrote:
Support prefetch ptes when intercept guest #PF, avoid to #PF by later
access
If we meet any failure in the prefetch path, we will exit it and
not try other ptes to avoid become heavy path
Note: this speculative will mark page
Avi Kivity wrote:
On 06/28/2010 12:55 PM, Alexander Graf wrote:
Avi Kivity wrote:
On 06/28/2010 12:27 PM, Alexander Graf wrote:
Am I looking at old code?
Apparently. Check book3s_mmu_*.c
I don't have that pattern.
It's in this patch.
Yes. Silly
On 06/28/2010 04:25 PM, Alexander Graf wrote:
Less and simpler code, better reporting through slabtop, less wastage
of partially allocated slab pages.
But it also means that one VM can spill the global slab cache and kill
another VM's mm performance, no?
What do you mean
Avi Kivity wrote:
On 06/28/2010 04:25 PM, Alexander Graf wrote:
Less and simpler code, better reporting through slabtop, less wastage
of partially allocated slab pages.
But it also means that one VM can spill the global slab cache and kill
another VM's mm performance, no?
The telnet service isn't used by kvm-autotest (AFAIK) and may interfere with
rss.exe (port 23).
Signed-off-by: Michael Goldish mgold...@redhat.com
---
client/tests/kvm/unattended/win2003-32.sif | 10 +++-
client/tests/kvm/unattended/win2003-64.sif | 10 +++-
On Mon, Jun 28, 2010 at 01:08:07PM +0300, Michael S. Tsirkin wrote:
Userspace virtio server has the following hack
so guests rely on it, and we have to replicate it, too:
Use port number to detect incoming IPv4 DHCP response packets,
and fill in the checksum for these.
The issue we are
On Wed, Jun 23, 2010 at 02:26:18PM +0300, Avi Kivity wrote:
No need to reload the mmu in between two different vcpu-requests checks.
kvm_mmu_reload() may trigger KVM_REQ_TRIPLE_FAULT, but that will be caught
during atomic guest entry later.
Signed-off-by: Avi Kivity a...@redhat.com
---
On Wed, Jun 23, 2010 at 10:24:02PM +0100, Stefan Hajnoczi wrote:
The virtio block device holds a lock during I/O request processing.
Kicking the virtqueue while the lock is held results in long lock hold
times and increases contention for the lock.
This patch modifies virtqueue_kick() to
From: Sheng Yang sh...@linux.intel.com
Signed-off-by: Sheng Yang sh...@linux.intel.com
Signed-off-by: Avi Kivity a...@redhat.com
---
target-i386/kvm.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/target-i386/kvm.c b/target-i386/kvm.c
index 576d3b5..a33d2fa 100644
---
The following changes since commit 4972d592113c627d4b6ea1be5c94a85b56099afd:
Stefan Weil (1):
win32: Add missing function ffs
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git uq/master
Andre Przywara (1):
fix CPUID vendor override
Jan
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
Signed-off-by: Avi Kivity a...@redhat.com
---
target-i386/kvm.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/target-i386/kvm.c b/target-i386/kvm.c
index 436c0c4..576d3b5 100644
--- a/target-i386/kvm.c
+++
From: Sheng Yang sh...@linux.intel.com
Would use it later for XSAVE related CPUID.
Signed-off-by: Sheng Yang sh...@linux.intel.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
---
kvm.h |2 +-
target-i386/kvm.c | 19 +++
2 files changed, 12 insertions(+),
From: Jan Kiszka jan.kis...@siemens.com
Guest debugging under KVM is currently broken once io-threads are
enabled. Easily fixable by switching the fake on_vcpu to the real
run_on_cpu implementation.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
Signed-off-by: Avi Kivity a...@redhat.com
---
From: Andre Przywara andre.przyw...@amd.com
the meaning of vendor_override is actually the opposite of how it
is currently used :-(
Fix it to allow KVM to export the non-native CPUID vendor if
explicitly requested by the user.
The intended behavior is:
With TCG:
- always inject the configured
From: Sheng Yang sh...@linux.intel.com
Signed-off-by: Sheng Yang sh...@linux.intel.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
---
kvm-all.c | 21 +++
kvm.h |2 +
target-i386/cpu.h |7 ++-
target-i386/kvm.c | 139
On 06/24/2010 06:12 AM, Avi Kivity wrote:
On 06/24/2010 01:58 PM, Andre Przywara wrote:
So who would create the /dev/shm/nodeXX files?
Currently it is QEMU. It creates a somewhat unique filename, opens
and unlinks it. The difference would be to name the file after the
option and to not
On 06/24/2010 06:42 AM, Avi Kivity wrote:
On 06/24/2010 02:34 PM, Andre Przywara wrote:
Non-anonymous memory doesn't work well with ksm and transparent
hugepages. Is it possible to use anonymous memory rather than file
backed?
I'd prefer non-file backed, too. But that is how the current
Anthony Liguori wrote:
On 06/24/2010 06:42 AM, Avi Kivity wrote:
On 06/24/2010 02:34 PM, Andre Przywara wrote:
Non-anonymous memory doesn't work well with ksm and transparent
hugepages. Is it possible to use anonymous memory rather than file
backed?
I'd prefer non-file backed, too. But
On Sun, 2010-06-27 at 11:59 +0300, Michael S. Tsirkin wrote:
When ring parsing fails, we currently handle this
as ring empty condition. This means that we enable
kicks and recheck ring empty: if this not empty,
we re-start polling which of course will fail again.
Instead, let's return a
On Mon, Jun 28, 2010 at 10:11:43AM -0700, Sridhar Samudrala wrote:
On Sun, 2010-06-27 at 11:59 +0300, Michael S. Tsirkin wrote:
When ring parsing fails, we currently handle this
as ring empty condition. This means that we enable
kicks and recheck ring empty: if this not empty,
we re-start
On Monday, June 28, 2010 12:28:52 pm BuraphaLinux Server wrote:
Hello,
I have tried qemu_kvm 0.12.4 release and also git from about 1/2
an hour ago. In both cases, I crash in the post_kvm_run() function on
the line about:
pthread_mutex_lock(qemu_mutex);
The command I use to run
Please send in any agenda items you are interested in covering.
If we have a lack of agenda items I'll cancel the week's call.
After last week debacle, I will wait until 10 mins before call to cancel
it.
thanks, Juan.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body
On 06/28/2010 11:14 AM, Marcelo Tosatti wrote:
The following changes since commit 4972d592113c627d4b6ea1be5c94a85b56099afd:
Stefan Weil (1):
win32: Add missing function ffs
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git uq/master
On Thu, Jun 24, 2010 at 08:29:51PM -0300, Lucas Meneghel Rodrigues wrote:
In order to make it convenient to run unit tests on
KVM autotest, add rules to install the flat files to
$(PREFIX)/share/qemu/tests.
Also, add a unittests.cfg file, a simple .ini file
that contains unittest
On Thu, Jun 24, 2010 at 08:19:02PM +0300, Michael S. Tsirkin wrote:
With recent git versions (like one in rhel6 beta),
git prints out tag info in addition to
requested format, if passed a tag name.
This breaks make-release.
To get just the time as we want, we need to
pass something that is
On Mon, 2010-06-28 at 13:08 +0300, Michael S. Tsirkin wrote:
Userspace virtio server has the following hack
so guests rely on it, and we have to replicate it, too:
Use port number to detect incoming IPv4 DHCP response packets,
and fill in the checksum for these.
The issue we are solving
On 06/28/10 16:26, SuNeEl wrote:
I have been trying desperately to achieve virtual networking with kvm, but =
some how I failed each time.. rather lot of unclear tutorial using differen=
t methods achieving common goals made me confuse like bridging, vmnet, tun,=
etc etc routing ,iptable
Avi Kivity wrote:
On 06/28/2010 01:02 PM, Xiao Guangrong wrote:
Avi Kivity wrote:
Instead of adding a new bit, can you encode the protection in the direct
sp's access bits? So we'll have one sp for read-only or
writeable-but-not-dirty small pages, and another sp for
Avi Kivity wrote:
I think I see. So, after A, the pages are write protected, but are
still marked as unsync. In B, we're testing SP2-unsync, which we plan
to sync soon, but haven't yet. So the test for s-unsync is incorrect.
Right.
So the patch is right. Thanks for the
On Mon, Jun 28, 2010 at 05:54:18PM +0300, Michael Goldish wrote:
The telnet service isn't used by kvm-autotest (AFAIK) and may interfere with
rss.exe (port 23).
Michael,
I think it is better to leave the port 23 (and also 22) alone, people
may want to use both telnet (e.g. telnet is
Some guest device driver may leverage the Non-Snoop I/O, and explicitly
WBINVD or CLFLUSH to a RAM space. Since migration may occur before WBINVD or
CLFLUSH, we need to maintain data consistency either by:
1: flushing cache (wbinvd) when the guest is scheduled out if there is no
wbinvd exit, or
2:
Please send in any agenda items you are interested in covering.
If we have a lack of agenda items I'll cancel the week's call.
thanks,
-chris
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Hello,
I have been scouring mailing lists, the wiki, and talked with iggy on
freenode/#kvm who suggested that I ask on the list. KVM reports that I
do not have an IOMMU, however, dmesg reports both DMAR and IOMMU. In
addition, I know that this board supports VT-d.
Something of note, ldd
Hidetoshi Seto seto.hideto...@jp.fujitsu.com writes:
Hao, Xudong xudong@intel.com writes:
When assign one PCI device, qemu fail to parse the command line:
qemu-system_x86 -smp 2 -m 1024 -hda /path/to/img -pcidevice host=00:19.0
Error:
qemu-system-x86_64: Parameter 'id' expects an
On Sun Jun 27 around 19:33:52 EST 2010 Alexander Graf wrote:
Am 27.06.2010 um 10:14 schrieb Avi Kivity avi at redhat.com:
On 06/26/2010 02:25 AM, Alexander Graf wrote:
+
+PPC hypercalls
+==
+
+The only viable ways to reliably get from guest context to host
On 28.06.2010, at 09:18, Milton Miller wrote:
On Sun Jun 27 around 19:33:52 EST 2010 Alexander Graf wrote:
Am 27.06.2010 um 10:14 schrieb Avi Kivity avi at redhat.com:
On 06/26/2010 02:25 AM, Alexander Graf wrote:
+
+PPC hypercalls
+==
+
+The only viable ways to reliably
(2010/06/27 16:32), Avi Kivity wrote:
On 06/25/2010 10:25 PM, Alexander Graf wrote:
On 23.06.2010, at 08:01, Takuya Yoshikawa wrote:
kvm_get_dirty_log() is a helper function for
kvm_vm_ioctl_get_dirty_log() which
is currently used by ia64 and ppc and the following is what it is doing:
-
On 06/28/2010 10:49 AM, Alexander Graf wrote:
I don't believe we support the kernel actually doing a syscall to itself
anymore, at least on powerpc. The callers call the underlying system
call function, or kernel_thread.
That said, I would suggest we allocate a syscall number for this, as it
On 06/28/2010 09:33 AM, Alexander Graf wrote:
Could you do something similar in module_finalize() to patch loaded modules'
.text sections?
I could, but do we need it? I objdump -d | grep'ed all my modules and didn't
find any need to do so.
You mean even kvm.ko doesn't use
On 28.06.2010, at 10:13, Avi Kivity wrote:
On 06/28/2010 10:49 AM, Alexander Graf wrote:
I don't believe we support the kernel actually doing a syscall to itself
anymore, at least on powerpc. The callers call the underlying system
call function, or kernel_thread.
That said, I would
On 06/28/2010 11:21 AM, Alexander Graf wrote:
The other alternative I'd see is to reuse an instruction that is not sc. We could for
example pull the mfpvr trick again, but pass a different magic value in the register this
time that tells the hypervisor this is a hypercall.
Or we could
On 06/28/2010 11:23 AM, Alexander Graf wrote:
You mean even kvm.ko doesn't use privileged instructions?
It does, but I don't think it's worth speeding those up. There are only a
couple. Most of the privileged instructions in PPC KVM are statically compiled
into the kernel because we
On 28.06.2010, at 10:28, Avi Kivity wrote:
On 06/26/2010 02:16 AM, Alexander Graf wrote:
Currently the shadow paging code keeps an array of entries it knows about.
Whenever the guest invalidates an entry, we loop through that entry,
trying to invalidate matching parts.
While this is a
On 06/28/2010 11:55 AM, Alexander Graf wrote:
+
+static inline u64 kvmppc_mmu_hash_pte(u64 eaddr) {
+ return hash_64(eaddr PTE_SIZE, HPTEG_HASH_BITS_PTE);
+}
+
+static inline u64 kvmppc_mmu_hash_vpte(u64 vpage) {
+ return hash_64(vpage 0xfULL, HPTEG_HASH_BITS_VPTE);
+}
Avi Kivity wrote:
On 06/28/2010 12:27 PM, Alexander Graf wrote:
Am I looking at old code?
Apparently. Check book3s_mmu_*.c
I don't have that pattern.
It's in this patch.
+static void invalidate_pte(struct kvm_vcpu *vcpu, struct hpte_cache *pte)
+{
+ dprintk_mmu(KVM: Flushing SPT:
On 06/28/2010 12:55 PM, Alexander Graf wrote:
Avi Kivity wrote:
On 06/28/2010 12:27 PM, Alexander Graf wrote:
Am I looking at old code?
Apparently. Check book3s_mmu_*.c
I don't have that pattern.
It's in this patch.
Yes. Silly me.
+static void
Avi Kivity wrote:
On 06/28/2010 12:55 PM, Alexander Graf wrote:
Avi Kivity wrote:
On 06/28/2010 12:27 PM, Alexander Graf wrote:
Am I looking at old code?
Apparently. Check book3s_mmu_*.c
I don't have that pattern.
It's in this patch.
Yes. Silly
92 matches
Mail list logo
