Hi,All
This is today's KVM test result against kvm.git
f1ca151a368192b182a9f9e696e211e18927f040 and kvm-userspace.git
0088a24f6b38f534ae620e4c484d10aba4f5da96.
No new issue has been found.
Issue List:
1. smp windows installer crashes while rebooting
https://sourceforge.net/tracker/index.php?func=d
On Thu, Jan 31, 2008 at 07:58:40PM -0800, Christoph Lameter wrote:
> Ok. Andrea wanted the same because then he can void the begin callouts.
Exactly. I hope the page-pin will avoid me having to serialize the KVM
page fault against the start/end critical section.
BTW, I wonder if the start/end cri
On Thu, Jan 31, 2008 at 09:04:39PM -0800, Christoph Lameter wrote:
> - Has page tables to track pages whose refcount was elevated(?) but
> no reverse maps.
Just a correction, rmaps exists or swap couldn't be sane, it's just
that it's not built on the page_t because the guest memory is really
vir
On Fri, Feb 01, 2008 at 11:23:57AM -0800, Christoph Lameter wrote:
> Yes so your invalidate_range is still some sort of dysfunctional
> optimization? Gazillions of invalidate_page's will have to be executed
> when tearing down large memory areas.
I don't know if gru can flush the external TLB re
On Fri, Feb 01, 2008 at 05:35:28PM -0600, Robin Holt wrote:
> No, we need a callout when we are becoming more restrictive, but not
> when becoming more permissive. I would have to guess that is the case
> for any of these callouts. It is for both GRU and XPMEM. I would
> expect the same is true
On Sun, Feb 03, 2008 at 03:17:04AM +0100, Andrea Arcangeli wrote:
> On Fri, Feb 01, 2008 at 11:23:57AM -0800, Christoph Lameter wrote:
> > Yes so your invalidate_range is still some sort of dysfunctional
> > optimization? Gazillions of invalidate_page's will have to be executed
> > when tearing d
On Sat, Feb 02, 2008 at 09:14:57PM -0600, Jack Steiner wrote:
> Also, most (but not all) applications that use the GRU do not usually do
> anything that requires frequent flushing (fortunately). The GRU is intended
> for HPC-like applications. These don't usually do frequent map/unmap
> operations
I'm experimenting with kvm on a Fedora 8 system. I've installed the
necessary packages, have a suitable CPU etc. I'll eventually aim for
a Windows guest, but am trying out a virtual Fedora 8 guest. When I
try to install a Fedora guest, it threatens to wipe and re-partition
the whole drive. It does
From: Xiantao Zhang <[EMAIL PROTECTED]>
Date: Sun, 3 Feb 2008 14:46:02 +0800
Subject: [PATCH] kvm: Let ioctl_get_regs suppot input pararmeters.
Since kvm_regs is allocated from kernel stack, and
its size is limited. In order to save large register
files of some archs, this API should accept input
