https://bugzilla.kernel.org/show_bug.cgi?id=26872
alien.vi...@gmail.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
On 01/20/11 20:39, Anthony Liguori wrote:
On 01/20/2011 02:44 AM, Gerd Hoffmann wrote:
Hi,
For (2), you cannot use bus=X,addr=Y because it makes assumptions about
the PCI topology which may change in newer -M pc's.
Why should the PCI topology for 'pc' ever change?
We'll probably get q35
Hi,
By the way, we don't have a QEMUState but instead use globals.
/me wants to underline this.
IMO it is absolutely pointless to worry about ways to pass around
kvm_state. There never ever will be a serious need for that.
We can stick with the current model of keeping global state in
On Thu, Jan 20, 2011 at 06:23:36PM -0600, Anthony Liguori wrote:
On 01/20/2011 10:07 AM, Michael S. Tsirkin wrote:
On Thu, Jan 20, 2011 at 09:43:57AM -0600, Anthony Liguori wrote:
On 01/20/2011 09:35 AM, Michael S. Tsirkin wrote:
When MSI is off, each interrupt needs to be bounced through the
On Thu, Jan 20, 2011 at 06:35:46PM -0700, Alex Williamson wrote:
On Thu, 2011-01-20 at 18:23 -0600, Anthony Liguori wrote:
On 01/20/2011 10:07 AM, Michael S. Tsirkin wrote:
On Thu, Jan 20, 2011 at 09:43:57AM -0600, Anthony Liguori wrote:
On 01/20/2011 09:35 AM, Michael S. Tsirkin
Gerd Hoffmann kra...@redhat.com writes:
On 01/20/11 20:39, Anthony Liguori wrote:
On 01/20/2011 02:44 AM, Gerd Hoffmann wrote:
Hi,
For (2), you cannot use bus=X,addr=Y because it makes assumptions about
the PCI topology which may change in newer -M pc's.
Why should the PCI topology for
Gerd Hoffmann kra...@redhat.com writes:
Hi,
By the way, we don't have a QEMUState but instead use globals.
/me wants to underline this.
IMO it is absolutely pointless to worry about ways to pass around
kvm_state. There never ever will be a serious need for that.
We can stick with the
On Thu, Jan 20, 2011 at 05:38:33PM +0900, Simon Horman wrote:
[ Trimmed Eric from CC list as vger was complaining that it is too long ]
On Tue, Jan 18, 2011 at 11:41:22AM -0800, Rick Jones wrote:
So it won't be all that simple to implement well, and before we try,
I'd like to know whether
On Fri, 2011-01-21 at 11:55 +0200, Michael S. Tsirkin wrote:
On Thu, Jan 20, 2011 at 06:35:46PM -0700, Alex Williamson wrote:
On Thu, 2011-01-20 at 18:23 -0600, Anthony Liguori wrote:
On 01/20/2011 10:07 AM, Michael S. Tsirkin wrote:
On Thu, Jan 20, 2011 at 09:43:57AM -0600, Anthony
On Fri, Jan 21, 2011 at 06:19:13AM -0700, Alex Williamson wrote:
On Fri, 2011-01-21 at 11:55 +0200, Michael S. Tsirkin wrote:
On Thu, Jan 20, 2011 at 06:35:46PM -0700, Alex Williamson wrote:
On Thu, 2011-01-20 at 18:23 -0600, Anthony Liguori wrote:
On 01/20/2011 10:07 AM, Michael S.
On Thu, Jan 20, 2011 at 12:48:00PM +0100, Ruben Kerkhof wrote:
I'm suddenly getting lots of the following errors on a server running
2.36.7, but I have no idea what it means:
2011-01-20T12:41:18.358603+01:00 phy005 kernel: EPT: Misconfiguration.
2011-01-20T12:41:18.358621+01:00 phy005
On Thu, Jan 20, 2011 at 09:56:27AM -0800, Jeremy Fitzhardinge wrote:
The key here is not to
sleep when waiting for locks (as implemented by current patch-series, which
can
put other VMs at an advantage by giving them more time than they are
entitled
to)
Why? If a VCPU can't
On 01/21/2011 03:48 AM, Michael S. Tsirkin wrote:
On Thu, Jan 20, 2011 at 06:23:36PM -0600, Anthony Liguori wrote:
On 01/20/2011 10:07 AM, Michael S. Tsirkin wrote:
On Thu, Jan 20, 2011 at 09:43:57AM -0600, Anthony Liguori wrote:
On 01/20/2011 09:35 AM, Michael S. Tsirkin
On 01/21/2011 03:55 AM, Michael S. Tsirkin wrote:
On Thu, Jan 20, 2011 at 06:35:46PM -0700, Alex Williamson wrote:
On Thu, 2011-01-20 at 18:23 -0600, Anthony Liguori wrote:
On 01/20/2011 10:07 AM, Michael S. Tsirkin wrote:
On Thu, Jan 20, 2011 at 09:43:57AM -0600, Anthony
On 01/21/2011 09:02 AM, Srivatsa Vaddagiri wrote:
On Thu, Jan 20, 2011 at 09:56:27AM -0800, Jeremy Fitzhardinge wrote:
The key here is not to
sleep when waiting for locks (as implemented by current patch-series, which can
put other VMs at an advantage by giving them more time than they are
On Fri, 21 Jan 2011, Balbir Singh wrote:
* Christoph Lameter c...@linux.com [2011-01-20 09:00:09]:
On Thu, 20 Jan 2011, Balbir Singh wrote:
+ unmapped_page_control
+ [KNL] Available if CONFIG_UNMAPPED_PAGECACHE_CONTROL
+ is enabled. It controls the
On Fri, Jan 21, 2011 at 8:46 AM, Gerd Hoffmann kra...@redhat.com wrote:
Hi,
By the way, we don't have a QEMUState but instead use globals.
/me wants to underline this.
IMO it is absolutely pointless to worry about ways to pass around kvm_state.
There never ever will be a serious need for
On 2011-01-21 17:37, Blue Swirl wrote:
On Fri, Jan 21, 2011 at 8:46 AM, Gerd Hoffmann kra...@redhat.com wrote:
Hi,
By the way, we don't have a QEMUState but instead use globals.
/me wants to underline this.
IMO it is absolutely pointless to worry about ways to pass around kvm_state.
I have constructed a test where I run an un-paced UDP_STREAM test in
one guest and a paced omni rr test in another guest at the same time.
Hmm, what is this supposed to measure? Basically each time you run an
un-paced UDP_STREAM you get some random load on the network.
Well, if the netperf
On Fri, Jan 21, 2011 at 5:21 PM, Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-01-21 17:37, Blue Swirl wrote:
On Fri, Jan 21, 2011 at 8:46 AM, Gerd Hoffmann kra...@redhat.com wrote:
Hi,
By the way, we don't have a QEMUState but instead use globals.
/me wants to underline this.
IMO it
On 2011-01-21 19:04, Blue Swirl wrote:
On Fri, Jan 21, 2011 at 5:21 PM, Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-01-21 17:37, Blue Swirl wrote:
On Fri, Jan 21, 2011 at 8:46 AM, Gerd Hoffmann kra...@redhat.com wrote:
Hi,
By the way, we don't have a QEMUState but instead use globals.
On Fri, Jan 21, 2011 at 6:17 PM, Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-01-21 19:04, Blue Swirl wrote:
On Fri, Jan 21, 2011 at 5:21 PM, Jan Kiszka jan.kis...@siemens.com wrote:
On 2011-01-21 17:37, Blue Swirl wrote:
On Fri, Jan 21, 2011 at 8:46 AM, Gerd Hoffmann kra...@redhat.com
From: Jan Kiszka jan.kis...@siemens.com
We must flush pending mmio writes if we leave kvm_cpu_exec for an IO
window. Otherwise we risk to loose those requests when migrating to a
different host during that window.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
kvm-all.c |4 ++--
1
From: Jan Kiszka jan.kis...@siemens.com
The imbalance in the hold time of qemu_global_mutex only exists in TCG
mode. In contrast to TCG VCPUs, KVM drops the global lock during guest
execution. We already avoid touching the fairness lock from the
IO-thread in KVM mode, so also stop using it from
From: Jan Kiszka jan.kis...@siemens.com
Instead of splattering the code with #ifdefs and runtime checks for
capabilities we cannot work without anyway, provide central test
infrastructure for verifying their availability both at build and
runtime.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
From: Jan Kiszka jan.kis...@siemens.com
If the kernel does not support KVM_CAP_ASYNC_PF, it also does not know
about the related MSR. So skip it during state synchronization in that
case. Fixes annoying kernel warnings.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
target-i386/kvm.c |
From: Jan Kiszka jan.kis...@siemens.com
The ordering doesn't matter in this case, but better keep it consistent.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
target-i386/kvm.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/target-i386/kvm.c
From: Jan Kiszka jan.kis...@siemens.com
Make sure to write the cleared MSR_KVM_SYSTEM_TIME, MSR_KVM_WALL_CLOCK,
and MSR_KVM_ASYNC_PF_EN to the kernel state so that a freshly booted
guest cannot be disturbed by old values.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
CC: Glauber Costa
From: Jan Kiszka jan.kis...@siemens.com
Introduce the cpu_dump_state flag CPU_DUMP_CODE and implement it for
x86. This writes out the code bytes around the current instruction
pointer. Make use of this feature in KVM to help debugging fatal vm
exits.
Signed-off-by: Jan Kiszka
From: Jan Kiszka jan.kis...@siemens.com
Ensure that we stop the guest whenever we face a fatal or unknown exit
reason. If we stop, we also have to enforce a cpu loop exit.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
kvm-all.c | 15 +++
target-i386/kvm.c |4
From: Jan Kiszka jan.kis...@siemens.com
kvm_arch_reset_vcpu initializes mp_state, and that function is invoked
right after kvm_arch_init_vcpu.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
target-i386/kvm.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git
From: Jan Kiszka jan.kis...@siemens.com
No longer used.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
kvm-all.c |4 ++--
kvm-stub.c |2 +-
kvm.h |4 ++--
target-i386/kvm.c |2 +-
target-ppc/kvm.c |2 +-
target-s390x/kvm.c |2 +-
From: Jan Kiszka jan.kis...@siemens.com
For unknown reasons, xcr0 reset ended up in kvm_arch_update_guest_debug
on upstream merge. Fix this and also remove the misleading comment (1 is
THE reset value).
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
target-i386/kvm.c |3 +--
1 files
From: Jan Kiszka jan.kis...@siemens.com
In order to support loading BIOSes 256K, reorder the code, adjusting
the base if the kernel supports moving the identity map.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
target-i386/kvm.c | 63
From: Jan Kiszka jan.kis...@siemens.com
If we lack kvm_para.h, MSR_KVM_ASYNC_PF_EN is not defined. The change in
kvm_arch_init_vcpu is just for consistency reasons.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
target-i386/kvm.c |8
1 files changed, 4 insertions(+), 4
From: Jan Kiszka jan.kis...@siemens.com
Simplify kvm_has_msr_star/hsave_pa to booleans and push their one-time
initialization into kvm_arch_init. Also handle potential errors of that
setup procedure.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
target-i386/kvm.c | 47
From: Jan Kiszka jan.kis...@siemens.com
This code path will not yet be taken as we still lack in-kernel irqchip
support. But qemu-kvm can already make use of it and drop its own
mp_state access services.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
target-i386/kvm.c |3 +++
1 files
In order to make progress with flushing my kvm-upstream queue without
overloading the channels (38 further patches are pending), here comes
part I against updated uq/master.
Changes in this part compared to last postings:
- Dropped kvm: Drop return value of kvm_cpu_exec, we will actually
From: Jan Kiszka jan.kis...@siemens.com
This exit only triggers activity in the common exit path, but we should
accept it in order to be able to detect unknown exit types.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
target-i386/kvm.c |3 +++
1 files changed, 3 insertions(+), 0
From: Jan Kiszka jan.kis...@siemens.com
Report KVM_EXIT_UNKNOWN, KVM_EXIT_FAIL_ENTRY, and KVM_EXIT_EXCEPTION
with more details to stderr. The latter two are so far x86-only, so move
them into the arch-specific handler. Integrate the Intel real mode
warning on KVM_EXIT_FAIL_ENTRY that qemu-kvm
On Fri, Jan 21, 2011 at 11:59:30AM +0200, Michael S. Tsirkin wrote:
On Thu, Jan 20, 2011 at 05:38:33PM +0900, Simon Horman wrote:
[ Trimmed Eric from CC list as vger was complaining that it is too long ]
On Tue, Jan 18, 2011 at 11:41:22AM -0800, Rick Jones wrote:
So it won't be all that
When doing device assignment, we use cpu_register_physical_memory() to
directly map the qemu mmap of the device resource into the address
space of the guest. The unadvertised feature of the register physical
memory code path on kvm, at least for this type of mapping, is that it
needs to allocate
KVM memory slots are used any place we want a guest to have direct
access to a chunk of memory. Unfortunately, there's only a small,
fixed number of them, and accidentally going over the limit causes
an abort. Add a trivial interface so that callers can at least
guess if they have a chance to
Each MMIO PCI BAR of an assigned device is directly mapped via a KVM
memory slot to avoid bouncing reads and writes through qemu. KVM only
provides a (small) fixed number of these slots and attempting to
exceed the unadvertised limit results in an abort. We can't reserve
slots, but let's at
In order to concentrate setup classes for the KVM autotest
tests, create test_setup.py. This library will contain
code used to perform actions before to the actual test
execution, putting some hooks on the test postprocessing
code. The first class in there is the UnattendedInstallConfig
class,
Also, get rid of references to the old unattended install
script.
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/tests/kvm/kvm_preprocessing.py |6 +-
client/tests/kvm/tests_base.cfg.sample |2 --
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git
So we concentrate the setup classes together.
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/tests/kvm/kvm_preprocessing.py |2 +-
client/tests/kvm/kvm_utils.py | 101 -
client/tests/kvm/test_setup.py| 101
Now that its functionality was implemented as part of
the framework.
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/tests/kvm/scripts/unattended.py | 543
client/tests/kvm/tests_base.cfg.sample |2 -
2 files changed, 0 insertions(+), 545
So we can get rid of the pre/post scripts. Wit the rearrangement
we were able to achieve several advantages:
- More rigorous and paranoid cleanup phase
- Better identification of the lvm devices, less likely to
originate conflicts with devices in the host
- Use the shared autotest API avoiding
As their functionality has been reimplemented as
framework functionality
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/tests/kvm/scripts/enospc-post.py | 77 ---
client/tests/kvm/scripts/enospc-pre.py | 73 -
2
For the sake of clarity, we stablish a convention, scripts copied
to guests and executed there by tests will be called
[test_name]_guest.py. This patchset takes care of renaming
the scripts.
Lucas Meneghel Rodrigues (4):
KVM test: Renaming script bonding_setup.py to nic_bonding_guest.py
KVM
We'll stablish a convention (of course, no extremely strict)
about scripts ran in guest: We can call them [test_name]_guest.py.
Let's start by converting bonding_setup to this convention.
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/tests/kvm/scripts/bonding_setup.py |
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/tests/kvm/scripts/join_mcast.py | 37 ---
client/tests/kvm/scripts/multicast_guest.py | 37 +++
client/tests/kvm/tests/multicast.py |4 +-
3 files changed, 39
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/tests/kvm/scripts/allocator.py| 237 --
client/tests/kvm/scripts/ksm_overcommit_guest.py | 237 ++
client/tests/kvm/tests/ksm_overcommit.py | 40 ++--
3 files
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/tests/kvm/scripts/virtio_console_guest.py | 715 ++
client/tests/kvm/scripts/virtio_guest.py | 715 --
client/tests/kvm/tests/virtio_console.py | 20 +-
3 files changed,
Those were introduced on a previous netperf fixes.
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/tests/kvm/tests_base.cfg.sample | 14 +++---
1 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/client/tests/kvm/tests_base.cfg.sample
On unattended_install with background ping pong migration.
It was my mistake when modifying the original Jason's patchset.
Signed-off-by: Lucas Meneghel Rodrigues l...@redhat.com
---
client/tests/kvm/tests_base.cfg.sample |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
On Fri, Jan 21, 2011 at 09:48:29AM -0500, Rik van Riel wrote:
Why? If a VCPU can't make progress because its waiting for some
resource, then why not schedule something else instead?
In the process, something else can get more share of cpu resource than its
entitled to and that's where I was
58 matches
Mail list logo
