On 07/01/2010 07:05 PM, Lucas Meneghel Rodrigues wrote:
On Thu, 2010-07-01 at 17:42 +0300, Avi Kivity wrote:
On 06/30/2010 06:39 PM, Lucas Meneghel Rodrigues wrote:
By default, HPET is enabled on qemu and no time drift
mitigation is being made for it. So, add -no-hpet
if qemu supports it,
On 02.07.2010, at 21:10, Scott Wood wrote:
On Fri, 2 Jul 2010 20:47:44 +0200
Alexander Graf ag...@suse.de wrote:
On 02.07.2010, at 19:59, Hollis Blanchard wrote:
[Resending...]
Please reconcile this with
http://www.linux-kvm.org/page/PowerPC_Hypercall_ABI, which has been
discussed
On 04.07.2010, at 00:41, Benjamin Herrenschmidt wrote:
On Fri, 2010-07-02 at 18:27 +0200, Segher Boessenkool wrote:
+To find out if we're running on KVM or not, we overlay the PVR
register. Usually
+the PVR register contains an id that identifies your CPU type. If,
however, you
+pass
On Fri, Jul 02, 2010 at 11:06:37PM +0200, Oleg Nesterov wrote:
On 07/02, Peter Zijlstra wrote:
On Fri, 2010-07-02 at 11:01 -0700, Sridhar Samudrala wrote:
Does it (Tejun's kthread_clone() patch) also inherit the
cgroup of the caller?
Of course, its a simple do_fork() which
On 07/04/2010 12:04 PM, Alexander Graf wrote:
My biggest concern about putting things in the device-tree is that I was trying
to keep things as separate as possible. Why does the firmware have to know that
it's running in KVM?
It doesn't need to know about kvm, it needs to know that a
On 04.07.2010, at 11:10, Avi Kivity wrote:
On 07/04/2010 12:04 PM, Alexander Graf wrote:
My biggest concern about putting things in the device-tree is that I was
trying to keep things as separate as possible. Why does the firmware have to
know that it's running in KVM?
It doesn't need
On 04.07.2010, at 11:17, Alexander Graf wrote:
On 04.07.2010, at 11:10, Avi Kivity wrote:
On 07/04/2010 12:04 PM, Alexander Graf wrote:
My biggest concern about putting things in the device-tree is that I was
trying to keep things as separate as possible. Why does the firmware have
On 07/04/2010 12:17 PM, Alexander Graf wrote:
On 04.07.2010, at 11:10, Avi Kivity wrote:
On 07/04/2010 12:04 PM, Alexander Graf wrote:
My biggest concern about putting things in the device-tree is that I was trying
to keep things as separate as possible. Why does the firmware have
On 07/04/2010 12:30 PM, Alexander Graf wrote:
Considering how the parts of the draft that I read about sound like, that's not
the inventor's idea. PPC people love to see the BIOS be part of the
virtualization solution. I don't. That's the biggest difference here and reason
for us going
On 07/02/2010 06:37 PM, Alexander Graf wrote:
Alexander Graf wrote:
We need to override EA as well as PA lookups for the magic page. When the guest
tells us to project it, the magic page overrides any guest mappings.
In order to reflect that, we need to hook into all the MMU layers of KVM
Enable RSS to send/receive files and directory trees (recursively).
See protocol details in rss.cpp.
Changes from v3:
- Protocol change: instead of sending a file in one big packet, send it in
multiple chunks. The last chunk of a file is identified by being smaller.
This solves a problem
See details in docstrings in rss_file_transfer.py.
See protocol details in deps/rss.cpp.
Changes from v3:
- Protocol change: instead of sending a file as one big packet, send it in
multiple chunks. See details in deps/rss.cpp.
Changes from v2:
- Raise FileTransferNotFoundError if no
find_command() is similar to os_dep.command(), but instead of searching $PATH,
it searches a few hard coded locations. The problem with searching
$PATH is that different users may have different $PATHs. For example, autotest
can be executed by a non-root user, or using sudo, and in some OSes
Instead of hardcoding binary paths, use kvm_utils.find_command().
This should make the KVM test a little more distro independent.
Signed-off-by: Michael Goldish mgold...@redhat.com
---
client/tests/kvm/kvm_preprocessing.py |4 ++--
client/tests/kvm/kvm_utils.py |7 ---
2
Tail threads refer to kvm_tail objects, preventing them from being garbage-
collected.
1) Before a tail thread exits, remove the reference to the thread from the
kvm_tail object.
2) Add a function kill_tail_threads() which asks all tail threads to terminate
and waits for them to do so.
3)
On 07/03/2010 04:03 PM, Xiao Guangrong wrote:
Avi Kivity wrote:
Well, in the description, it looked like everything was using small
pages (in kvm, level=1 means PTE level, we need to change this one
day). Please describe again and say exactly when the guest or host
uses large pages.
On 07/03/2010 03:57 PM, Xiao Guangrong wrote:
Avi Kivity wrote:
And this check is not sufficient, since it's only checked if the
mapping is zapped or not exist, for other words only when broken this
judgment:
is_shadow_present_pte(*sptep) !is_large_pte(*sptep)
but if the middle
Hi all!
Is it possible to resize the partition of a KVM virtual machine without
it is down?
With Xen PV virtual machines, I get this by umounting the filesystem on
the VM, detaching the device and then resizing the logical volume and
file system in the VMHost. Finally, I attach the device and
On Saturday 03 July 2010 16:02:42 Xiao Guangrong wrote:
Commit 341d9b535b6c simplify reload logic while entry guest mode, it
can avoid unnecessary sync-root if KVM_REQ_MMU_RELOAD and
KVM_REQ_MMU_SYNC both set.
Which commit you are talking about? Can't find 341d9b535b6c...
--
regards
Yang,
On Sat, Jul 03, 2010 at 04:02:42PM +0800, Xiao Guangrong wrote:
Commit 341d9b535b6c simplify reload logic while entry guest mode, it
can avoid unnecessary sync-root if KVM_REQ_MMU_RELOAD and
KVM_REQ_MMU_SYNC both set.
But, it cause a issue that when we handle 'KVM_REQ_TLB_FLUSH', the
root
Avi Kivity wrote:
Umm, if we move the check before the judgment, it'll check every level,
actually, only the opened mapping and the laster level need checked, so
for the performance reason, maybe it's better to keep two check-point.
What exactly are the conditions when you want to
Sheng Yang wrote:
On Saturday 03 July 2010 16:02:42 Xiao Guangrong wrote:
Commit 341d9b535b6c simplify reload logic while entry guest mode, it
can avoid unnecessary sync-root if KVM_REQ_MMU_RELOAD and
KVM_REQ_MMU_SYNC both set.
Which commit you are talking about? Can't find
Avi Kivity wrote:
On 07/02/2010 11:00 AM, Xiao Guangrong wrote:
The IOAPIC spec says:
When accessing these registers, accesses must be done one dword at a
time.
For example, software should never access byte 2 from the Data
register before
accessing bytes 0 and 1. The hardware will not
On 02.07.2010, at 21:10, Scott Wood wrote:
On Fri, 2 Jul 2010 20:47:44 +0200
Alexander Graf ag...@suse.de wrote:
On 02.07.2010, at 19:59, Hollis Blanchard wrote:
[Resending...]
Please reconcile this with
http://www.linux-kvm.org/page/PowerPC_Hypercall_ABI, which has been
discussed
On 04.07.2010, at 00:41, Benjamin Herrenschmidt wrote:
On Fri, 2010-07-02 at 18:27 +0200, Segher Boessenkool wrote:
+To find out if we're running on KVM or not, we overlay the PVR
register. Usually
+the PVR register contains an id that identifies your CPU type. If,
however, you
+pass
On 04.07.2010, at 11:17, Alexander Graf wrote:
On 04.07.2010, at 11:10, Avi Kivity wrote:
On 07/04/2010 12:04 PM, Alexander Graf wrote:
My biggest concern about putting things in the device-tree is that I was
trying to keep things as separate as possible. Why does the firmware have
On 07/04/2010 12:17 PM, Alexander Graf wrote:
On 04.07.2010, at 11:10, Avi Kivity wrote:
On 07/04/2010 12:04 PM, Alexander Graf wrote:
My biggest concern about putting things in the device-tree is that I was trying
to keep things as separate as possible. Why does the firmware have
On 07/04/2010 12:30 PM, Alexander Graf wrote:
Considering how the parts of the draft that I read about sound like, that's not
the inventor's idea. PPC people love to see the BIOS be part of the
virtualization solution. I don't. That's the biggest difference here and reason
for us going
On 07/02/2010 06:37 PM, Alexander Graf wrote:
Alexander Graf wrote:
We need to override EA as well as PA lookups for the magic page. When the guest
tells us to project it, the magic page overrides any guest mappings.
In order to reflect that, we need to hook into all the MMU layers of KVM
29 matches
Mail list logo
