On Thu, Jun 21, 2012 at 2:49 PM, Emmanuel Noobadmin
wrote:
> On 6/20/12, Stefan Hajnoczi wrote:
>> Anyway, once you've tried qemu.git/master we'll know whether the bug
>> still exists and with all the info you've shared maybe Gerd (USB
>> maintainer) will know what the issue is.
>
> Sadly, my noo
On 07/06/12 09:17, Alex Williamson wrote:
> On Fri, 2012-05-25 at 17:35 +1000, Alexey Kardashevskiy wrote:
>> Some adapters (like NEC PCI USB controller) do not flush their config
>> on a sioftware reset and remember DMA config, etc.
>>
>> If we use such an adapter with QEMU, then crash QEMU (stop
On Thu, 21 Jun 2012 17:52:38 +0900
Takuya Yoshikawa wrote:
...
> + /* Handle the first one even if idx == idx_end. */
> + do {
> + ret |= handler(kvm, rmapp++, data);
> + } while (++idx < idx_end);
This is un
On Thu, Jun 21, 2012 at 04:56:08PM +0530, Raghavendra K T wrote:
> Here are the results from kernbench.
>
> PS: I think we have to only take that, both the patches perform better,
> than reading into actual numbers since I am seeing more variance in
> especially 3x. may be I can test with some mor
From: Stuart Yoder
This is a reworked version of the v10 patchset I sent out back
in March, address the comments, plus adding some additional
fixes found in further testing.
Liu Yu-B13201 (3):
KVM: PPC: Add support for ePAPR idle hcall in host kernel
KVM: PPC: ev_idle hcall support for e500
From: Stuart Yoder
Signed-off-by: Stuart Yoder
---
-this is a new patch in v11
arch/powerpc/include/asm/epapr_hcalls.h |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/include/asm/epapr_hcalls.h
b/arch/powerpc/include/asm/epapr_hcalls.h
index bf2c06c..c0
From: Stuart Yoder
Signed-off-by: Stuart Yoder
---
-v11:
-as per Alex's comments, created a KVM hcall macro to
simplify code creating hcall tokens
-used macro for success return code
arch/powerpc/include/asm/kvm_para.h | 21 +++--
arch/powerpc/kernel/kvm.c
From: Stuart Yoder
Signed-off-by: Liu Yu
[stuart: factored this out from idle hcall support in host patch]
Signed-off-by: Stuart Yoder
---
-v11
-split this code out into a separate patch as per the review
comments
arch/powerpc/kvm/powerpc.c | 10 +-
1 files changed, 9 inserti
From: Liu Yu-B13201
And add a new flag definition in kvm_ppc_pvinfo to indicate
whether the host supports the EV_IDLE hcall.
Signed-off-by: Liu Yu
[stuart.yo...@freescale.com: cleanup,fixes for conditions allowing idle]
Signed-off-by: Stuart Yoder
---
-v11:
-added PV info flag definition in
From: Liu Yu-B13201
Signed-off-by: Liu Yu
[varun: 64-bit changes]
Signed-off-by: Varun Sethi
Signed-off-by: Stuart Yoder
---
-v11:
-added comment about origin of idle instruction sequence
-update for 64-bit support found in testing
arch/powerpc/include/asm/epapr_hcalls.h | 11 +--
From: Stuart Yoder
Signed-off-by: Stuart Yoder
---
-new in v11-- this patch is needed so the dependencies are correct
for all users of epapr hcalls, without it there will be build issues
after hardcoded opcodes for hcalls are removed
arch/powerpc/platforms/Kconfig |1 +
drivers/tty/Kconf
Stuart Yoder wrote:
> -new in v11-- this patch is needed so the dependencies are correct
> for all users of epapr hcalls, without it there will be build issues
> after hardcoded opcodes for hcalls are removed
This should have been part of the patch description.
--
Timur Tabi
Linux kernel devel
From: Scott Wood
Signed-off-by: Scott Wood
Signed-off-by: Stuart Yoder
---
-new in v11-- this is derived from an internal patch from Scott,
without it there will be build issues after hardcoded opcodes for
hcalls are removed
arch/powerpc/sysdev/fsl_msi.c |9 +++--
arch/powerpc/sysde
From: Liu Yu-B13201
Signed-off-by: Liu Yu
Signed-off-by: Stuart Yoder
---
-v11: no changes
arch/powerpc/include/asm/epapr_hcalls.h | 22 +-
arch/powerpc/include/asm/fsl_hcalls.h | 36 +++---
2 files changed, 29 insertions(+), 29 deletions(-)
diff
On 06/22/2012 08:41 PM, Andrew Jones wrote:
On Thu, Jun 21, 2012 at 04:56:08PM +0530, Raghavendra K T wrote:
Here are the results from kernbench.
PS: I think we have to only take that, both the patches perform better,
than reading into actual numbers since I am seeing more variance in
especiall
I've cc'ed the KVM list to get their early input on this.
On Mon, May 14, 2012 at 9:06 AM, Marc Zyngier wrote:
> Reflect the changes in the API due to the introduction of VGIC.
>
> Signed-off-by: Marc Zyngier
> ---
> Documentation/virtual/kvm/api.txt | 24 +---
> 1 files c
I'm running a Windows XP guest which is experiencing poor performance
with the virtio drivers. I'm booting the guest with the modified vfio
kernel and qemu from https://github.com/awilliam/qemu-vfio and
https://github.com/awilliam/linux-vfio to use a vfio PCI device, as
well as using the qemu from
Here's a refined series based on my previous RFC. I now have this
working through VFIO-based device assignment in Qemu. I've split
up the patches and tried to generalize the interface as one of
potentially a couple ways we might support level irqfds. I also
tried to document the requirements aro
Prune this down to just the struct kvm_irqfd so we can avoid
changing function definition for every flag for field we use.
Signed-off-by: Alex Williamson
---
include/linux/kvm_host.h |4 ++--
virt/kvm/eventfd.c | 20 ++--
virt/kvm/kvm_main.c |2 +-
3 files c
Signed-off-by: Alex Williamson
---
Documentation/virtual/kvm/api.txt | 17 +
1 file changed, 17 insertions(+)
diff --git a/Documentation/virtual/kvm/api.txt
b/Documentation/virtual/kvm/api.txt
index 310fe50..9b4cb2b 100644
--- a/Documentation/virtual/kvm/api.txt
+++ b/Documen
KVM_IRQFD currently only supports edge triggered interrupts,
asserting then immediately deasserting an interrupt. There are a
couple ways we can emulate level triggered interrupts using
discrete events depending on the usage model we expect from drivers.
This patch implements a level emulation mod
I think we're probably also going to need something like this.
When running in non-accelerated qemu, we're going to have to
create some kind of EOI notifier for drivers. VFIO can make
additional improvements when running on KVM so it will probably
make use of the KVM_IRQFD_LEVEL_EOI interface, but
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 be used because
> we otherwise need to synchronize APIC and oth
ESR register is required by Data Storage Interrupt handling code.
Add the specific flag to the interrupt handler.
Signed-off-by: Mihai Caraman
---
arch/powerpc/kvm/bookehv_interrupts.S |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/kvm/bookehv_interrupts.S
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
On 6/22/12, Stefan Hajnoczi wrote:
> Thanks for investigating and sharing the information you've found.
> It's archived on the list so anyone who hits it in the future or wants
> to reproduce it can try.
I decided to give it one more try before I formatted that machine and
tried the rpm method. T
26 matches
Mail list logo
