From: Alex Williamson alex.william...@redhat.com
Include the first byte at 40h or else access might go to the
hardware instead of the emulated config space, resulting in
capability loops, since the ordering is different.
Signed-off-by: Alex Williamson alex.william...@redhat.com
Signed-off-by:
From: Alex Williamson alex.william...@redhat.com
Half of these aren't used anywhere, the other half are wrong. Now that
device assignment is trying to match physical hardware offsets for PCI
capabilities, we can't round up the MSI and MSI-X length. MSI-X is
always 12 bytes. MSI is variable
From: Alex Williamson alex.william...@redhat.com
Nothing good can happen when we overlap capabilities
Signed-off-by: Alex Williamson alex.william...@redhat.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/hw/pci.c b/hw/pci.c
index b08113d..288d6fd 100644
--- a/hw/pci.c
+++ b/hw/pci.c
From: Alex Williamson alex.william...@redhat.com
Signed-off-by: Alex Williamson alex.william...@redhat.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/hw/device-assignment.c b/hw/device-assignment.c
index 1a90a89..0ae04de 100644
--- a/hw/device-assignment.c
+++
From: Alex Williamson alex.william...@redhat.com
Some drivers depend on finding capabilities like power management,
PCI express/X, vital product data, or vendor specific fields. Now
that we have better capability support, we can pass more of these
tables through to the guest. Note that VPD and
From: Joerg Roedel joerg.roe...@amd.com
This patch adds the clean-bit for intercepts-vectors, the
TSC offset and the pause-filter count to the appropriate
places. The IO and MSR permission bitmaps are not subject to
this bit.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
Signed-off-by: Avi
From: Joerg Roedel joerg.roe...@amd.com
This patch adds the clean bit for the physical addresses of
the MSRPM and the IOPM. It does not need to be set in the
code because the only place where these values are changed
is the nested-svm vmrun and vmexit path. These functions
already mark the
From: Roedel, Joerg joerg.roe...@amd.com
This patch adds the infrastructure for the implementation of
the individual clean-bits.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/arch/x86/include/asm/svm.h b/arch/x86/include/asm/svm.h
index
From: Joerg Roedel joerg.roe...@amd.com
This patch implements the clean-bit for the asid in the
vmcb.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
index 1802f7c..a3fd9ba 100644
---
From: Joerg Roedel joerg.roe...@amd.com
This patch implements the clean-bit for all interrupt
related state in the vmcb. This corresponds to vmcb offset
0x60-0x67.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/arch/x86/kvm/svm.c
From: Joerg Roedel joerg.roe...@amd.com
This patch implements the CRx clean-bit for the vmcb. This
bit covers cr0, cr3, cr4, and efer.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
index
From: Joerg Roedel joerg.roe...@amd.com
This patch implements the clean-bit defined for the cs, ds,
ss, an es segemnts and the current cpl saved in the vmcb.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/arch/x86/kvm/svm.c
From: Joerg Roedel joerg.roe...@amd.com
This patch implements the clean-bit for all LBR related
state. This includes the debugctl, br_from, br_to,
last_excp_from, and last_excp_to msrs.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git
From: Joerg Roedel joerg.roe...@amd.com
This patch implements the clean-bit for the cr2 register in
the vmcb.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
index 85d3350..e5db339 100644
---
From: Xiao Guangrong xiaoguangr...@cn.fujitsu.com
It's the speculative path if 'no_apf = 1' and we will specially handle this
speculative path in the later patch, so 'prefault' is better to fit the sense.
Signed-off-by: Xiao Guangrong xiaoguangr...@cn.fujitsu.com
Signed-off-by: Avi Kivity
From: Joerg Roedel joerg.roe...@amd.com
This function is unused and there is svm_flush_tlb which
does the same. So this function can be removed.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
index
From: Xiao Guangrong xiaoguangr...@cn.fujitsu.com
Retry #PF is the speculative path, so don't set the accessed bit
Signed-off-by: Xiao Guangrong xiaoguangr...@cn.fujitsu.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index 4954de9..04f9033
From: Xiao Guangrong xiaoguangr...@cn.fujitsu.com
Retry #PF for softmmu only when the current vcpu has the same cr3 as the time
when #PF occurs
Signed-off-by: Xiao Guangrong xiaoguangr...@cn.fujitsu.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/arch/x86/include/asm/kvm_host.h
From: Joerg Roedel joerg.roe...@amd.com
This patch replaces all calls to force_new_asid which are
intended to flush the guest-tlb by the more appropriate
function svm_flush_tlb. As a side-effect the force_new_asid
function is removed.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
From: Joerg Roedel joerg.roe...@amd.com
This patch adds the new flush-by-asid of upcoming AMD
processors to the KVM-AMD module.
Signed-off-by: Joerg Roedel joerg.roe...@amd.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/arch/x86/include/asm/svm.h b/arch/x86/include/asm/svm.h
index
From: Anthony Liguori aligu...@us.ibm.com
In certain use-cases, we want to allocate guests fixed time slices where idle
guest cycles leave the machine idling. There are many approaches to achieve
this but the most direct is to simply avoid trapping the HLT instruction which
lets the guest
From: Sheng Yang sh...@linux.intel.com
CPUID's OSXSAVE is a mirror of CR4.OSXSAVE bit. We need to update the CPUID
after migration.
KVM-Stable-Tag.
Signed-off-by: Sheng Yang sh...@linux.intel.com
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
From: Avi Kivity a...@redhat.com
If KVM sees a read-only host page, it will map it as read-only to prevent
breaking a COW. However, if the page was part of a large guest page, KVM
incorrectly extends the write protection to the entire large page frame
instead of limiting it to the normal host
From: Avi Kivity a...@redhat.com
Make it available for all archs.
Signed-off-by: Avi Kivity a...@redhat.com
diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
index bd0da8f..b5021db 100644
--- a/include/linux/kvm_host.h
+++ b/include/linux/kvm_host.h
@@ -256,8 +256,8 @@ struct kvm
From: Joerg Roedel joerg.roe...@amd.com
To support xsave properly for the guest the SVM module need
software support for it. As long as this is not present do
not report the xsave as supported feature in cpuid.
As a side-effect this patch moves the bit() helper function
into the x86.h file so
On Sun, 12 Dec 2010, Jan Kiszka wrote:
Am 12.12.2010 18:29, Thomas Gleixner wrote:
Also we should name it different than status, drv_status perhaps, to
avoid confusion with the irq_desc status.
OK, will address both in a succeeding round (just waiting for potential
further comments).
No
On 12.12.2010, at 23:31, Erik Brakkee wrote:
Jan Kiszka wrote:
Are there some tuning parameters I can use or perhaps even kernel
configuration paramters on the host to solve this?
Cheers
Erik
Host:Motherboard Supermicro X8DTi-F, Intel Xeon L5630, 12MB
OS: Opensuse
On 12/10/2010 04:41 PM, Jan Kiszka wrote:
Am 10.12.2010 08:42, Lai Jiangshan wrote:
Make use of the new KVM_NMI IOCTL to send NMIs into the KVM guest if the
user space raised them. (example: qemu monitor's nmi command)
Signed-off-by: Lai Jiangshan la...@cn.fujitsu.com
---
diff --git
* Avi Kivity a...@redhat.com [2010-12-11 09:31:24]:
On 12/10/2010 07:03 AM, Balbir Singh wrote:
Scheduler people, please flame me with anything I may have done
wrong, so I can do it right for a next version :)
This is a good problem statement, there are other things to consider
as
On Sun, Dec 12, 2010 at 12:22:40PM +0100, Jan Kiszka wrote:
The result may look simpler on first glance than v1, but it comes with
more subtle race scenarios IMO. I thought them through, hopefully
catching all, but I would appreciate any skeptical review.
Thought about the races till my head
On 12/12/2010 01:22 PM, Jan Kiszka wrote:
From: Jan Kiszkajan.kis...@siemens.com
PCI 2.3 allows to generically disable IRQ sources at device level. This
enables us to share IRQs of such devices on the host side when passing
them to a guest.
However, IRQ disabling via the PCI config space is
Currently, if the page is not allowed to write, then it can drop
ACC_WRITE_MASK in pte_access, and the direct sp's access is:
gw-pt_access gw-pte_access
so, it also removes the write access in the direct sp.
There is a problem: if the access of those pages which map thought the same
It only allows to audit one guest in the system since:
- 'audit_point' is a glob variable
- mmu_audit_disable() is called in kvm_mmu_destroy(), so audit is disabled
after a guest exited
this patch fix those issues then allow to audit more guests at the same time
Signed-off-by: Xiao Guangrong
On 12/13/2010 12:31 PM, Xiao Guangrong wrote:
Currently, if the page is not allowed to write, then it can drop
ACC_WRITE_MASK in pte_access, and the direct sp's access is:
gw-pt_access gw-pte_access
so, it also removes the write access in the direct sp.
There is a problem: if the
Hi,
I am using a tv card in a VM and get jerky video.As I understand it, the
VM is using USB 1.1. However, when I set the USB controller in the BIOS
of my server to Fullspeed (12 Mbit/s) which is the USB 1.1 speed I am
able to get perfect results on the host but still on the guest the video
Please merge the following tree for 2.6.38.
Thanks!
The following changes since commit ad1184c6cf067a13e8cb2a4e7ccc407f947027d0:
net: au1000_eth: remove unused global variable. (2010-12-11 12:01:48 -0800)
are available in the git repository at:
Hi
2010/12/13 Stefan Hajnoczi stefa...@gmail.com:
On Dec 13, 2010 5:14 AM, अनुज anu...@gmail.com wrote:
Hi
I am trying to implement VirtIO support for a proprietary OS. And It
would be great if I am able to process SCSI commands over VirtIO Block
device.
I tried to execute INQUIRY
(2010/12/13 2:47), Avi Kivity wrote:
On 12/12/2010 07:43 PM, Arnaldo Carvalho de Melo wrote:
Em Sun, Dec 12, 2010 at 07:42:06PM +0200, Avi Kivity escreveu:
On 12/12/2010 07:36 PM, Arnaldo Carvalho de Melo wrote:
Em Sun, Dec 12, 2010 at 06:35:24PM +0200, Avi Kivity escreveu:
On
On 12/11/2010 03:57 PM, Balbir Singh wrote:
* Avi Kivitya...@redhat.com [2010-12-11 09:31:24]:
On 12/10/2010 07:03 AM, Balbir Singh wrote:
Scheduler people, please flame me with anything I may have done
wrong, so I can do it right for a next version :)
This is a good
On 12/09/2010 06:16 PM, Alex Williamson wrote:
Signed-off-by: Alex Williamsonalex.william...@redhat.com
Applied, thanks.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to
On 12/09/2010 08:43 AM, Wei Yongjun wrote:
Fix the following compile error in next tree:
CCx86_64-softmmu/device-assignment.o
hw/device-assignment.c: In function ‘assigned_device_pci_cap_init’:
hw/device-assignment.c:1463: error: ‘PCI_PM_CTRL_NO_SOFT_RST’ undeclared
(first use in this
On 12/08/2010 01:27 PM, Andre Przywara wrote:
The handling of CR8 writes in KVM is currently somewhat cumbersome.
This patch makes it look like the other CR register handlers
and fixes a possible issue in VMX, where the RIP would be incremented
despite an injected #GP.
unsigned long
On 12/10/2010 03:51 PM, Andre Przywara wrote:
Newer SVM implementations provide the GPR number in the VMCB, so
that the emulation path is no longer necesarry to handle CR
register access intercepts. Implement the handling in svm.c and
use it when the info is provided.
Signed-off-by: Andre
On 12/10/2010 03:51 PM, Andre Przywara wrote:
Newer SVM implementations provide the GPR number in the VMCB, so
that the emulation path is no longer necesarry to handle debug
register access intercepts. Implement the handling in svm.c and
use it when the info is provided.
+
+ if (!err)
+
On 12/10/2010 03:51 PM, Andre Przywara wrote:
In case of a nested page fault or an intercepted #PF newer SVM
implementations provide a copy of the faulting instruction bytes
in the VMCB.
Use these bytes to feed the instruction emulator and avoid the costly
guest instruction fetch in this case.
* Avi Kivity a...@redhat.com [2010-12-13 13:57:37]:
On 12/11/2010 03:57 PM, Balbir Singh wrote:
* Avi Kivitya...@redhat.com [2010-12-11 09:31:24]:
On 12/10/2010 07:03 AM, Balbir Singh wrote:
Scheduler people, please flame me with anything I may have done
wrong, so I can do
On 12/13/2010 02:39 PM, Balbir Singh wrote:
* Avi Kivitya...@redhat.com [2010-12-13 13:57:37]:
On 12/11/2010 03:57 PM, Balbir Singh wrote:
* Avi Kivitya...@redhat.com [2010-12-11 09:31:24]:
On 12/10/2010 07:03 AM, Balbir Singh wrote:
Scheduler people, please flame
Hi
Where can I find out, the order in which the CPUs are discovered?
When having:
- Multiple sockets.
- Multiple cores.
- Hyper-threading (HTT).
E.g. a single Socket with two cores and HTT enabled on both cores.
This would be 4 CPUs.
Would cpu0 and cpu1 be the first core, and cpu2 and 3
On Wed, 2010-12-08 at 17:31 -0200, Marcelo Tosatti wrote:
On Tue, Dec 07, 2010 at 03:12:36PM -0200, Glauber Costa wrote:
On Mon, 2010-12-06 at 19:04 -0200, Marcelo Tosatti wrote:
On Mon, Dec 06, 2010 at 09:03:46AM -0500, Glauber Costa wrote:
Usually nobody usually thinks about that
Currently, we record '1' for count regardless of the real count. Fix.
Signed-off-by: Avi Kivity a...@redhat.com
---
arch/x86/kvm/x86.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index 8d76150..cf5fab1 100644
---
On Sun, 2010-12-12 at 18:10 +0200, Avi Kivity wrote:
On 11/23/2010 12:52 PM, Avi Kivity wrote:
I see a trace_printk() commit in trace-cmd.git. Is that related? If
not, I'll work on getting a small sample of the problem.
Sample: http://people.redhat.com/akivity/trace.dat.bz2
You
On 12/13/2010 05:26 PM, Steven Rostedt wrote:
On Sun, 2010-12-12 at 18:10 +0200, Avi Kivity wrote:
On 11/23/2010 12:52 PM, Avi Kivity wrote:
I see a trace_printk() commit in trace-cmd.git. Is that related? If
not, I'll work on getting a small sample of the problem.
Sample:
On Mon, 2010-12-13 at 17:43 +0200, Avi Kivity wrote:
What's your work flow? Do you
load kvm modules after you start the trace, or are they always loaded?
Loaded on boot.
Via initramfs?
Are the trace_printk's in the core kernel too, and not being printed?
I don't have any
On Mon, Dec 06, 2010 at 02:37:05PM -0200, Thiago Farina wrote:
On Mon, Nov 29, 2010 at 3:16 PM, Michael S. Tsirkin m...@redhat.com wrote:
+#define container_of(ptr, type, member) ({ \
+ const typeof( ((type *)0)-member ) *__mptr = (ptr); \
+ (type *)(
On 12/11/2010 08:57 AM, Balbir Singh wrote:
If the vpcu holding the lock runs more and capped, the timeslice
transfer is a heuristic that will not help.
That indicates you really need the cap to be per guest, and
not per VCPU.
Having one VCPU spin on a lock (and achieve nothing), because
the
On 12/13/2010 06:28 PM, Steven Rostedt wrote:
On Mon, 2010-12-13 at 17:43 +0200, Avi Kivity wrote:
What's your work flow? Do you
load kvm modules after you start the trace, or are they always loaded?
Loaded on boot.
Via initramfs?
No, regular printks.
Are the
On 12/13/2010 07:05 PM, Avi Kivity wrote:
On 12/13/2010 06:28 PM, Steven Rostedt wrote:
On Mon, 2010-12-13 at 17:43 +0200, Avi Kivity wrote:
What's your work flow? Do you
load kvm modules after you start the trace, or are they always
loaded?
Loaded on boot.
Via initramfs?
No,
On Mon, Dec 06, 2010 at 03:23:02PM +1030, Rusty Russell wrote:
On Tue, 30 Nov 2010 03:46:37 am Michael S. Tsirkin wrote:
This is the userspace part of the tool: it includes a bunch of stubs for
linux APIs, somewhat simular to linuxsched. This makes it possible to
recompile the ring code in
On Mon, Dec 13, 2010 at 12:44:13PM +0200, Michael S. Tsirkin wrote:
Please merge the following tree for 2.6.38.
Thanks!
Um, I sent this out before I noticed the mail from Rusty
with some questions on the test code. I missed that and
assumed no comments - no issues, perhaps wrongly.
Rusty - I
Gleb Natapov gleb at redhat.com writes:
On Wed, Jul 28, 2010 at 12:53:02AM +0300, Harri Olin wrote:
Gleb Natapov wrote:
On Wed, Jul 21, 2010 at 09:25:31AM +0300, Harri Olin wrote:
Gleb Natapov kirjoitti:
On Mon, Jul 19, 2010 at 10:17:02AM +0300, Harri Olin wrote:
Gleb Natapov
On 12/13/2010 09:42 PM, Manfred Heubach wrote:
Gleb Natapovglebat redhat.com writes:
On Wed, Jul 28, 2010 at 12:53:02AM +0300, Harri Olin wrote:
Gleb Natapov wrote:
On Wed, Jul 21, 2010 at 09:25:31AM +0300, Harri Olin wrote:
Gleb Natapov kirjoitti:
On Mon, Jul 19, 2010 at 10:17:02AM
On Mon, 2010-12-13 at 22:12 +0200, Dor Laor wrote:
On 12/13/2010 09:42 PM, Manfred Heubach wrote:
Gleb Natapovglebat redhat.com writes:
On Wed, Jul 28, 2010 at 12:53:02AM +0300, Harri Olin wrote:
Gleb Natapov wrote:
On Wed, Jul 21, 2010 at 09:25:31AM +0300, Harri Olin wrote:
No comments since v3, please apply. Thanks,
Alex
v3:
- Address review comments
- pc registers all memory below 4G in one chunk
Let me know if there are any further issues.
v2:
- Move to Makefile.objs
- Move structures to memory.c and create a callback function
- Fix memory leak
I
This adds a minimum chunk of Anthony's RAM API support so that we
can identify actual VM RAM versus all the other things that make
use of qemu_ram_alloc.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
Makefile.objs |1 +
cpu-common.h |2 +
memory.c | 97
Register the actual VM RAM using the new API
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
hw/pc.c |9 +++--
1 files changed, 3 insertions(+), 6 deletions(-)
diff --git a/hw/pc.c b/hw/pc.c
index e1b2667..1554164 100644
--- a/hw/pc.c
+++ b/hw/pc.c
@@ -913,14 +913,11 @@
On 12/13/2010 02:47 PM, Alex Williamson wrote:
This adds a minimum chunk of Anthony's RAM API support so that we
can identify actual VM RAM versus all the other things that make
use of qemu_ram_alloc.
Signed-off-by: Alex Williamsonalex.william...@redhat.com
---
Makefile.objs |1 +
On Mon, Dec 13, 2010 at 8:47 PM, Alex Williamson
alex.william...@redhat.com wrote:
This adds a minimum chunk of Anthony's RAM API support so that we
can identify actual VM RAM versus all the other things that make
use of qemu_ram_alloc.
Signed-off-by: Alex Williamson
Required for regions mapped via qemu_ram_alloc_from_ptr(). VFIO
and ivshmem will make use of this to remove mappings when devices
are hot unplugged.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
No comments on original patch. Obvious missing function. Cam has since
requested
This adds a minimum chunk of Anthony's RAM API support so that we
can identify actual VM RAM versus all the other things that make
use of qemu_ram_alloc.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
Makefile.objs |1 +
cpu-common.h |2 +
memory.c | 94
Update per comments, Thanks,
Alex
v4:
- ram_slot - RamSlot (per CODING_STYLE)
- drop qemu_ prefix from functions (per CODING_STYLE)
- mallocz - malloc
- drop extraneous return from void function
v3:
- Address review comments
- pc registers all memory below 4G in one chunk
Let me know
Register the actual VM RAM using the new API
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
hw/pc.c |9 +++--
1 files changed, 3 insertions(+), 6 deletions(-)
diff --git a/hw/pc.c b/hw/pc.c
index e1b2667..87adca2 100644
--- a/hw/pc.c
+++ b/hw/pc.c
@@ -913,14 +913,11 @@
Do not call pci_update_mappings on the lower 32-bits of a 64-bit bar. Wait for
the upper 32 or else Qemu will try to map on just the lower 32 which is
probably going to corrupt memory.
I was encountering crashes when mapping certain PCI region sizes. The problem
turns out that
Am 13.12.2010 11:10, Michael S. Tsirkin wrote:
On Sun, Dec 12, 2010 at 12:22:40PM +0100, Jan Kiszka wrote:
The result may look simpler on first glance than v1, but it comes with
more subtle race scenarios IMO. I thought them through, hopefully
catching all, but I would appreciate any skeptical
This addresses the review comments of the previous round:
- renamed irq_data::status to drv_status
- moved drv_status around to unbreak GENERIC_HARDIRQS_NO_DEPRECATED
- fixed signature of get_irq_status (irq is now unsigned int)
- converted register_lock into a global one
- fixed critical
From: Jan Kiszka jan.kis...@siemens.com
This associates a status word with every IRQ descriptor. Drivers can obtain
its content via get_irq_status(irq). First use case will be propagating the
interrupt sharing state.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
include/linux/interrupt.h
From: Jan Kiszka jan.kis...@siemens.com
PCI 2.3 allows to generically disable IRQ sources at device level. This
enables us to share IRQs of such devices on the host side when passing
them to a guest.
However, IRQ disabling via the PCI config space is more costly than
masking the line via
From: Jan Kiszka jan.kis...@siemens.com
This enabled interrupt handlers to retrieve the current line sharing state via
the new interrupt status word so that they can adapt to it.
The switch from shared to exclusive is generally uncritical and can thus be
performed on demand. However, preparing a
From: Jan Kiszka jan.kis...@siemens.com
Provide an adaptive version of IRQF_ONESHOT: If the line is exclusively used,
IRQF_COND_ONESHOT provides the same semantics as IRQF_ONESHOT. If it is
shared, the line will be unmasked directly after the hardirq handler, just as
if IRQF_COND_ONESHOT was not
This series includes cleanups of the PCI config access of assigned
devices, fixes a corner case in this area, removes that suspicious VGA
hunk from assigned_dev_pci_read_config, and finally enables support for
the latest host IRQ sharing support via PCI-2.3 interrupt masking. See
the patches for
From: Jan Kiszka jan.kis...@siemens.com
Use rages_overlap and proper constants to match the access range against
regions that need special handling. This also fixes yet uncaught
high-byte write access to the command register. Moreover, use more
constants instead of magic numbers.
Signed-off-by:
From: Jan Kiszka jan.kis...@siemens.com
If we emulate the command register, we must only read its content from
the shadow config space. For dword read of both PCI_COMMAND and
PCI_STATUS, at least the latter must be read from the device.
For simplicity reasons and as the code path is not
From: Jan Kiszka jan.kis...@siemens.com
Define a mask of PCI command register bits that need to be emulated,
i.e. read back from their shadow state. We will need this for
selectively emulating the INTx mask bit.
Note: No initialization of emulate_cmd_mask to zero needed, the device
state is
From: Jan Kiszka jan.kis...@siemens.com
Enable the new KVM feature that allows legacy interrupt sharing for
PCI-2.3-compliant devices. This requires to synchronize any guest
change of the INTx mask bit to the kernel.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
hw/device-assignment.c |
Am 12.12.2010 23:31, Erik Brakkee wrote:
Jan Kiszka wrote:
Are there some tuning parameters I can use or perhaps even kernel
configuration paramters on the host to solve this?
Cheers
Erik
Host:Motherboard Supermicro X8DTi-F, Intel Xeon L5630, 12MB
OS: Opensuse 11.3
2010/12/12 Erik Brakkee e...@brakkee.org:
Does this mean I have a chance now that PCI passthrough of my WinTV PVR-500
might work now?
Passthrough of a PVR-500 has been working for a long time. I've been
running with passthrough of a PVR-500 in my HTPC, since
November/December 2009...so it
On Tue, 2010-12-14 at 00:25 +0100, Jan Kiszka wrote:
From: Jan Kiszka jan.kis...@siemens.com
If we emulate the command register, we must only read its content from
the shadow config space. For dword read of both PCI_COMMAND and
PCI_STATUS, at least the latter must be read from the device.
On Tue, 2010-12-14 at 00:25 +0100, Jan Kiszka wrote:
From: Jan Kiszka jan.kis...@siemens.com
Use rages_overlap and proper constants to match the access range against
regions that need special handling. This also fixes yet uncaught
high-byte write access to the command register. Moreover, use
On Tue, 2010-12-14 at 00:25 +0100, Jan Kiszka wrote:
From: Jan Kiszka jan.kis...@siemens.com
No one can remember where this came from, and it looks very hacky
anyway (we return 0 for config space address 0xfc of _every_ assigned
device, not only vga as the comment claims). So better remove
On Tue, 2010-12-14 at 00:25 +0100, Jan Kiszka wrote:
From: Jan Kiszka jan.kis...@siemens.com
Define a mask of PCI command register bits that need to be emulated,
i.e. read back from their shadow state. We will need this for
selectively emulating the INTx mask bit.
Note: No initialization
Please send in any agenda items you are interested in covering.
thanks,
-chris
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, 2010-12-14 at 00:25 +0100, Jan Kiszka wrote:
From: Jan Kiszka jan.kis...@siemens.com
Enable the new KVM feature that allows legacy interrupt sharing for
PCI-2.3-compliant devices. This requires to synchronize any guest
change of the INTx mask bit to the kernel.
Signed-off-by: Jan
2010/12/14 Erik Brakkee e...@brakkee.org:
From: Kenni Lund ke...@kelu.dk
Does this mean I have a chance now that PCI passthrough of my WinTV
PVR-500
might work now?
Passthrough of a PVR-500 has been working for a long time. I've been
running with passthrough of a PVR-500 in my HTPC, since
On 12/13/2010 06:32 PM, Avi Kivity wrote:
On 12/13/2010 12:31 PM, Xiao Guangrong wrote:
Currently, if the page is not allowed to write, then it can drop
ACC_WRITE_MASK in pte_access, and the direct sp's access is:
gw-pt_access gw-pte_access
so, it also removes the write access in the
On Mon, Dec 13, 2010 at 03:43:44PM -0700, Cam Macdonell wrote:
Do not call pci_update_mappings on the lower 32-bits of a 64-bit bar. Wait
for the upper 32 or else Qemu will try to map on just the lower 32 which is
probably going to corrupt memory.
I was encountering crashes when mapping
Keep track of which task is running a KVM vcpu. This helps us
figure out later what task to wake up if we want to boost a
vcpu that got preempted.
Unfortunately there are no guarantees that the same task
always keeps the same vcpu, so we can only track the task
across a single run of the vcpu.
Add a yield_to function to the scheduler code, allowing us to
give the remainder of our timeslice to another thread.
We may want to use this to provide a sys_yield_to system call
one day.
Signed-off-by: Rik van Riel r...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
---
- move to
When running SMP virtual machines, it is possible for one VCPU to be
spinning on a spinlock, while the VCPU that holds the spinlock is not
currently running, because the host scheduler preempted it to run
something else.
Both Intel and AMD CPUs have a feature that detects when a virtual
CPU is
Instead of sleeping in kvm_vcpu_on_spin, which can cause gigantic
slowdowns of certain workloads, we instead use yield_to to hand
the rest of our timeslice to another vcpu in the same KVM guest.
Signed-off-by: Rik van Riel r...@redhat.com
Signed-off-by: Marcelo Tosatti mtosa...@redhat.com
diff
On Tue, 14 Dec 2010 03:54:47 am Michael S. Tsirkin wrote:
On Mon, Dec 13, 2010 at 12:44:13PM +0200, Michael S. Tsirkin wrote:
Please merge the following tree for 2.6.38.
Thanks!
Um, I sent this out before I noticed the mail from Rusty
with some questions on the test code. I missed that
Hi,
Which version of Qemu contains the Smbios code? If I have to get the code in my
repo, is there any place I can get the complete set of patches?
Thanks
Anjali
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo
1 - 100 of 108 matches
Mail list logo
