On 06/26/2012 01:49 AM, Sridhar Samudrala wrote:
On 6/25/2012 2:16 AM, Jason Wang wrote:
Hello All:
This series is an update version of multiqueue virtio-net driver
based on
Krishna Kumar's work to let virtio-net use multiple rx/tx queues to
do the
packets reception and transmission. Please
On 06/26/2012 02:01 AM, Shirley Ma wrote:
Hello Jason,
Good work. Do you have local guest to guest results?
Thanks
Shirley
Hi Shirley:
I would run tests to measure the performance and post here.
Thanks
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message
On Mon, Jun 25, 2012 at 06:50:06PM +0300, Avi Kivity wrote:
Later we can extend x86_decode_insn() and the other
functions to follow the same rule.
What rule? We cannot not initialize a context. You can reduce things
that should be initialized to minimum (getting GP
On 06/26/2012 11:30 AM, Gleb Natapov wrote:
Where will you put those for instance: interruptibility, have_exception,
perm_ok, only_vendor_specific_insn and how can they not be initialized
before each instruction emulation?
x86_emulate_ops::get_interruptibility()
Folks,
here is a patch that fixes vhost to use USER_DS before
doing a use_mm/usercopy operation. This was found during
vhost prototyping on s390 were we have a separate user/kernel
address space.
Jens Freimann (1):
use USER_DS in vhost_worker thread
drivers/vhost/vhost.c |3 +++
1 files
On Tue, Jun 26, 2012 at 12:59:58PM +0200, Christian Borntraeger wrote:
From: Jens Freimann jf...@linux.vnet.ibm.com
On some architectures address spaces are set up in a way that this is
not necessary to work properly but on some others (like s390) it is.
Make sure we operate on the user
Greetings everybody,
We are running qemu-kvm-0.14.0 on stock ubuntu-natty 2.6.38-8, and
booting stock ubuntu-precise image (3.2.0-25-generic), as a guest.
Occasionally, grub gets stuck before it reaches the OS selection menu.
After adding prints to grub, we discovered that it gets stuck in
From: Heiko Carstens heiko.carst...@de.ibm.com
Just use the defines instead of using plain numbers and adding
a comment behind each line.
Signed-off-by: Heiko Carstens heiko.carst...@de.ibm.com
Signed-off-by: Cornelia Huck cornelia.h...@de.ibm.com
---
arch/s390/kvm/sigp.c | 58
From: Heiko Carstens heiko.carst...@de.ibm.com
If an invalid parameter is passed or the addressed cpu is in an
incorrect state sigp set prefix will store a status.
This status must only have bits set as defined by the architecture.
The current kvm implementation missed to clear bits and also did
Avi, Marcelo,
here are some more s390 patches for the next release.
Patches 1 and 2 are included for dependency reasons; they will also
be sent through Martin's s390 tree.
The other patches fix several problems in our sigp handling code
and make it nicer to read.
Cornelia Huck (1):
KVM:
From: Heiko Carstens heiko.carst...@de.ibm.com
The smp and the kvm code have different defines for the sigp order codes.
Let's just have a single place where these are defined.
Also move the sigp condition code and sigp cpu status bits to the new
sigp.h header file.
Signed-off-by: Heiko Carstens
From: Heiko Carstens heiko.carst...@de.ibm.com
Only if the sensed cpu is not running a status is stored, which
is reflected by condition code 1. If the cpu is running, condition
code 0 should be returned.
Just the opposite of what the code is doing.
Acked-by: Cornelia Huck
From: Heiko Carstens heiko.carst...@de.ibm.com
condition code status stored for sigp sense running always implies
that only the not running status bit is set. Therefore no need to
check if it is set.
Signed-off-by: Heiko Carstens heiko.carst...@de.ibm.com
Signed-off-by: Martin Schwidefsky
If sigp sense doesn't have any status bits to report, it should set
cc 0 and leave the register as-is.
Since we know about the external call pending bit, we should report
it if it is set as well.
Acked-by: Heiko Carstens heiko.carst...@de.ibm.com
Reviewed-by: Christian Borntraeger
On 26.06.2012, at 16:06, Cornelia Huck wrote:
From: Heiko Carstens heiko.carst...@de.ibm.com
Only if the sensed cpu is not running a status is stored, which
is reflected by condition code 1. If the cpu is running, condition
code 0 should be returned.
Just the opposite of what the code is
On 26.06.2012, at 16:06, Cornelia Huck wrote:
From: Heiko Carstens heiko.carst...@de.ibm.com
If an invalid parameter is passed or the addressed cpu is in an
incorrect state sigp set prefix will store a status.
This status must only have bits set as defined by the architecture.
The current
On 13.03.2012 16:06, Alexander Graf wrote:
On 13.03.2012, at 16:05, Corentin Chary wrote:
On Tue, Mar 13, 2012 at 12:29 PM, Peter Lievenp...@dlh.net wrote:
On 11.02.2012 09:55, Corentin Chary wrote:
On Thu, Feb 9, 2012 at 7:08 PM, Peter Lievenp...@dlh.net wrote:
Hi,
is anyone aware if
https://bugzilla.kernel.org/show_bug.cgi?id=42782
--- Comment #11 from Reartes Guillermo rtgui...@gmail.com 2012-06-26
15:11:16 ---
I booted with iommu=pt kernel parameter and i stopped getting these messages.
I am experimenting with pcie kvm pass-through, so i ended using that parameter.
On Tue, 26 Jun 2012 16:52:56 +0200
Alexander Graf ag...@suse.de wrote:
On 26.06.2012, at 16:06, Cornelia Huck wrote:
From: Heiko Carstens heiko.carst...@de.ibm.com
Only if the sensed cpu is not running a status is stored, which
is reflected by condition code 1. If the cpu is
On 26.06.2012, at 17:33, Cornelia Huck wrote:
On Tue, 26 Jun 2012 16:52:56 +0200
Alexander Graf ag...@suse.de wrote:
On 26.06.2012, at 16:06, Cornelia Huck wrote:
From: Heiko Carstens heiko.carst...@de.ibm.com
Only if the sensed cpu is not running a status is stored, which
is
On Tue, 26 Jun 2012 16:56:08 +0200
Alexander Graf ag...@suse.de wrote:
On 26.06.2012, at 16:06, Cornelia Huck wrote:
From: Heiko Carstens heiko.carst...@de.ibm.com
If an invalid parameter is passed or the addressed cpu is in an
incorrect state sigp set prefix will store a status.
Am 26.06.2012 um 17:39 schrieb Cornelia Huck cornelia.h...@de.ibm.com:
On Tue, 26 Jun 2012 16:56:08 +0200
Alexander Graf ag...@suse.de wrote:
On 26.06.2012, at 16:06, Cornelia Huck wrote:
From: Heiko Carstens heiko.carst...@de.ibm.com
If an invalid parameter is passed or the
On Tue, 26 Jun 2012 17:36:19 +0200
Alexander Graf ag...@suse.de wrote:
On 26.06.2012, at 17:33, Cornelia Huck wrote:
On Tue, 26 Jun 2012 16:52:56 +0200
Alexander Graf ag...@suse.de wrote:
On 26.06.2012, at 16:06, Cornelia Huck wrote:
From: Heiko Carstens
On 26.06.2012, at 17:57, Cornelia Huck wrote:
On Tue, 26 Jun 2012 17:36:19 +0200
Alexander Graf ag...@suse.de wrote:
On 26.06.2012, at 17:33, Cornelia Huck wrote:
On Tue, 26 Jun 2012 16:52:56 +0200
Alexander Graf ag...@suse.de wrote:
On 26.06.2012, at 16:06, Cornelia Huck wrote:
During discussions on whether to make -cpu host the default in SLE, I found
myself disagreeing to the thought, because it potentially opens a big can
of worms for potential bugs. But if I already am so opposed to it for SLE, how
can it possibly be reasonable to default to -cpu host in upstream
When running QEMU without -cpu parameter, the user usually wants a sane
default. So far, we're using the qemu64/qemu32 CPU type, which basically
means the maximum TCG can emulate.
That's a really good default when using TCG, but when running with KVM
we much rather want a default saying the
The kvm_enabled() helper doesn't work in a function as early as -cpu ?
yet. It also doesn't make sense to list the -cpu ? output conditional on
the -enable-kvm parameter. So let's always mention -cpu host in the
CPU list when KVM is supported on that configuration.
In addition, this patch also
Hi
This are the minutes for Today call
- q35 integration
why not ICH10? ICH9 is already obsolete.
what are the differences?
We need to check guests from Windows XP and some *BSD.
Having it default for 1.2? Anthony.
Having is as an option in 1.2 and make it defalut in 1.3. Alex?
On Sat, Jun 23, 2012 at 12:55:49AM +0200, Jan Kiszka wrote:
Should have declared this [RFC] in the subject and CC'ed kvm...
On 2012-06-23 00:45, Jan Kiszka wrote:
This sketches a possible path to get rid of the iothread lock on vmexits
in KVM mode. On x86, the the in-kernel irqchips has to
This implementation of a virtio balloon driver uses the page cache to
store pages that have been released to the host. The communication
(outside of target counts) is one way--the guest notifies the host when
it adds a page to the page cache, allowing the host to madvise(2) with
MADV_DONTNEED.
On 06/26/2012 04:32 PM, Frank Swiderski wrote:
This implementation of a virtio balloon driver uses the page cache to
store pages that have been released to the host. The communication
(outside of target counts) is one way--the guest notifies the host when
it adds a page to the page cache,
On Mon, 2012-06-25 at 22:55 -0600, Alex Williamson wrote:
Hi,
VFIO has been kicking around for well over a year now and has been
posted numerous times for review. The pre-requirements are finally
available in linux-next (or will be in the 20120626 build) so I'd like
to request a new branch
On Tue, Jun 26, 2012 at 1:40 PM, Rik van Riel r...@redhat.com wrote:
On 06/26/2012 04:32 PM, Frank Swiderski wrote:
This implementation of a virtio balloon driver uses the page cache to
store pages that have been released to the host. The communication
(outside of target counts) is one
On Tue, Jun 26, 2012 at 01:32:58PM -0700, Frank Swiderski wrote:
This implementation of a virtio balloon driver uses the page cache to
store pages that have been released to the host. The communication
(outside of target counts) is one way--the guest notifies the host when
it adds a page to
On 06/26/2012 05:31 PM, Frank Swiderski wrote:
On Tue, Jun 26, 2012 at 1:40 PM, Rik van Rielr...@redhat.com wrote:
The code looks good to me, my only worry is the
code duplication. We now have 5 balloon drivers,
for 4 hypervisors, all implementing everything
from scratch...
Do you have any
On Tue, Jun 26, 2012 at 02:31:26PM -0700, Frank Swiderski wrote:
On Tue, Jun 26, 2012 at 1:40 PM, Rik van Riel r...@redhat.com wrote:
On 06/26/2012 04:32 PM, Frank Swiderski wrote:
This implementation of a virtio balloon driver uses the page cache to
store pages that have been released to
On Mon, 2012-06-25 at 15:26 +0300, Mihai Caraman wrote:
Refactor exception prolog to allow save/restore register parameters. Add
addition none definition for exception prolog usage.
This is needed for exceptions like Guest Doorbell that use GSRRx regsiters
which do not map on exception type.
On Mon, 2012-06-25 at 15:26 +0300, Mihai Caraman wrote:
Machine check exception handler was using a wrong prolog. Hypervisors, like
KVM, which are called early from the exception handler rely on the interrupt
source.
Signed-off-by: Mihai Caraman mihai.cara...@freescale.com
Ack.
Please
On Mon, 2012-06-25 at 15:26 +0300, Mihai Caraman wrote:
Embedded.Hypervisor category defines GSPRG0..3 physical registers for guests.
Avoid SPRG4-7 usage as scratch in host exception handlers, otherwise guest
SPRG4-7 registers will be clobbered.
For bolted TLB miss exception handlers, which is
On 06/25/2012 07:26 AM, Mihai Caraman wrote:
Embedded.Hypervisor category defines GSPRG0..3 physical registers for guests.
Avoid SPRG4-7 usage as scratch in host exception handlers, otherwise guest
SPRG4-7 registers will be clobbered.
For bolted TLB miss exception handlers, which is the
On 06/25/2012 07:26 AM, Mihai Caraman wrote:
Add KVM_SREGS_E_64 feature and EPCR spr support in get/set sregs
for 64-bit hosts.
Signed-off-by: Mihai Caraman mihai.cara...@freescale.com
---
arch/powerpc/kvm/booke.c | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
On Tue, Jun 26, 2012 at 2:47 PM, Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Jun 26, 2012 at 02:31:26PM -0700, Frank Swiderski wrote:
On Tue, Jun 26, 2012 at 1:40 PM, Rik van Riel r...@redhat.com wrote:
On 06/26/2012 04:32 PM, Frank Swiderski wrote:
This implementation of a virtio
On Tue, Jun 26, 2012 at 2:45 PM, Rik van Riel r...@redhat.com wrote:
On 06/26/2012 05:31 PM, Frank Swiderski wrote:
On Tue, Jun 26, 2012 at 1:40 PM, Rik van Rielr...@redhat.com wrote:
The code looks good to me, my only worry is the
code duplication. We now have 5 balloon drivers,
for 4
Hi Alex,
On Mon, 25 Jun 2012 22:55:52 -0600 Alex Williamson alex.william...@redhat.com
wrote:
VFIO has been kicking around for well over a year now and has been
posted numerous times for review. The pre-requirements are finally
available in linux-next (or will be in the 20120626 build) so
From: Namhyung Kim namhyung@lge.com
The kvm_emulate_insn tracepoint used __print_insn()
for printing its instructions. However it makes the
format of the event hard to parse as it reveals TP
internals.
Fortunately, kernel provides __print_hex for almost
same purpose, we can use it instead of
We only know of one so far.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
virt/kvm/eventfd.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/virt/kvm/eventfd.c b/virt/kvm/eventfd.c
index c307c24..7d7e2aa 100644
--- a/virt/kvm/eventfd.c
+++ b/virt/kvm/eventfd.c
@@
In order to inject an interrupt from an external source using an
irqfd, we need to allocate a new irq_source_id. This allows us to
assert and (later) de-assert an interrupt line independently from
users of KVM_IRQ_LINE and avoid lost interrupts.
We also add what may appear like a bit of
This new ioctl enables an eventfd to be triggered when an EOI is
written for a specified irqchip pin. By default this is a simple
notification, but we can also tie the eoifd to a level irqfd, which
enables the irqchip pin to be automatically de-asserted on EOI.
This mode is particularly useful
This is an alternate level irqfd de-assert mode that's potentially
useful for emulated drivers. It's included here to show how easy it
is to implement with the new level irqfd and eoifd support. It's
possible this mode might also prove interesting for device-assignment
where we inject via level
Ok, let's see how this flies. I actually quite like this, so be
gentle tearing it apart ;)
I just couldn't bring myself to contort KVM_IRQFD into something
that either sets up an irqfd or specifies a nearly unrelated EOI
eventfd. The solution I've come up with, that also avoids exposing
Prune this down to just the struct kvm_irqfd so we can avoid
changing function definition for every flag or field we use.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
include/linux/kvm_host.h |4 ++--
virt/kvm/eventfd.c | 20 ++--
virt/kvm/kvm_main.c
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
Documentation/virtual/kvm/api.txt | 16
1 file changed, 16 insertions(+)
diff --git a/Documentation/virtual/kvm/api.txt
b/Documentation/virtual/kvm/api.txt
index 310fe50..ea9edce 100644
---
On Mon, 2012-06-25 at 15:26 +0300, Mihai Caraman wrote:
Refactor exception prolog to allow save/restore register parameters. Add
addition none definition for exception prolog usage.
This is needed for exceptions like Guest Doorbell that use GSRRx regsiters
which do not map on exception type.
On Mon, 2012-06-25 at 15:26 +0300, Mihai Caraman wrote:
Embedded.Hypervisor category defines GSPRG0..3 physical registers for guests.
Avoid SPRG4-7 usage as scratch in host exception handlers, otherwise guest
SPRG4-7 registers will be clobbered.
For bolted TLB miss exception handlers, which is
On 06/25/2012 07:26 AM, Mihai Caraman wrote:
Embedded.Hypervisor category defines GSPRG0..3 physical registers for guests.
Avoid SPRG4-7 usage as scratch in host exception handlers, otherwise guest
SPRG4-7 registers will be clobbered.
For bolted TLB miss exception handlers, which is the
On 06/25/2012 07:26 AM, Mihai Caraman wrote:
Add KVM_SREGS_E_64 feature and EPCR spr support in get/set sregs
for 64-bit hosts.
Signed-off-by: Mihai Caraman mihai.cara...@freescale.com
---
arch/powerpc/kvm/booke.c | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
56 matches
Mail list logo
